A few months ago, *admis* asked a question on sub-Stories in this post: Create New Tiddler and Substories <https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/sY2rsxp2tD4>
That is what I first thought of when I read the post above by *Joe Armstrong*. The reason is that a sub-Story has its own history. It may also be able to have its own view-template - perhaps useful for navigation. I am stuck on the way to present the series of Beginner tiddlers <https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/b6TBlPPWRhM> for tiddlywiki.com . Interestingly this is the exact case *Joe Armstrong* referred to: So I'd like a tiddler called 'beginner' to contain a list of tiddlers, and > 'intermediate' to contain a different list of tiddlers > I wanted to use a *tabbed-internal* Table of Contents, not only for this, but for the many *list-links* tiddlers on tiddlywiki.com . I opened a GitHub issue #3664 <https://github.com/Jermolene/TiddlyWiki5/issues/3664> on it, but the sugestions did not gain traction. I toyed with the idea of making a sub-Story of the Beginner series with their own forward and backward navigation. Some features that it may need: - The navigation - not just *Previous* & *Next*, but also *Back* (when tiddlers are opened out of order) - Dealing with the case of a tiddler not in the sub-Story-list being opened, where to display it - If it's closed, how to get back to the proper place in the sub-Story. (This is one case where *Back* is needed) - Where the tiddler is not closed, how to get back to the proper place in the sub-Story - Restoring the previous Story when finished with the Beginner series. *AlexHough*, as you rightly pointed out, the tiddlers and their order can be available in any list field. Since the documentation is for tiddlywiki.com - it would be interesting to make this a *Collaborative Effort* of regulars here. So how about we try it for fun and see where it leads! One person will be in charge of *writing the Specs*. Here is a great short and fun to read guide for how this can be done: Painless Functional Specifications - Part 1: Why Bother? <https://www.joelonsoftware.com/2000/10/02/painless-functional-specifications-part-1-why-bother/> - Part 2: What’s a Spec? <https://www.joelonsoftware.com/2000/10/03/painless-functional-specifications-part-2-whats-a-spec/> - Part 3: But… How? <https://www.joelonsoftware.com/2000/10/04/painless-functional-specifications-part-3-but-how/> I nominate: @TiddlyTweeter - perhaps guided by Joe Armstrong A suggested guide of what can be included in the specs is above, and suggested material to include is already available <https://00ss.github.io/help/Adding-a-table-of-contents-to-the-sidebar.html> . Once the Specs are made, the community gets involved with the actual coding needed for meeting the Specs. What's the harm in trying this out? On Monday, March 18, 2019 at 3:12:09 AM UTC+7, AlexHough wrote: > > Would a trail be one of many lists? > > When a tiddler is tagged, the order of the tiddler can be changed in the > list. Perhaps if there was more than one list field in which tiddlers could > registered? > > > Alex > >> . >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b31b7183-c17a-4681-92a4-aaf97193c24f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
