Introducing the boilerplate
By Admin User
Every project starts the same way: authentication, a content page or two, an admin panel, and a fortnight gone before the interesting part begins. This is the starting point that gets that fortnight back.
What is in the box
- Accounts with everything a real product needs: email verification, password reset, two-factor, passkeys.
- A roles-and-permissions model that covers a small team on day one.
- Content pages and a blog, written in Markdown from the admin panel.
- Payments: one-off and subscription, with receipts and refunds.
- The operational spine -- logging, audits, health checks, summaries.
What is deliberately not in the box
Opinions about your domain. The boilerplate ends where your product begins, and not a screen later.
The demo instance
Deploy it and it seeds itself into a working state: accounts you can one-click into, a year of trading on the dashboard, and content on every page. It is meant to be shown, not assembled first.
Start from it, and put your fortnight into the thing only you can build.
