Documentation

Building a Personal API

Building a Personal API

My personal API isn't OAuth and microservices. It's structured context for future me and my tools without re-explaining everything.

Collaborative Knowledge

Collaborative Knowledge

Most of my notes are solo. But teams need shared context too - here's what I look for when knowledge has more than one author.

Formatting for Readability

Formatting for Readability

Dense walls of text don't get reread. I format notes like I'd format a post - headings, bullets, bold for the point.

Future-Proofing Knowledge

Future-Proofing Knowledge

Future-proofing isn't predicting tech for me. It's plain text, open tools, and exports I test before I need them.

Metadata Strategy

Metadata Strategy

Tags, categories, dates, aliases - metadata should help me find notes, not become a second job.

Consistent AI Output for WordPress Builds

Consistent AI Output for WordPress Builds

Month one with AI on WordPress builds I was thrilled. Month three I finally got consistent output - helpers, reference examples, and a short rules doc that stop every feature from drifting.

Categories
Tags