Forge CMS

@forge_cms
0 Followers
0 Following
6 Posts

A Go CMS framework built for you and AI. Zero dependencies. SEO, AI-indexing, Social sharing and content lifecycle.

Zero dependencies. No ambiguity.

https://forge-cms.dev/

https://github.com/forge-cms/forge

githubhttps://github.com/forge-cms/forge
webhttps://forge-cms.dev/

Prompt that delivered real value today:

"Do any of these fixes reveal patterns worth reviewing across the existing codebase?"

Result: a structured audit that surfaced two silent failure patterns I wasn't looking for.

The best AI prompt isn't always the most sophisticated one. It's the one that asks the question you didn't know you needed to ask.

#ForgeGo #golang #ai

v1.0.0 is live.

Zero dependencies. Content lifecycle. AI indexing. Three example apps. 85%+ test coverage.

8 days from first commit to stable release — built with AI as the primary developer, not just a helper.

→ github.com/forge-cms/forge/releases/tag/v1.0.0

#ForgeGo #ForgeAI #golang

I'm not a pro Go dev: Classic ASP in the 90s → IT PM since 2005 → no full-time coding for 20 years. Learned Go last year with Claude Sonnet + Copilot. Result: Forge, a Go framework with built-in content lifecycle, SEO, auth & AI.
One declarative block = full CRUD, role-based auth, perfect SEO/JSON-LD, and gzipped AI endpoints. Next: MCP for safe agent read/write/publish.
Still early —feedback welcome from AI coding tool users!

🔗 Repo: github.com/forge-cms/forge

#ForgeGo #golang #BuildWithForge

Forge 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
GitHub - forge-cms/forge: The Go web framework designed for how you actually think.

The Go web framework designed for how you actually think. - forge-cms/forge

GitHub
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

Introducing Forge — a Go web framework where content lifecycle,
SEO, and AI indexing are built in, not bolted on.

One app.Content() call wires a complete content module: full
CRUD, role enforcement, event-driven sitemap, JSON-LD structured
data, HTML templates, and content negotiation across
JSON/HTML/Markdown.

Draft content never leaks — enforced by the framework, not by
convention. Zero dependencies. Go 1.22+.

WIP → https://github.com/forge-cms/forge

#golang #go #webdev #opensource