Bundles

A bundle is a ready-made starting point. Rather than enabling modules and adding fields one at a time in a blank workspace, you pick a bundle close to what you're tracking and it sets things up for you: the right modules, the fields that matter, some sensible views, and a set of features already turned on.

Named for what you track, not how you work

A bundle is named for the thing it's about (Yarn, Lego, 3D Printers), not for a workflow. What it actually does comes from the features it turns on. Two people can start from the same Yarn bundle and end up with different apps because they checked different feature boxes. One tracks dye lots, another logs projects, a third runs a shop.

The name tells you where to start, the features tell you what it can do, and you're locked into neither. You can toggle features and enable more modules whenever you want.

From a bundle or from scratch

Starting from a bundle is the fast path: a working setup you can use right away and reshape as you go. Starting from scratch means enabling modules and defining fields yourself, which is there for when nothing fits or you want full control. Either way you land in the same place, a workspace made of modules, so a bundle is a head start rather than a cage.

Bundles are just configuration

Under the hood a bundle is data, not code: a declared set of enabled modules, features, fields, views, and wires. That's why they can be authored, including by describing what you want in plain language and letting Cobblr generate the bundle for you. See Authoring a bundle.