Feature with Three Steps

ProWabbit

Numbered step-by-step feature layout with timeline connectors and images

Go from Zero to Deployed in Three Steps

Tome is designed to be operational the same day you fork the starter. No bespoke infrastructure required.

1

Fork the Starter

Clone the tome-starter repo, configure your Payload instance, and point it at your Verdaccio registry. The scaffold ships with auth, roles, and the admin sidebar pre-wired.

Terminal showing git clone command for tome-starter
2

Enable Your Layers

Add the @wabbit/tome-* packages for the capabilities you need — LMS, CRM, blocks, motion — and register them in payload.config.ts. Each layer is independently deployable.

Code editor showing payload.config.ts with tome layers registered
3

Deploy and Iterate

Push to your host of choice. Coolify, Vercel, Railway — the starter is infrastructure-agnostic. Ship incremental changes without breaking existing consumers.

Deployment dashboard showing a successful production build
featurestepsprocess