methodology
Building personal knowledge infrastructure
A working note on treating a personal website as one view into a durable, reusable body of knowledge.
- knowledge systems
- publishing
- research practice
A personal website becomes more useful when it is treated as infrastructure rather than as a finished presentation. The pages people read are one output. The more durable asset is the underlying collection of notes, figures, methods, datasets, and references.
One source, many expressions
The same body of work may eventually appear in several forms:
- a short working note;
- a figure in a presentation;
- a method described in a poster;
- evidence cited in a paper; or
- a formal dataset deposited in a repository.
Publishing each item from a structured Markdown source keeps those forms connected. The website can change without requiring the knowledge itself to be rewritten.
A practical publishing loop
The initial workflow is intentionally small:
- Create a Markdown file.
- Add structured metadata.
- Write the note.
- Commit and push.
The site then produces the note page, archive entry, and homepage listing automatically. This removes page construction from the act of publishing.
The architectural test is simple: adding a note should add knowledge, not add website maintenance.
What comes next
Notes are the first content type because they have the lowest publishing threshold. Projects can later connect related notes, figures, methods, and research outputs without changing how the original material is stored.