Five pages, one checkout, zero duplication

Each of the five service pages — audio, production, musician, software, accessibility — has its own URL, its own copy, and its own product listings. But the underlying components are shared. One service navigation bar handles switching between pages. One sidebar accordion handles packages, booking, and contact. One checkout wizard handles the four-step payment flow. One product card grid handles the pricing display. Adding a sixth service would mean creating one data file and one page component. Everything else is already built. This is what reusable components are supposed to do — not premature abstractions, but proven patterns extracted from five real pages that all needed the same thing.