V3 launch: promote v3 to main site, archive old site

Date: 2026-05-16 Status: Design approved, ready for implementation plan Scope: www/ only — no backend, no infra changes

Goal

Make www/v3/ the live site at getorcha.com/de/ and getorcha.com/en/, archive the current site to getorcha.com/archive/, and reuse the existing community pages under v3's header/footer.

The /v3/ URL path disappears entirely after launch.

Non-goals

• Rewriting or restyling the community pages — body content and design stay as-is, only header/footer change
• Setting up redirects from /v3/* to / (no external backlinks rely on /v3/ paths)
• Touching the deploy pipeline — AWS CodePipeline picks up www/ as-is; user triggers deploy manually
• Restyling 404 pages — reuse the existing ones from the current site

File-system topology

Before

www/
├── index.html                  # redirects to /de/
├── css/globals.css
├── js/{community-forms, main, orb, tracker}.js
├── images/, logos/
├── de/                         # current live site
│   ├── 404.html
│   ├── index.html
│   ├── about/, contact/, imprint/, privacy/, produkt/, terms/
│   ├── validation-preview.html
│   └── community/              # ★ stays
│       ├── index.html
│       ├── posts/<37 dirs>/index.html
│       └── videos/
├── en/                         # mirror of de/, with /imprint/, /privacy/, /terms/, /product/
└── v3/                         # new site, currently not live
    ├── de/
    │   ├── index.html
    │   ├── agents-draft.html, korrektheit-draft.html       # to delete
    │   ├── produkt/<10 pages>, agenten/, steuerberater/
    │   ├── roi/, implementierung/, trial/
    │   ├── impressum/, datenschutz/, agb/
    │   └── archive/                                         # internal v3 working files
    ├── en/                     # mirror with /imprint/, /privacy/, /terms/
    ├── css/{v3, product, responsive, tokens, trial}.css
    ├── js/{chrome.de, chrome, hero, roi, swimlanes, …}.js
    ├── design-guide.html       # internal design ref
    ├── variations/             # UI exploration mockups
    ├── dev/                    # Playwright screenshot tooling
    └── robots.txt              # redundant; root www/robots.txt is authoritative

After

www/
├── index.html                  # unchanged (still redirects to /de/)
├── robots.txt                  # updated: Disallow: /archive/
├── sitemap.xml                 # regenerated for v3 page set
├── css/
│   ├── globals.css             # unchanged (community + archive use this)
│   ├── v3.css                  # from www/v3/css/
│   ├── product.css             # from www/v3/css/
│   ├── responsive.css          # from www/v3/css/
│   ├── tokens.css              # from www/v3/css/
│   └── trial.css               # from www/v3/css/
├── js/
│   ├── community-forms.js, main.js, orb.js, tracker.js    # unchanged
│   ├── chrome.de.js, chrome.js                            # from www/v3/js/, with path fixes
│   └── ablauf, dunning, hero, hero-agent, home-pipeline,
│       orchestration, roi, supplier-chat, swimlanes,
│       testimonials, trial-form, viz-activate, workflow.js # from www/v3/js/
├── images/, logos/             # unchanged
├── archive/                    # NEW — frozen old site
│   ├── de/
│   │   ├── index.html
│   │   ├── about/, contact/, imprint/, privacy/, produkt/, terms/
│   │   └── validation-preview.html
│   └── en/  (mirror)
├── de/                         # v3 promoted
│   ├── 404.html                # kept from old site (not archived)
│   ├── index.html              # from www/v3/de/
│   ├── produkt/, agenten/, steuerberater/, roi/, implementierung/
│   ├── trial/, impressum/, datenschutz/, agb/
│   └── community/              # ★ unchanged location + body; new header/footer wired
└── en/                         # v3 EN promoted
    ├── 404.html                # kept from old site
    ├── index.html
    ├── produkt/, agenten/, steuerberater/, roi/, implementierung/
    ├── trial/, imprint/, privacy/, terms/
    └── community/              # ★ unchanged body; new header/footer

Files deleted outright (not archived)

• www/v3/de/agents-draft.html
• www/v3/de/korrektheit-draft.html
• www/v3/variations/ (entire directory — UI exploration mockups)
• www/v3/dev/ (entire directory — Playwright screenshot tooling)
• www/v3/design-guide.html (internal design reference)
• www/v3/de/archive/, www/v3/en/archive/ (v3-internal working files, distinct from the new www/archive/)
• www/v3/robots.txt (root www/robots.txt is authoritative)
• www/v3/ itself (empty after the above)

Files explicitly preserved

• www/index.html — root redirect, points to /de/, content unchanged
• www/de/404.html, www/en/404.html — kept at the new root, NOT archived (per user request to "take the one we already have"). Wired with v3 chrome in the same pass as community pages.
• www/de/community/, www/en/community/ — entire directories (index + posts + videos) stay at their URLs. Only <header> and <footer> change; body content, Tailwind setup, orb canvas, AOS, globals.css references all stay.

Path and reference rewrites

chrome.de.js and chrome.js (after move into www/js/)

Switch all internal hrefs to absolute paths (this is the single change that makes the script depth-independent and lets community posts at depth 3 work without special-case logic).

Specific edits:

• Language toggle: location.pathname.replace(/\/v3\/de(\/|$)/, "/v3/en$1") becomes location.pathname.replace(/\/de(\/|$)/, "/en$1")
• Trial CTAs /v3/de/trial/, /v3/en/trial/ → /de/trial/, /en/trial/
• Logo paths: ../../logos/orcha-logo.png and the deeper ../../../logos/... both become /logos/orcha-logo.png (same for orcha-icon.png)
• All homeHref, moduleHref, steuerberaterHref, agentenHref, roiHref, implementierungHref, impressumHref, datenschutzHref, agbHref, anchorHref helpers: switch from depth-relative to absolute paths
• isProductSubpage / isOtherSubpage detection: regexes already use /de/ (not /v3/de/), so they keep working post-move and on community pages without changes
• Community link in footer already uses /de/community/ (absolute) — no change

All HTML files moved from www/v3/ to root

Find/replace /v3/de/ → /de/ and /v3/en/ → /en/. Affects:

• <link rel="canonical"> URLs
• <link rel="alternate" hreflang=…> URLs
• <meta property="og:url"> content
• Any in-body href="/v3/..." references
• Inline <script> blocks that hardcode paths

Per earlier exploration: ~19 files reference /v3/ explicitly.

Community page chrome wiring

Affects:

• www/de/community/index.html
• www/en/community/index.html
• www/de/community/posts/<slug>/index.html × 37
• www/en/community/posts/<slug>/index.html × 27

Subtotal: 66 community files (2 indexes + 64 posts).

Plus, in the same pass:

• www/de/404.html, www/en/404.html (2 files)

Grand total for step 6: 68 files get the chrome treatment.

Per-file changes

1. In <head>, add: <link rel="stylesheet" href="/css/v3.css">
2. Rename the existing header element ID: <header id="site-navbar" class="..."> → <header id="site-header"></header> (drop the Tailwind classes — v3 chrome supplies its own styling)
3. Leave the existing footer placeholder ID unchanged: <footer id="site-footer"></footer> already matches what v3 chrome looks for
4. Before </body>, add: <script src="/js/chrome.de.js"></script> (DE) or <script src="/js/chrome.js"></script> (EN). Must come AFTER main.js in the script tag order — see "main.js coexistence" below

main.js coexistence

The community pages currently load /js/main.js, which does several things:

• Populates #site-navbar with old chrome (no-op after we rename to #site-header)
• Populates #site-footer with old chrome (collides with v3 chrome)
• Wires #cookie-banner / #cookie-accept click handlers (independent body elements — keep working)
• Wires #scroll-to-top and #copy-email-btn handlers (currently inside main.js's rendered old footer — these are lost once v3 chrome overwrites the footer, but neither feature is critical for community pages)

Resolution:

• Keep the main.js script tag in community pages (it still handles the cookie banner that lives in the page body)
• Ensure the v3 chrome script tag is placed after the main.js tag in source order. Both scripts run on DOMContentLoaded; the later-registered handler runs last, so v3 chrome's innerHTML write to #site-footer overwrites main.js's. Brief flash of the old footer is possible but imperceptible (both run on the same DOMContentLoaded tick).
• Accept that scroll-to-top and copy-email-btn no longer work on community pages — they were features of the old footer, not the v3 footer. Not worth re-implementing.

Preserved per page

• Tailwind CDN script
• Google Fonts links
• AOS CSS/JS
• globals.css link
• main.js (for cookie banner)
• orb.js, community-forms.js, tracker.js script tags
• All body content (hero, post grid, post body, cookie banner div, etc.)
• All meta tags (canonical, OG, Twitter, hreflang)
• Favicon link

Path adjustments inside community pages

Community pages currently use ../../css/globals.css, ../../js/main.js, etc. (depth-2 relative paths). After this change:

• Keep the existing depth-relative paths — they still resolve correctly because www/css/, www/js/, www/logos/ are unchanged
• The newly-added v3 references (/css/v3.css, /js/chrome.de.js) use absolute paths
• Posts at depth 3 (/de/community/posts/<slug>/index.html) use ../../../css/globals.css etc. — verify case-by-case during implementation; no change needed if existing paths are correct

CSS conflict concern

v3.css and Tailwind both define base styles. Risk: v3 resets or typography bleed into community body.

Mitigation: v3.css selectors are mostly class-based (.nav-*, .btn, .dropdown-*). Risk is low. Verify by spot-checking 3 wired pages (DE community index, 1 DE post, 1 EN post) — if visible regressions, scope v3 chrome under a .v3-chrome class. Don't pre-scope; YAGNI.

Sitemap, robots, redirects

www/sitemap.xml

Regenerate from scratch. Include:

• https://getorcha.com/ (root)
• https://getorcha.com/de/, https://getorcha.com/en/ (home)
• All 10 product pages per language (produkt/{kreditoren, debitoren, dokumente, vertraege, freigaben, abschluss, varianz, fpa, einkauf, spesen}.html)
• Top-level v3 pages per language: agenten/, steuerberater/, roi/, implementierung/, trial/
• Legal pages: DE impressum/, datenschutz/, agb/; EN imprint/, privacy/, terms/
• https://getorcha.com/de/community/, https://getorcha.com/en/community/
• All community posts (37 DE + 27 EN)

Exclude:

• /archive/* (not for indexing)
• 404 page
• Internal/draft pages (already deleted at this stage)

Set <lastmod> to today (2026-05-16). Use existing sitemap format as template.

www/robots.txt

Add Disallow: /archive/. Leave existing rules intact.

Redirects

None needed. Per user: no external backlinks rely on /v3/ paths.

Testing checklist (manual, pre-merge)

Before opening the PR / triggering deploy:

• www/de/index.html renders correctly with logo, nav, footer (paths resolve)
• www/en/index.html same
• One product subpage per language renders: /de/produkt/kreditoren, /en/produkt/kreditoren
• One other top-level subpage per language: /de/agenten/, /en/agenten/; /de/roi/, /en/roi/
• Language toggle works from a deep page: /de/produkt/kreditoren → /en/produkt/kreditoren
• Trial CTA in nav points to /de/trial/ (and resolves)
• Trial form on /de/trial/ submits successfully (Google Apps Script integration)
• Community index /de/community/ shows v3 nav + footer, hero/post grid/Tailwind body unchanged
• One DE community post and one EN community post render with v3 chrome, no orb/AOS regressions
• 404 page (/de/404.html) renders with v3 chrome
• /archive/de/index.html opens (acceptable if CSS partly broken — frozen artifact)
• No file at www/v3/ remains
• Grep for /v3/ in www/ returns zero results

Post-merge / post-deploy:

• Visit getorcha.com → redirects to /de/
• Visit getorcha.com/v3/de/ → 404 (no leftover content)
• Verify in Google Search Console: sitemap accepted, archive paths not indexed

Commit slicing

Single branch, 7 commits:

1. chore(www): move current site to /archive/ — move all of www/de/{about,contact,imprint,privacy,produkt,terms,index.html,validation-preview.html} → www/archive/de/; same for EN. Keep 404.html and community/ at original location.
2. chore(www): delete v3 draft and exploration files — agents-draft.html, korrektheit-draft.html, variations/, dev/, design-guide.html, de/archive/, en/archive/, v3/robots.txt.
3. feat(www): promote v3 css and js to root — move www/v3/css/* → www/css/; www/v3/js/* → www/js/. No filename conflicts verified at design time.
4. feat(www): move v3 de and en content into root — www/v3/de/* → www/de/; www/v3/en/* → www/en/. Delete empty www/v3/.
5. fix(chrome): switch internal paths to absolute, drop /v3/ references — chrome.de.js, chrome.js, and the ~19 HTML files with /v3/ references.
6. feat(community,404): wire v3 header and footer into community pages and 404 — 68 files (66 community + 2 404). Add v3.css link, rename #site-navbar → #site-header, append v3 chrome script tag after main.js.
7. chore(www): regenerate sitemap.xml and update robots.txt

Each commit is independently reviewable. The branch as a whole is the cut-over.

Risks and rollback

• Risk: CSS bleed in community pages. Mitigation: manual spot-check during step 6; scope under .v3-chrome only if regressions appear.
• Risk: missed /v3/ reference causes broken link. Mitigation: post-step-5 grep gate (! grep -r "/v3/" www/ --include="*.html" --include="*.js").
• Risk: archived pages load with broken CSS because their ../../css/style.css paths still resolve to /css/. Mitigation: this is acceptable — /archive/ is a frozen snapshot, not a polished destination. If wholly broken, accept it; if needed later, paths can be patched in archive HTML.
• Rollback: revert the merge commit. The branch is one atomic change; reverting it restores www/ to its pre-launch state, since git tracks the moves as rename operations.

Out of scope

• Setting up /v3/* → /* redirects in CloudFront/S3
• Triggering AWS CodePipeline deploy (user-initiated)
• Restyling 404 pages beyond wiring v3 chrome
• Updating any external references (LinkedIn posts, email signatures) — user owns
• Re-indexing in Google Search Console — user owns
• Cleanup of www/de/community/videos/ (untouched, out of scope)