Cookbook

Draft placeholder — content to be written (docs #3 on the 0.4.0 launch checklist). Worked examples and recommended patterns go here.

Naming your components

Avoid generic or reserved-sounding names for your own defs components — macro, Macro, macro1, function, helper, data, and similar. They are legal, but easy to confuse with built-in names or with each other. Prefer descriptive names tied to what the component actually does.

TODO: more recipes — recursive components, closures (0.5+), common navigation patterns, working with datasets, etc.