Interactive graph
Building a Personal API
- Personal API
- PKM
- Automation
- Second Brain
- AI
- Knowledge Management
- Static Site Generator
- Documentation
- Future of PKM
- Trends
- Tools
Table of Contents
Frontmatter and folders shaped so future you and scripts need no fresh briefing every time.
Key Concept
- My personal API is not OAuth and microservices.
- I shape frontmatter and folders so future me and my scripts do not need a fresh briefing every time.
- Frontmatter and folder shape are the contract between past me and future me.
- Consistent slugs and fields let agents and scripts read the garden without a tour.
Level 1 - Recognize
A personal API is a consistent set of fields, names, and folders that people and tools can read without a fresh briefing.
Level 2 - Explain
The shared shape acts as a contract between past work and future use, making notes predictable to scripts and agents.
Level 3 - Use
Choose one slug pattern and frontmatter shape, then use them on every new note.
Level 4 - Connect
Consistency improves reuse but adds rules to maintain; change the contract carefully because old notes and scripts may depend on it.
Level 5 - Create
Extend the contract with one useful field, migrate existing notes, and prove a script can use it without special cases.
Examples
- Our pantry uses the same rule - snacks, baking, breakfast - my wife finds the rice without me re-explaining where everything lives.
- Our team names drills the same way every season - level, skill, variation - so a sub can run practice without a twenty-minute briefing.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Local-first Software | Structured API vs plain files when sync layers multiply |
| contradicts | Digital Minimalism | when structured context beats fewer moving parts |
| extends | Metadata Strategy | Consistent frontmatter turns your notes into something tools can read without you re-explaining |
