Skip to content
Strata

Roadmap

What is planned for the template and how to propose changes.

The template is intentionally opinionated and small enough to understand in an afternoon. These are the areas under consideration; none of them are promises.

Planned#

  • Internationalisation layout: Astro’s i18n routing with a language switcher and translated content collections.
  • Newsletter action: a double-opt-in subscribe flow backed by Resend audiences.
  • More islands: a command palette, a pricing table and a theme-aware chart example.
  • Profile editing on the dashboard (name and avatar).

Under evaluation#

  • Route caching (cache and routeRules, stable in Astro 7) for server-rendered pages with CDN cache providers on Vercel, Netlify and Cloudflare.
  • Two-factor authentication through the Better Auth plugin.
  • Scheduled retention as a workflow in the repository rather than an example in the docs.

Non-goals#

  • A component library beyond what the site itself needs.
  • A CMS integration. Content collections accept any loader; wire your CMS through a custom loader instead.
  • Supporting Node versions older than 24.

Proposing changes#

Open an issue describing the problem first. Pull requests should include a changeset, pass the CI matrix and update the documentation that describes the affected behaviour.