Content Roadmap
> Evergreen content that builds long-term authority.
> Last updated: 2026-07-24
---
Now (Q3 2026)
| Piece | Type | Effort | Links To | Status |
|---|---|---|---|---|
| Agent Programming Guide from Interface Notions | Technical guide | Medium | Opportunity #1 | Not started |
| How Seed Enables Web of Trust | Platform case study | Low | Graduated Trust, Seed primitives | Not started |
| Content-Start Alignment: Design Principles | Design doc | Low | Editor rendering fix | Not started |Next (Q4 2026)
| Piece | Type | Effort | Links To | Status |
|---|---|---|---|---|
| State Machines for Agent Orchestration | Long-form article | Medium | Agent guide, doc machine | Not started |
| From Deploy to Own: Forking Seed | Tutorial | Low | Deploy from fork guide | Not started |
| Performance Manifesto | Essay | Medium | Electron tRPC, editor fixes, startup | Not started |Later (2027)
| Piece | Type | Effort | Links To | Status |
|---|---|---|---|---|
| State Machines Video Course | Video series | High | Content hub | Not started |
| Document Machine OSS Package | Code + Docs | High | State machine brand | Not started |
| Building on Primitive: The Seed Platform Philosophy | Long-form essay | Medium | Graduated Trust, capabilities | Not started |---
Guiding Principles
Evergreen first — every piece should be as relevant in 2 years as today
Compound across projects — each piece should reference and strengthen previous work
Distinctive positioning — avoid generic "how to use React" content; focus on what only this author can say
Seed-adjacent — content should either directly help Seed or establish credibility that reflects well on Seed
Recurring Content Types
Weekly Reviews — regular progress documentation (existing pattern, continue)
Short Posts — quick ideas, observations, external references (existing pattern, continue)
Tech Talks — deep technical analysis (existing pattern, continue)
Recently Published
Deploy a Seed Site From Your Own Fork — July 1, 2026
Interface Notions — component catalog
Notes about how the document machine should work — state machine spec
What I want for the commenting experience to be — UX requirements
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime