Dossier goal
Show that this site, while visually sober, is engineered and operated with production discipline: automated quality, observability, security, traceability, and controlled maintenance.
Website engineering
Public documentation of the technical layer that makes elmst.ibaifernandez.com robust internally.
Architecture and hosting
Static HTML/CSS/JS website deployed on Netlify, with serverless functions for runtime config, captcha verification, and contact submit.
- Hosting: Netlify with production domain
elmst.ibaifernandez.com.
- Functions:
runtime-config, verify-turnstile, submit-contact.
- Routing/hardening:
_redirects, _headers, netlify.toml.
Quality and CI
Blocking pipeline in GitHub Actions: if one check fails, quality gate fails.
- Playwright E2E for critical routes and contact form.
- Desktop/mobile visual regression with versioned baselines.
- Automated accessibility with axe.
- Lighthouse CI + route budgets + release report snapshots.
Security
- CSP/HSTS/X-Frame-Options headers and mixed-content controls.
- Invisible Turnstile captcha with server-side verification.
- Honeypot + strict backend field validation.
- No legacy PHP backend in production.
Technical SEO and i18n
- ES/EN versions with page-level
hreflang and canonical.
- Sitemap and robots aligned with production domain.
- Route-level OG/Twitter metadata.
- Controlled legacy compatibility with explicit redirects.
Observability and uptime
- Sentry for frontend error tracking by environment.
- UptimeRobot monitoring production HTTP availability.
- P1/P2/P3 alerting and incident runbook documented.
Continuous operations
- Manual quality gate + weekly scheduled execution.
- Versioned technical report for every release.
- Monthly manual QA checks in CSV (desktop/mobile).
- Backlog and roadmap refreshed every iteration.
