I have an updated PR based on feedback from the first one. The field name has changed to related, and it’s now the first and default tab in a footer than also includes backlinks, tagging, and another meta-information tab.
You can see it in action at https://deploy-preview-8997–tiddlywiki-previews.netlify.app, although only fifty or so tiddlers have been given the new field.
It looks like
@Scott_Sauyet , certainly this is a great improvement, congratulations.
I guess I would like to also see labels for facilities/functions used in the outside world to map them into TW concepts as per the DropDown menu discussion I posted recently. This mapping could be built slowely over time as someone seeks info on a way of doing stuff and once they have the solution, record that in the documentation. I know TW-Talk does that but it is not as user friendly as it could be. Dropdown menu is one example, inhibiting editing of a TW delivered via a non-File protocol is another.
bobj
This technique could easily extend to handle aliases. In the SelectWidget tiddler, add an aliases field, and include “dropdown” in the list. Then add another tab to the footer I’m building for aliases. I think the search would have to be extended to include that field as well.
It’s not clear to me how much this would help, though. When you search for “dropdown” now, the SelectWidget tiddler is in the list, but its name sorts it near the bottom. I don’t really know how to fix that.
It would probably be helpful to have a “Drop-Downs” tiddler that gives a short explanation an/or example and links to all the relevant doc tiddlers (and in turn is linked to by the SelectWidget tiddler, at least in its related field). Not everything must be within the tiddler describing the widget itself. These are too long already in some places. Tiddlers should be small pieces of interlinked information, after all, not pages-long essays.
