Restyle AS208437 site to match HyperBit Website-New design system

[francescomasala]

Summary

• Restyle the AS208437 public site to match the visual language and stack of HyperBit-IT/Website-New: dark theme, grid background, Poppins/JetBrains Mono, coral accent, subpage/panel/data-table patterns.
• Add Tailwind CSS 4 and the fontsource font packages, aligning core tooling versions (SvelteKit, Svelte, Vite, TypeScript) with Website-New. Kept adapter-static since the Azure Static Web Apps workflow expects a static build/ output.
• Kept all existing public information (ASN, prefixes, peering policy wording, reserved rights, contacts) — nothing removed, only reformatted.
• Enriched the technical content (upstreams table, IXP presence, RPKI/DDoS highlights, resource links) using data already published on the sibling Website-New repo's /rete page (MINAP Milano, RETN/Navigabene/Hurricane Electric upstreams, monitoring coverage), for a more technical NOC-style page as requested.
• Replaced the generic InfoCard/PrefixCard components with SiteNav/SiteFooter plus data-table driven sections (upstreams, prefixes, IXP presence).

Test plan

• npm run check — 0 errors/warnings
• npm run build — builds successfully with adapter-static
• Verified homepage and /peering-policy render correctly in a headless browser at desktop and mobile viewports (tables scroll horizontally on narrow screens instead of wrapping mid-word)

---

Generated by Claude Code

[francescomasala]

CI failure investigated — it's not caused by this PR's changes.

The Build and Deploy Job fails ~21s in, before any npm install/build of the site even runs, with:

The content server has rejected the request with: BadRequest
Reason: No matching Static Web App was found or the api key was invalid.

This happens inside the Azure/static-web-apps-deploy@v1 action itself, during its initial auth/validation step against the Azure backend — it never gets to building the app. Checking the workflow's run history on main, the last successful run of this exact workflow (azure-static-web-apps-polite-mud-07f02c503.yml) was a push back on 2026-03-20; I don't see any successful pull_request-triggered runs for it since.

This points to the AZURE_STATIC_WEB_APPS_API_TOKEN_POLITE_MUD_07F02C503 repo secret being stale/rotated, or the underlying Azure Static Web App resource having changed — something that needs to be checked/fixed in the Azure portal and GitHub secrets, which I don't have access to. Not something I can fix from the codebase.

I confirmed the app itself builds cleanly (npm run check and npm run build both pass locally on this branch), so once the Azure token/resource is sorted this should deploy fine.

---

Generated by Claude Code

[francescomasala]

Pushed a follow-up commit: switched the deployment target from Azure Static Web Apps to Coolify, matching Website-New's pattern.

• svelte.config.js now uses @sveltejs/adapter-node instead of adapter-static
• Added a multi-stage Dockerfile (node:22-alpine build + runtime, PORT/HOST env, node build entrypoint) and .dockerignore, mirroring Website-New's Dockerfile
• Removed the Azure Static Web Apps GitHub Actions workflow (the one failing earlier due to the stale/invalid deploy token) — there's no GitHub Actions build step anymore since Coolify builds/deploys the container itself
• Verified locally: npm run build succeeds with adapter-node, and node build (the same command the container runs) serves both / and /peering-policy correctly. I couldn't run docker build in this sandbox (no Docker daemon available), but the Dockerfile is the same verified pattern already in production for Website-New.

This repo has no CI workflow left to watch (Coolify builds happen outside GitHub Actions), so there's nothing further to monitor here from CI unless one gets added.

---

Generated by Claude Code

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.