Idea Papers

About

A library, not a feed

Idea Papers collects ideas, papers and working notes about technology, architecture and digital transformation — and, more importantly, the connections between them.

What this is

Most writing about technology is published on blogs that are organised by date. That ordering is chronological, not intellectual: it tells you when something was written and nothing about whether it is still believed. This is an attempt to keep a body of thinking in a shape that survives revision.

There are three kinds of content, and they are deliberately different. Papers are long arguments that have been thought through properly. Ideas are shorter: a question, a suspicion, a position that is still being tested. Research notes are working material — reading notes, comparisons, summaries of standards — kept close to the papers that rely on them.

Everything is classified by topics and finer-grained tags , and connected to related work through declared relations. Those relations are the part that matters: a paper is only as good as the ideas and evidence it sits between.

The shape of the library

papers
02
ideas
00
research notes
00
references
33
topics
09

The knowledge graph is the same library seen as relations rather than as pages.

How it is built

Every piece of content is a file in a Git repository. There is no database, no authoring interface beyond a text editor, and no content that exists only on a server. The site is compiled to static HTML and served by Nginx behind Docker; the only thing that runs in a visitor’s browser is the search interface, the diagram renderer, and the graph.

Relations between documents are declared once, in frontmatter, and resolved at build time. A relation that points at something that no longer exists disappears quietly rather than producing a broken link. The graph and the “referenced by” lists are two views of that same resolution.

Framework
Astro — static output, no server runtime
Language
TypeScript, strict
Content
MDX and Markdown, committed to Git
Styling
Tailwind CSS with design tokens in custom properties
Search
Pagefind — an index built from the rendered HTML
Code
Shiki, dual light/dark themes
Diagrams
Mermaid, rendered in the browser on demand
Maths
KaTeX, rendered at build time
Storage
None. A relational database would be a liability at this scale

Who writes it

ThePocket006 works on enterprise architecture, cloud and security — mostly on the problem of making large information systems simpler than they naturally want to be. The writing here is personal: it is not a company position, it is not a product, and it is often the case that a piece is published before the argument is settled.

Papers carrying a Draft or Exploring status are honest about that. Nothing published here is finished in the sense that it will never change; the last updated date is on every page for exactly this reason.

Contact

Corrections, disagreements and pointers to things worth reading are welcome. The most reliable route is email: [email protected].

Type to search