Content Collections & Routes

Lumio Theme Documentation

Lumio’s content system is more advanced than a simple “one Markdown file equals one page” setup.

The project uses Astro content collections defined in:

Lumio defines collections for:

Many collections are configurable through config.toml. For example:

[settings]
  blogFolder = "blog"
  servicesFolder = "services"
  caseStudiesFolder = "case-studies"

That means route behavior and content lookup depend partly on config, not just file names.

Generic static pages are rendered by:

That file:

So files like these:

become localized routes through that catch-all page.

Files in src/content/sections/<language>/ are usually not routed directly.

They are data sources for section components such as:

This is why editing a section file changes multiple pages at once when that section is reused.

Use this simple rule:

That separation is powerful, but it is also the main reason Lumio feels more “app-like” than a basic Markdown theme.