[Migration Setup] Shared Assets & Cross-Site Navigation Guidelines

[ZJvandeWeg]

Epic

4867

Description

Objective

Prevent visual jumping when users navigate between the Nuxt SPA and the 11ty static pages, and ensure routing doesn't break during the transition.

Tasks

• Move global CSS, fonts, and core branding images to a shared location (e.g., Nuxt's public folder) so both legacy and nuxt point to the exact same stylesheets.
• Document navigation rules in the project README:
  • Explain that <NuxtLink> should only be used to link to migrated Vue pages.
  • Explain that standard <a href="..."> tags (or <NuxtLink external>) must be used when a Nuxt page links to a legacy 11ty page, forcing a hard browser navigation.

Acceptance Criteria

• 11ty and Nuxt look visually identical using the exact same CSS files.
• Developers have clear documentation on how to link between the two systems safely.

Acceptance Criteria

No response

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate