Summary
Migrate the site from Netlify to Vercel, and drop the Jekyll dependency entirely in favor of a zero-build static deploy.
Context
The site is currently deployed via Netlify, which auto-detects Jekyll from the Gemfile and _config.yml, runs jekyll build, and serves _site/ from the main branch. There is no netlify.toml — everything is inferred.
However, Jekyll is only used to render supporters.md via _layouts/supporters.html. Everything else (index.html, 404.html, images) is already fully static. The deployment architecture check (.continue/checks/deployment-architecture.md) already anticipates this migration.
What needs to happen
Why
Vercel with zero-build static deploy is simpler, removes the Ruby/Jekyll dependency entirely, and aligns with the site's philosophy of resisting unnecessary complexity.
Summary
Migrate the site from Netlify to Vercel, and drop the Jekyll dependency entirely in favor of a zero-build static deploy.
Context
The site is currently deployed via Netlify, which auto-detects Jekyll from the
Gemfileand_config.yml, runsjekyll build, and serves_site/from themainbranch. There is nonetlify.toml— everything is inferred.However, Jekyll is only used to render
supporters.mdvia_layouts/supporters.html. Everything else (index.html,404.html, images) is already fully static. The deployment architecture check (.continue/checks/deployment-architecture.md) already anticipates this migration.What needs to happen
supporters.mdto static HTML (or convertsupporters.mdto a self-containedsupporters.html)Gemfile,Gemfile.lock,_config.yml,_layouts/)amplified.devcustom domain to Vercelllms.txt,robots.txt,sitemap.xml) work correctlyREADME.mdto reference Vercel instead of Netlify and remove the Jekyll development instructionsWhy
Vercel with zero-build static deploy is simpler, removes the Ruby/Jekyll dependency entirely, and aligns with the site's philosophy of resisting unnecessary complexity.