Josiah,
I have being looking closely at the optimum way to represent all resources us TiddlyWiki enthusiasts use in the process of developing a Community resource website, also within my own network of wikis I have built informal standards around storing such things in Tiddlers. This is not yet exhaustive but that is where I am headed.
It is critical to develop such methods as tiddlywiki can generate a lot of details people can make use of, for example in my MyMenus plugin every menu item can also be a code snip-it people can use and I have almost 100 of these and I have only started.
Basing everything on a tiddler model makes sense because they immediately become shareable, and can carry the required tags to make them work.
My own method includes creating fields such as field-caption menu-caption to define "field tiddlers" and "menu tiddler "and where ever a macro is defined in a tiddler a field macro-macroname with the "syntax" in the field value etc... is another standard.
Some reoccurring objects in tiddlywiki such as macros, buttons etc... are often already grouped using the relevant system tag that results in their display, which may be a sensible way
- view template additions $:/tags/ViewTemplate
for the view template
- view toolbar additions $:/tags/ViewToolbar
for the view mode tiddler toolbar
- edit toolbar additions $:/tags/EditorToolbar
Note that there are some cases where an Item could be validly tagged with more than one
So If we take the urls from TiddlyToolMap we could create tiddlers that have say the tiddllywiki-resource field containing the url, use the title and description fields even an icon if one is available.
It would be quite easy to build some macros that display and list such items intelligently.
I suppose my point is this is about knowledge and information management and we have the perfect tool for this, tiddlywiki all we need to do is promote some defacto standards and share them.
Regards
Tony