performancedeployment
Rest as a performance budget
How the seventh day maps to maintainability, caching, minimal JavaScript, and a calm production surface.
Astro 6.2 production template
Astro Genesis
A content-first Astro template that demonstrates static generation, server rendering, live content, actions, sessions, SEO, dark mode, and Docker deployment through the creation narrative.
Day 1
Light and Time
The first separation creates rhythm: day, night, contrast, perception, and the first measurable frame.
Day 2
Waters and Sky
A boundary appears between depths and heights, giving the world a layered architecture.
Day 3
Land and Growth
Structure becomes habitat, and habitat becomes a system that can bear seed, fruit, and continuity.
Day 4
Luminaries
The heavens become a calendar: signs, seasons, governance, and navigable time.
Architecture
Latest Astro features without needless ceremony
The template keeps Astro primitives visible and replaceable: content collections for durable content, SSR only where it earns its keep, and typed data where teams need confidence.
Astro 6.2 server output with per-route prerendering
Implemented as a reusable pattern with documentation and a minimal public surface.
Tailwind CSS 4 through the official Vite plugin path
Implemented as a reusable pattern with documentation and a minimal public surface.
Content Collections with MDX, typed frontmatter, tags, RSS, and sitemap
Implemented as a reusable pattern with documentation and a minimal public surface.
Live Content Collections demo for request-time data
Implemented as a reusable pattern with documentation and a minimal public surface.
Server islands, Actions, Sessions, Middleware, and API endpoints
Implemented as a reusable pattern with documentation and a minimal public surface.
Fonts API, CSP API, image defaults, prefetch, and CSP-safe navigation
Implemented as a reusable pattern with documentation and a minimal public surface.
Docker standalone Node deployment and GitHub CI automation
Implemented as a reusable pattern with documentation and a minimal public surface.
Content model
Genesis as structured demo content
Each creation day is represented as content data and routed into pages, widgets, live collections, and dynamic endpoints.
Day 1
Light and Time
The first separation creates rhythm: day, night, contrast, perception, and the first measurable frame.
Day 2
Waters and Sky
A boundary appears between depths and heights, giving the world a layered architecture.
Day 3
Land and Growth
Structure becomes habitat, and habitat becomes a system that can bear seed, fruit, and continuity.
Day 4
Luminaries
The heavens become a calendar: signs, seasons, governance, and navigable time.
Day 5
Creatures of Water and Air
Movement fills the open spaces, showing how content and interaction can animate a static frame.
Day 6
Humanity and Stewardship
The template shifts from spectacle to responsibility: accessible interfaces, clear editing, and care.
Day 7
Rest and Completion
The final measure is not more complexity; it is a stable system that can be maintained without strain.
Loading server island...
Widgets
A complete starter surface
Common website modules are included as simple Astro components, with just enough JavaScript for menus, tabs, accordions, and theme control.
Editorial
Hero
Feature grid
Timeline
Stats
Blog cards
Callouts
Conversion
CTA band
Contact action
Newsletter pattern
FAQ accordion
Feature matrix
Platform
Server island
Session counter
Live collection
JSON endpoint
RSS
Sitemap
Can this ship as a static site?
Yes. Static routes opt into prerendering while the repository keeps a Node adapter for SSR demos, Actions, Sessions, and server islands.
Where do project-specific contents live?
Blog posts live in src/content, structured demo data lives in src/data, and shared template code stays in components, layouts, and lib.
How is the template kept up to date?
The repo includes CI, Dependabot groups for Astro and Tailwind, an upgrade script, and documentation describing safe update steps.
Blog
Demo posts with MDX and typed frontmatter
The blog proves content collections, tags, RSS, sitemap generation, and article SEO in one place.
genesisarchitecture
Waters above, waters below, and layered architecture
A Genesis-inspired model for separating content, rendering, styling, runtime behavior, and deployment concerns.
genesisaccessibility
Day One: Light as the first interface
How the first act of separation becomes a metaphor for routing, contrast, accessibility, and fast first paint.
Ready for adaptation
Keep the architecture. Replace the story.
Genesis is the demo layer. The template structure is built so real projects can update content, navigation, and branding without editing routing, SEO, or deployment internals.