Context
We're approaching cutover from the Gridsome site to the Astro migration. Before switching, we need a manual QC pass on the highest-traffic pages to catch any rendering issues that automated tests might miss.
Pages are listed by visitor count (from Plausible analytics). For each page, compare the current production site against the Astro build and flag anything that looks off.
What to look for
- Broken or degraded layouts
- Missing or broken images
- Broken links
- Missing or garbled content
- Styling regressions (spacing, fonts, colors)
- Functional issues (interactive elements, navigation)
Top pages
Bare / embed pages
These pages are served inside Galaxy instances as iframes (welcome pages, embedded news/events). They have different layout requirements — no site chrome, just the content panel.
Context
We're approaching cutover from the Gridsome site to the Astro migration. Before switching, we need a manual QC pass on the highest-traffic pages to catch any rendering issues that automated tests might miss.
Pages are listed by visitor count (from Plausible analytics). For each page, compare the current production site against the Astro build and flag anything that looks off.
What to look for
Top pages
Bare / embed pages
These pages are served inside Galaxy instances as iframes (welcome pages, embedded news/events). They have different layout requirements — no site chrome, just the content panel.