Stack Principles


<2021-11-09 Tue>

The blog comprises solely of static pages: there is no form of server-side or client-side execution whatsoever. Pages are treated as documents to be read, not applications to be interacted with.

This approach will throw everyone back into the stone age, although it comes with a few nifty technical and philosophical advantages. In essence, simplicity should be one of the pillars of craftsmanship. It must be striven for as much as practically feasible.


Everything can be cached, and no unnecessary resources are wasted to serve these words. The verbosity of these paragraphs may contradict the aforementioned efficiency, however.

The more resources we have available, the more we take them for granted, and thus the more wasteful we become. Resources should be used to their fullest through efficient diversity; that is, multiple projects should each consume available resources as necessary.

The opposite would be one project taking up all of the available resources, without any practical benefits. Unnecessary monopolisation of resources is detrimental to the quality of the project, and also detrimental to the potential of other projects.


It's accessible and customisable. Almost any device and browser should be able to access these posts without any complications. A budget phone in a rural area shouldn't be prevented from reading these idealistic paragraphs, and the same applies for screen readers or terminals.

The HTML is semantic, styling is minimal, and scripting is non-existent. The latter should most definitely please the lads and lasses whom are vocally opposed against the ever-increasing intrusiveness and complexity of the modern web.

Because of the simplicity, it's possible for you to tweak the presentation. Whether you want to toggle your browser's reader mode, or apply your own CSS on top, it's all easily doable. This flexibility is presented as a feature, but in reality, it's simply a byproduct of keeping things as mundane as possible.


Each page should be self-contained as much as possible. This includes having the styling embedded right into it, instead of a CSS file being referenced. At most, only media assets should be referenced instead of being embedded onto the page.

This adds a bit of sanity as far as HTTP requests and file management goes. Compression and disk de-duplication will compensate for the repetitive data across the pages. The scenario where the CSS needs to be updated is also taken care of. This is accomplished by simply regenerating all of the HTML pages from the original text files.