FEATURE CATALOGUE
Twenty-seven features. You choose which exist.
Switch a feature off and it doesn't hide — it disappears. Its API routes stop answering, and it vanishes from the menu, from search, from bulk actions, and from the dashboard. Your client never sees a greyed-out thing they can't have.
Showing 27 of 27 features
| Feature | What it does | Group | Type |
|---|---|---|---|
| Authentication & accounts | Sign-in, sessions, profile and address book. The account spine everything else depends on. | Core | Core |
| Content engine | Content types, entries, blocks, taxonomy, and the public content API. | Core | Core |
| Media library | Upload, storage, derivatives, and controlled delivery of every file. | Core | Core |
| User management | The user directory, roles, and access administration. | Core | Core |
| Settings & branding | Colours, fonts, logo, text direction, default language, feature toggles. | Core | Core |
| Notifications | The event engine and delivery across every channel. | Core | Core |
| Full-text search | Unified search across content, products, and categories, with ranking and highlighted snippets. | Content | Optional |
| Navigation menus | Tree-structured menus placed in named locations — header, footer, sidebar — fetched in one call. | Content | Optional |
| Spec sheets | Structured technical attributes with filtering and side-by-side comparison. | Content | Optional |
| Media albums & gated downloads | Grouped media and downloads restricted to who's allowed them. | Content | Optional |
| Product catalog | Public product, collection, and brand browsing with faceted filtering. | Commerce | Optional |
| Shopping cart | Guest and account carts, reservations, and gifting. | Commerce | Optional |
| Shipping | Zones, methods, composite rate rules, and bookable delivery slots. | Commerce | Optional |
| Checkout & orders | Payment, the order lifecycle, tracking, and the customer's order history. | Commerce | Optional |
| Coupons & discounts | A composable rule engine — conditions and effects — applied to the cart. | Commerce | Optional |
| Customer wallet | A double-entry ledger with balances, holds, and transfers between wallets. | Commerce | Optional |
| Form builder | Build any form from typed fields, collect structured submissions, reply, export. | Engagement | Optional |
| Newsletter | Double opt-in subscription with consent state and source tracking. | Engagement | Optional |
| Case engine | Multi-stage client cases with events, documents, and a shared status timeline. | Engagement | Optional |
| Reviews & ratings | Customer reviews and scores with a moderation workflow. | Engagement | Optional |
| Comments | Threaded comments on any content, moderated before they go public. | Engagement | Optional |
| Public profiles | Public-facing profiles for users who create content. | Engagement | Optional |
| Two-factor authentication | TOTP apps and WebAuthn security keys, with recovery codes and trusted devices. | Platform | Optional |
| Global admin search | One search box across every section of the admin panel. | Platform | Optional |
| Saved views | Filter and column combinations saved and reused per operator. | Platform | Optional |
| Bulk actions | Act on many records at once, with permission checks and audit entries per record. | Platform | Optional |
| Admin dashboard | Configurable widgets, positioned per administrator. | Platform | Optional |
How toggling behaves
Three rules, and the third is the one people expect to be marketing.
Off means gone
A disabled feature's API routes return 404. It's removed from the admin menu, from global search, from bulk actions, and from the dashboard. There is no greyed-out upsell.
Dependencies are enforced
Checkout needs a cart. A cart needs a catalogue. Coupons need a cart. You can't enable something whose prerequisites are off, and you can't disable something another feature still needs — the system explains why instead of breaking.
Core stays on
Authentication, content, media, users, settings, and notifications can't be switched off. Nothing works without them, so the system refuses rather than letting you break it.
Need something that isn't on this list?
That's usually a registry away, not a fork away. Your requirement becomes a new definition, not a modified core.
- Field types
- Payment gateways
- Discount rules
- Notification channels
- Dashboard widgets
- Reports
- Importers
Bring your requirements list.
Send it over. We'll mark off what's already here and be straight about what isn't.
- We reply within one working day
- No sales sequence, no drip campaign
- NDA before the call if you'd prefer