Planning Page

Subdomain Route Groups

This page mirrors the current consolidation plan and keeps route-group data visible while the navigation rebuild is still in progress.

Route Manifest Snapshot

The routes JSON is still active and will be used again when grouped navigation is rebuilt.

Base Path: /

Routes: 7

Base Path: /wiki

Routes: 1

Base Path: /projects

Routes: 1

sakura-sedaia.com serves portfolio routes such as /about, /contact, and /commissions.
wiki.sakura-sedaia.com is currently deployed from a separate wiki codebase.
projects.sakura-sedaia.com is currently deployed from a separate projects codebase.
This app still keeps wiki:// and projects://-aware URL prefix behavior for cross-section links.

If wiki and projects are merged into this SolidStart app, route groups can become canonical subdomain sections.
Public URLs would resolve as `https://wiki.sakura-sedaia.com/...` and `https://projects.sakura-sedaia.com/...`.
Top-level portfolio pages such as `/about` remain canonical on `https://sakura-sedaia.com/about`.

Use one Vercel project with host-based rewrites for:

Decide whether wiki and projects should be merged into this repository or remain independent Vercel projects.
If merged, port the canonical wiki and projects routes into `src/routes`.
Add or update route-group manifests for wiki and projects.
Update metadata generation so canonical URLs use route-group subdomains.
Update sitemap generation to emit canonical domain URLs (or split by subdomain).
Keep wiki:// and projects:// as preferred internal cross-section link prefixes.
Verify rewrites and redirects in production-like previews before permanent redirects go live.

Do not apply host rewrites while wiki and projects are still served by separate repositories.
Until consolidation, this app should keep linking to wiki and projects as external deployments.
In-repo route groups can still act as migration staging areas without replacing standalone deployments.