Forge CMSForge roadmap — v0.5.0:
✅ M1 — Core: lifecycle, auth, signals, storage
✅ M2 — App bootstrap: forge.New, graceful shutdown
✅ M3 — SEO & Head: JSON-LD, sitemaps, robots
✅ M4 — Templates: html/template, forge:head
✅ M5 — Social & AI: OG, Twitter, llms.txt, AIDoc, RSS
🔲 M6 — Cookie compliance
🔲 M7 — Automatic redirects
🔲 M8 — Scheduled publishing
🔲 M9 — v1.0.0
🔲 M10 — MCP: AI agents read/write natively
5 milestones. 6 days. Zero deps.
→ https://github.com/forge-cms/forge
#ForgeGo #ForgeAI #golang
Why did I build Forge?
Developers are tiptoeing around AI — not fully trusting it
to build, not committing to AI builds, human reviews.
The bottleneck isn't capability. It's tooling not designed
for AI as the primary builder.
Forge is built for that reality. One right way to do
everything. Declarative intent. All context available.
An agent reading a Forge codebase can improve it without
breaking it. That's the goal.
→ https://github.com/forge-cms/forge
#ForgeGo #ForgeAI #golang #go #ai
Developers are tiptoeing around AI — not fully trusting it
to build, not committing to AI builds, human reviews.
The bottleneck isn't capability. It's tooling not designed
for AI as the primary builder.
Forge is built for that reality. One right way to do
everything. Declarative intent. All context available.
An agent reading a Forge codebase can improve it without
breaking it. That's the goal.
→ https://github.com/forge-cms/forge
#ForgeGo #ForgeAI #golang #go #ai