Now, why bother with defining all that? Well, that would make sharing recipes a lot easier in the TiddlyCook community.
In fact, perhaps the use of tags should be discouraged and a *cook* field used, e.g... - *cook*=recipe - *cook*=recipe-category - *cook*=ingredient - *cook*=ingredient-category - *cook*=method - *cook*=list-recipes - *cook*=list-recipe-categories - *cook*=list-methods - *cook*=list-ingredients - *cook*=list-ingredient-categories Now, why use a *cook* field for that? Consider multiple-languages each with their own set of category tags. Having a (hidden) *cook* field set to the type of the tiddler will not only match the categories across languages correctly, it will also make it easier to use the same templates, and allow the user to name their category tiddlers or tags whichever way they want. Best wishes, Tobias. -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
