Case study · dylanseybold.com
Real routes, honest copy, no fake delivery.
This is my own site — not a client NDA project — but it is representative of how I build marketing sites and personal brands when the goal is trust and search clarity, not hype.
ProblemSeptember 2026 audit
The site shipped as one HTML file with CSS hiding inactive “pages.” Only / was a real file; /about depended on host rewrites. On production, a redirect sent refreshes back to Home — bad for bookmarks, press links, and Google.
Approachstatic-first
- Single source
_src/site.htmlcompiled by zero-dependencybuild.mjsinto one HTML file per public route - Each URL returns its own title, description, canonical, and visible content on first paint — no SPA fallback that turns 404s into Home
- Progressive enhancement router: fetch + swap for smooth transitions; full page load still works without JS
- Prelaunch ventures labelled consistently — no “live product” language where only a waitlist exists
- Contact: Formspree when a form ID is configured at build time; transparent mailto fallback otherwise
- Regression tests on generated output (routes, stale pricing removal, press assets, form behaviour)
Outcomeswhat improved
- /about (and every route) is a standalone document — refresh and share links work
- Sitemap and JSON-LD Person graph aligned with CEO positioning and real social profiles
- Press kit: bios, headshot download, appearances list (empty until coverage exists), interview CTA
- Projects page links to mysticonnect.com, purepawraw.com, Hollistic-Connect, and dibbles0910 with “what exists today” lines
- Deployed on Cloudflare Pages with production branch discipline
Stacksame family as freelance site work
Node build script, semantic HTML/CSS, minimal client JS, Cloudflare Pages, Formspree optional — no framework churn for a site that needs to stay fast and maintainable.