Give the artwork a purpose
The starting point was a cyberpunk homepage image. A later workstation-focused version created room for the site’s central idea: helping readers understand and control their technology. The visual carries the atmosphere; ordinary page text carries the message.
Keep the architecture small
The site uses static HTML, shared CSS and a small amount of JavaScript. Navigation and articles work without an application server. Repeated elements are generated from one layout, and the guide library reads from a single content file. A guide can be updated without hand-editing its homepage card.
Make the tool useful without an account
The checklist stores only the identifiers of completed steps in browser storage. It does not ask for passwords, account names or personal notes. A reset button removes its saved progress. If storage is blocked, the checklist continues working for the current visit and explains the limitation.
Treat content and experiments differently
The reference guides link to official documentation and explain the scope of each task. They do not claim that a personal cloud or local AI system has been deployed in this lab. This build note describes the publication itself; future experiment reports should include the actual setup, observations and limitations.
Keep changes reversible
The previous homepage was preserved before replacement. Website releases can back up the files they touch while leaving older media and unrelated directories in place. Smaller, explicit changes make it easier to review the result and restore a previous version if needed.