diff options
| -rw-r--r-- | doc/todo/wikitrails.mdwn | 1 | ||||
| -rw-r--r-- | doc/todo/wikitrails/discussion.mdwn | 25 |
2 files changed, 25 insertions, 1 deletions
diff --git a/doc/todo/wikitrails.mdwn b/doc/todo/wikitrails.mdwn index f6e41253b..ca97c9404 100644 --- a/doc/todo/wikitrails.mdwn +++ b/doc/todo/wikitrails.mdwn @@ -38,3 +38,4 @@ the index page is parsed as markdown; numbered lists and "`*`" bulleted lists ar * search for index page is currently next to hardcoded * reading the index --- markdown syntax parsing is currently on a it-can-use-what-i-produce level; maybe integrate with existing mdwn parser * uses undocumented titlepage command + > Don't worry about that, titlepage isn't going anywhere, and will probably before a formal part of the api next time I consider api changes. --[[Joey]] diff --git a/doc/todo/wikitrails/discussion.mdwn b/doc/todo/wikitrails/discussion.mdwn index 9de2cb7d4..327e61491 100644 --- a/doc/todo/wikitrails/discussion.mdwn +++ b/doc/todo/wikitrails/discussion.mdwn @@ -1 +1,24 @@ -This sounds like a more general version of what I want for one-photo-per-page galleries, where each page has previous|up|next links (like this plugin) and the index page has a list or grid of thumbnails (\[[!inline]] with a specially modified template perhaps). I'll watch this with interest! --[[smcv]] +This sounds like a more general version of what I want for +one-photo-per-page galleries, where each page has previous|up|next links +(like this plugin) and the index page has a list or grid of thumbnails +(\[[!inline]] with a specially modified template perhaps). I'll watch this +with interest! --[[smcv]] + +This is a nice idea, I do have my gripes about the imeplementation. + +Assuming that the index's list is in mdwn format is not ideal. I guess the +other way to do it would be to make the index be a directive, something +like: \[[!trail pages="foo bar baz"]]. Assuming that a flat trail structure +is enough, otherwise you'd have to get more fancy. + +The trailinclude seems a bit redundant with inline, and wanting to inline +together all pages in a trail for printing or whatever seems like an +unusual use case anyway? + +The !trail directive could be simplified to just \[[!trail my_indexpage]]. +But I wonder if needing to add this directive to every page is the best +approach. Alternate approach would be to make the trail index cause +breadcrums to be automatically inserted at the top of every page on the +trail. (You'd have to use a directive to define the index for that to work.) + +--[[Joey]] |