Teyvat Center
A content site built from scratch and shipped on its own domain: Astro for static generation, Pages CMS for backend-free editing, deployed on Netlify with DNS on Cloudflare. No cookies, no analytics, no third-party resources — and a deploy that only runs when you actually ask for it.
Challenge I solved
Netlify moved to credit-based plans: every production deploy costs 15 of the 300 monthly credits on the free tier, and every CMS save is a commit that triggers a build — twenty saves would have burned through the whole month. The fix is an ignore script that cancels builds for ordinary pushes, at zero cost: deploys only run on request, via a tag in the commit message or Netlify's build hook.
Why I built it
Teyvat Center collects Italian-language guides and analyses of Genshin Impact characters. Theme aside, for me it was the proving ground for a specific idea: a fully static content site where writers work from a CMS without needing to know what git is, and where “no tracking” isn’t a line in the privacy policy but a technical guarantee. The site uses no cookies, no analytics and no third-party resources, and the Content Security Policy set in the response headers blocks any request to external domains: if something ever tried to call out, it simply wouldn’t work.
Deployment: Netlify and the credits problem
The site is published on Netlify, connected to the GitHub repository: the
whole configuration — build command, security headers, cache rules — lives in
a single netlify.toml versioned alongside the code. The domain is registered
on Cloudflare, which acts purely as registrar and DNS here (proxy off):
Netlify already has its own CDN and issues and renews the HTTPS certificate on
its own.
The knot to untangle came with Netlify’s credit-based plans: every
production deploy costs 15 of the 300 monthly credits included in the free
tier. Trouble is, every CMS save is a commit, and every commit used to trigger
a build: twenty saves — a normal writing session — and the month was gone. The
solution is one ignore line in netlify.toml: builds for ordinary pushes
get cancelled, and a cancelled build costs nothing. When the content is ready,
the deploy is launched deliberately — with the [deploy] tag in the commit
message, or via the build hook, which always bypasses the script. The result:
dozens of saves a day, a single deploy when it matters.
Why Pages CMS
Pages CMS is the choice that holds everything else together. It’s a hosted app (app.pagescms.org): nothing to install in the repository, nothing to run on a server, no API keys. It connects to GitHub through a GitHub App and writes Markdown files straight into the repository — every save is a commit, so the full editing history is git’s, for free. The site stays completely static: no serverless functions, no authentication endpoint, no database to maintain or defend.
The editing interface builds itself from a single YAML file in the repository: structured fields, repeatable lists, drafts, and cross-collection references that become dropdown menus in the CMS — writers pick from a list instead of typing free text, and typos disappear at the root. A verification script keeps the CMS schema and the site schema aligned, so a field added on only one side can’t break things silently.
Tech stack
The site is built with Astro in static output: every page is an HTML file, served from the CDN with no unnecessary JavaScript. Content lives in content collections typed with TypeScript and validated at build time: a wrong reference doesn’t produce a broken page, it stops the build with a message listing the allowed values. The interface uses Tailwind CSS with Starwind components adapted to the site’s design, and a set of Node scripts keeps the game data registries up to date from public APIs without ever overwriting manual corrections.