Practical notes from the workbench
These guides explain three decisions that keep a small site maintainable: who owns each change, how translated sections share a structure and why installation is not synchronization.
In practice
Read one guide before changing a layer you do not normally touch. Native authoring is most useful when the ownership of content, composition and presentation stays visible.
Continue through this site
- Modularis: structure without a second editor
- Thematis: a calm frame for the whole site
- Derivis: inherit a theme, keep your identity
- From installation to a first useful page
- Choose the smallest useful combination
A launch is a starting point, not a synchronization job
A Launch Pack copies a versioned native page tree into an unused target. The installation marker records the created files. After that, those Pages belong to the site owner and can change independently of the bundled source.
Translate the message, share the structure
Native language files let a page keep different titles and bodies. Composer deliberately manages one common logical order of modular sections across supported parent variants. The translated wording is not an alternative structure store.
One change, three different owners
A sentence belongs to the page editor. The order of sections belongs to Page Composer. The site header belongs to the active theme. These are ordinary ownership boundaries, not three competing builders.