Axerity

Roadmap

Where Axerity is and where it is heading. This tracks the engine itself. It is a direction, not a set of promises.

Prebuilt server engine Shipped · 0.2.0

The engine ships compiled. Content and config are read from the filesystem at runtime, with no bundler in the serving path, so a package manager quirk can no longer break a build.

Runtime base path Planned

Resolve the base path at request time instead of at compile time, so a site can be hosted under a sub path, like a project page.

OpenAPI for user projects Planned

Run API reference generation as a CLI pre step, so a project’s openapi config produces pages without needing the engine compile.

Merge the public folder Planned

Fold a project’s public/ folder into the built output, for custom images and other static assets.

Smaller installs Planned

Move build only packages to dev dependencies, so a project installs a handful of runtime packages instead of the full toolchain.

Incremental builds Exploring

Cache rendered pages by content hash, so a large site only rebuilds the pages that changed.

A plugin surface Exploring

Let projects add their own remark or rehype steps and custom components without forking the engine.