Museum information is often fragmented and presented without a clear path from discovery to planning a visit.
How I fixed it
I built a multi-page static Astro experience with typed local content, collection and article detail routes, accessible motion, and self-hosted variable fonts.
What it can do
Static multi-page museum experience
Collection and news detail routes
Visit and event information
Typed local content source
Reduced-motion support
The stack that shipped it
Astro keeps content pages lightweight, while GSAP and Lenis provide progressive cinematic motion that respects reduced-motion preferences.
What changed
The project demonstrates an editorial cultural website architecture without requiring a runtime database or server functions.
What I learned
The current authentication and contact screens are UI demonstrations, and seeded placeholder photography remains intentionally disclosed until official assets are available.