frontend-architecture

To unify static Astro pages with dynamic Jinja2 templates, this architecture uses a pre-bundled Astro build alongside a Jinja2 runtime and shared tokens configuration. It enables fast SEO-friendly public routes and dynamic user-specific content without code duplication.

Yes, HTMX enables lightweight fragment updates on card-sized components within Jinja2 templates without requiring full page reloads. This allows progressive enhancement of statically generated Astro pages by injecting dynamic server-rendered content.

You share design tokens between Astro and Jinja2 by using a single shared CSS variables configuration. This shared tokens system ensures visual consistency across both static and dynamic routes within the unified frontend architecture.

The best way to serve SEO-friendly public routes and dynamic user-specific content is a unified rendering strategy using Astro for static generation and Jinja2 for dynamic server rendering, avoiding code duplication through shared design tokens.

Yes, you need a pre-bundled Astro build to generate static assets before starting the Jinja2 dynamic server. This pre-bundled build works with the Jinja2 runtime and shared tokens configuration to verify HTMX interactions.

You should not use a unified Astro and Jinja2 frontend architecture if your project does not require both static pre-built pages and dynamic server-rendered templates, or if you cannot maintain a shared tokens configuration across both rendering strategies.