Skip to content
Zelavis Docs

Zelavis Docs

Public documentation for the Zelavis composable backend platform.

Principles

Section titled “Principles”
  • Organize by durable product and package categories.
  • Document current behavior first.
  • Clearly distinguish implemented behavior from planned behavior.
  • Keep section structure stable so future doc versioning can be added without a rewrite.

Sections

Section titled “Sections”

Version-ready structure

Section titled “Version-ready structure”

The docs are intentionally organized so future versioning can be added without changing the information architecture.

Current approach:

  • website/src/content/docs/ contains the current canonical documentation.
  • Top-level folders represent stable sections, not framework-specific menus.
  • File names should remain durable and descriptive.

Planned future path when multiple maintained doc versions are needed:

  • versioned doc trees under the website project (for example current/, v1/, v2/)

Until then, keep website/src/content/docs/ as the single current source of truth.

Start here

Section titled “Start here”