Decisions summary
| Topic | Decision | Why |
|---|---|---|
| Product | The core is the main product; modules and extra themes are extras | The developer audience moves faster with ready-made vertical modules |
| Ecosystem | Modules first, then themes | The theme market is saturated; a module answers the question "what can I build with this" |
| Updates | Signed manifest, atomic writes, DB backup, automatic rollback | The only part that can destroy the site is the update |
| WAF | Is not turned off; a narrow exemption for writing fields | No compromise on security and performance |
| Malware scanner | A local scanner, off by default | Does not load the system; no GPL code is linked |
| Update channel | A private channel (for the main site) | Trying first on our own site in production |
| Documentation | Docusaurus style, versioned, md/zip import | An experience recognized worldwide; docs stay in sync with the repository |
| Markdown | league/commonmark (core dependency) + local Toast UI Editor |
Correct and safe Markdown; no CDN |
| Migrated projects | Each becomes a module; the core's gaps are given back to the core | The core matures with every migration |
For the details and history of the decisions, see the other pages in this section and the changelog.