← systems · level 2
serhiykucherenko.dev
A build step, not a server. Nothing runs when you read it.
publish line — from a commit to the page in front of you
- edita data file or a page, in the repoContent is typed data rather than a CMS. Adding an article is one line; there is no admin to log into and nothing to keep patched.
- pushto main, which is the only trigger
- buildevery page rendered to static htmlStatic over a server, so a bad deploy cannot take the site down: the previous build keeps serving.
- deployassets go to the edge
- readserved from the city nearest youNo trackers and no third-party scripts, which is most of why it loads the way it does.
runs on
Cloudflarebuild, host, dns, wafGitHubsource and the deploy trigger
- No database, no server, no tracker. A failed build keeps the previous version live.
- Articles are not stored here — the site links out to where each was published.