Refine UX

[faktorial-ai]

Batch 1 - Page Inventory And Source Cleanup

The current site is a static Vite/React app. Public routes are driven by src/data/siteContent.ts, rendered by src/pages/SiteHomePage.tsx, and emitted as static route artifacts by vite.config.ts plus scripts/assert-static-routes.mjs. Keep the work scoped to the current Svärd Entreprenad site and do not preserve Eriksson & Svärd links as customer-facing UI.

• Inventory every current public route and record the page purpose, visible sections, and missing page-specific visual assets for /, /tjanster/, /om-oss/, /stensattning/, /markarbete/, /gravjobb/, /dranering/, /tradgardsplanering/, and /kontakt/.
• Remove or replace all customer-facing Eriksson & Svärd / erikssonsvard references, source links, partner names, and tests that assert them, while keeping any historical notes only where clearly non-public and still useful.

Batch 2 - Page-Specific Visual Asset Model

Add a lightweight content model for page visuals before wiring UI. Prefer generated placeholder photos or image slots that clearly represent Svärd Entreprenad work categories and can later be replaced with real photos without redesigning the page.

• Add route/service image metadata to the static content/types so each public page has an explicit visual asset, alt text, and page-appropriate intent. Cover home, services index, about, contact, and each service page.
• Create or add generated placeholder image assets under public/ for the current route inventory, using filenames and alt text tied to the actual Svärd Entreprenad page topics rather than the old source company.

Batch 3 - UX Wiring And Verification

Once the content model and assets exist, wire them into the real pages with responsive, polished layouts. Avoid adding a marketing-only landing layer; the first screen should remain the usable site experience.

• Render the page-specific images in src/pages/SiteHomePage.tsx across home, listing, service, about, and contact surfaces with stable responsive dimensions, accessible alt text, and no layout shifts.
• Update tests to assert route coverage, image/alt coverage, absence of old-company references, and static route artifact generation for the refined UX.