Legacy path preservation
The slug stays exactly the same for continuity and SEO stability.
Service page
Services New Page
The legacy URL is preserved without changing the slug, while the page remains a reserved path ready for future content.
Phase 1 uses structured mock data and reusable sections that can later connect to API sources.
Overview
The copy is placeholder, the architecture is real
This route exists because it is part of the existing sitemap and needs to stay preserved in the new architecture.
Phase 1 gives it the same rendering and metadata quality as the other pages, even though the content is not finalized yet.
Capabilities
Sections can expand without changing the page files
These cards model typed content structure rather than final marketing copy.
Ready placeholder
The page can later become a separate service landing page or campaign page.
Full metadata support
Canonical URLs and alternates follow the same rules as the rest of the routes.
Building blocks
The components are ready for future data feeds
Clear route manifest entry
The legacy URL is explicitly defined in the central manifest.
Reusable section set
Hero, sections and CTA are already ready for real content once it is defined.
Static generation
The route enters generateStaticParams and the sitemap without special handling.
How it scales
This reserved route can quickly become a real production page
- Add the final title and description once the content is approved.
- Replace placeholder capability cards with real offers or modules.
- Decide whether the route is permanent or campaign-based, then adjust the CTA flow.
Call to action
The legacy path is safely preserved in the new foundation
This keeps full control over sitemap continuity while the content for this route is still maturing.
