Announcing Tidbits — a community recipe edition (v1.0.0)

[Scott_Sauyet]

@jrbntt

Importing my existing (and very small) recipe set worked with minimal effort. I already had lists for Ingredients, and after tagging the imported tiddlers with the Recipe tag and a few small edits to headings, everything “just worked”.

Wonderful!

@jrbntt

I have a generic ingredient name (like “Egg”), which has aliases (“Egg white”, “Egg yolk”), so that I can link whichever specific ingredient from a recipe, but the recipes collect upward into the base Ingredient in addition to appearing on the specific alias.

Hmm, another interesting use of aliases. As I said in my recent response to @vilc, I feel like what I have is at best a good first pass. I still don’t know what a complete one would look like. I’ll keep this use-case in mind, but further suggestions would be very welcome.

@jrbntt

I had already decided on a naming convention for ingredients (title is singular, first word capitalized, etc) and create links using a named link (3 [[egg whites|Egg white]]). This fits my mental model for organizing everything while also making the ingredients list read like a typical recipe, but did require some up-front planning.

Another thing on my todo list is exactly this, with precisely the same conventions, and update my sample recipes (which were borrowed without real change from TheMenuDB.)

@jrbntt

Would it be reasonable to include Ingredient tags in the “Tags” card of the Recipe Box, or perhaps have separate cards for Recipe and Ingredient tags?

Sure. That makes sense, and it’s easy enough. I hadn’t done any ingredient tagging, but clearly there’s room for it.

@jrbntt

On mobile, I completely overlooked the button to expand the Ingredients list in cooking mode.

Any suggested way to make sure it’s discoverable? I love the two-column cooking view, but the one-column one for phone sizes is lacking the recipes. It really needs to, or we’d lose readability, but I want to make sure it’s trivial to get back and forth between them.

@jrbntt

My own thoughts are that the core functionality can (and possibly should) be bundled together into a plugin. The “edition” is simply a pre-configured TiddlyWiki instance with the plugin bundled in.

I do have to think this through some more, but I’m pretty sure I agree.

@jrbntt

The sample content could also be a separate plugin, so that it is easy to test out the edition with some relevant tiddlers, but the sample content is also easy to disable if the user wants to then get to work on their on content without setting up a separate empty instance.

There’s a separate mechanism for this, precisely because I don’t want any recipes or ingredients to be buried in shadow tiddlers. Can you look at it and see if it does what you need?

@jrbntt

So having something that looks nice and meets a common, practical use case does attract interest from a (mostly) non-technical user.

Design goal #1 - check!

@jrbntt

The source field is designed to work with a URL and renders as a link, which makes sense for any recipe found on the Internet. However, if I’ve taken a recipe from a book or my grandmother’s Rolodex, the URL behavior is obviously not the desired outcome.

This should be easy. Only format it as a link if it looks like a URL. If there’s not already a TW built-in for this, it will be easy enough to add. Now on the TODO list.

Thank you for some wonderful feedback!