Docs and guides

Make the route clear before the stack gets crowded.

This docs layer exists to help people choose the right entrance. It is not there to bury them in brand language or fake technical theater.

Start with templates Go to live apps

Getting started

For first-time visitors

Choose whether you need a template route, a live app route or the custom studio path.
Use `.online` when you want to browse the system world.
Use `.nl` when you are ready for a direct service conversation.

Guides

For route decisions

When to start from a template versus going custom from day one.
How live utility routes support the wider brand and hosting story.
Why the world/studio split is cleaner than one overloaded domain.

Reference

For recurring notes

Route naming and domain logic.
Public maturity levels for products and experiments.
Shared design language across sites, apps and future builder surfaces.

Current public notes

How to move through the ecosystem

Need a launch surface fast: start at the template route.
Need to see live utilities: go to the apps route.
Need custom architecture or hosting discipline: go straight to the studio.
Need rougher experiments or future-facing notes: enter the lab route.

Why this matters

The system reads cleaner when each layer has its own place.

Without docs, the whole thing risks feeling like a scattered collection of domains and side projects. With docs, the same ecosystem starts reading like a shaped operating model.

Clarity is part of the product.