$ ls projects/
A selection of things I have built or am currently building. Code, links, and short writeups where they exist.
A short, one-line description of what this thing does and why anyone should care.
A longer paragraph explaining the project: what problem it solves, the interesting technical decisions, what you learned, and what state it is in today. Two or three sentences is usually plenty.
Another project description. Replace this with something real.
Frame the project around an outcome — "cut p99 latency from 800ms to 90ms" reads better than "rewrote the cache." Numbers, context, and tradeoffs do more for a reader than feature lists.
An older project you still want to mention.
Old projects worth keeping are usually the ones that taught you something or pushed an unusual idea. Say what that was.