Static website

Minerva brings data, workflows, approvals, and AI setup into one operational platform.

Every page now lives as an explicit Svelte route, route-specific UI stays close to the page that uses it, and the site stays fully static with no runtime content fetching.

Built for teams that change systems often

Minerva is a low-code operations platform for teams that need their internal systems to keep up with the business. Collections model the data, apps and pages shape the experience, approvals add control, and automations keep recurring work moving in the background.

The website follows that same structure: product pages, docs, changelogs, feature guides, and blog posts all live as route-backed Svelte files instead of hidden behind generic loaders or runtime content readers.

What this gives the team

  • One explicit route file per page, including docs pages, blog posts, and feature guides.
  • Static rendering with no runtime content fetching.
  • Local components/ folders whenever a page needs richer UI.
  • Shared metadata that powers navigation, feature menus, listings, and SEO.

A simpler authoring model

Every route is discoverable in src/routes, which makes the content structure easier to understand and easier to extend. Feature pages live next to feature-specific UI. Docs pages live in the docs route tree. Blog posts live in the blog route tree.

That keeps the app static, keeps the route tree honest, and removes hidden content collections behind generic slug loaders.

Feature guides

Each feature page is a first-class route with its own Svelte file and metadata. That metadata is reused for the navbar and listing pages so the website only has one source of truth.

From the blog

Blog posts are static route files too, so the index, article pages, and navigation all come from local route metadata instead of server-side readers or remote functions.