No framework, no build server, no database. This is plain HTML, CSS and JavaScript on GitHub Pages — the same free static hosting anybody gets with a repository — and a pile of Python that writes the pages before they ship.
Every number below is counted from the repository when this page is built, not typed in. That is the rule the whole site runs on: if a figure is on a page, something measured it.
A post is a file. Everything a reader sees is built from it, which means the pages can always be thrown away and made again — and are, on every publish. Here is the whole trip a post takes, from the file to your screen.
The same trip, laid out at once: what is written by hand, what Python builds from it, what stands between the two, and what a reader finally opens. Every box names a real file in the repository — a check refuses this page if one of them stops existing.
scroll the diagram sideways →
7 of those 13 run on a clock, on GitHub’s machines rather than mine. They fetch, rebuild and commit on their own — the cloud pages are current whether or not I have opened a laptop. The rest run when something is pushed.
| Job | Does | When |
|---|---|---|
| doc-freshness | flag documentation going stale | Tuesdays, 07:00 UTC |
| health | rebuild the health report | daily, 13:00 UTC |
| ingest-news | ingest announcements, rebuild What’s new | daily, 05:10 UTC |
| refresh-aws-services | refresh the AWS service catalogue | Mondays, 06:00 UTC |
| refresh-events | re-import events from the vendors | daily, 05:40 UTC |
| status | fetch every cloud's incidents, rebuild Live status | every hour |
| verify-events | open every event link, reconcile what is missing | daily, 06:20 UTC |
53 checks, in a real browser, on every push. They do not read the code — they open the pages and look: does the header hold still, does the music button actually play, does a filter filter, does every link still resolve, is each page asking for the current stylesheet. If one fails, the push is refused. It costs about twelve minutes, which is the price of not finding out from a reader.
The terminal on the portfolio answers questions over these posts rather than from a model’s memory: the question is matched against what is actually written here, and the answer cites the post it came from. If nothing here covers it, it says so instead of inventing something.
Static files cannot be hacked through a plugin, cost nothing to serve, and load on a bad connection. Nothing here needs a server to be running, a subscription to be paid or a database to be backed up. In ten years these pages will open the same way, because they are just files.
The whole thing is public: github.com/katta698/katta698.github.io