A content backend with a native AI interface. In fact, every interface.
Zero dependencies. No ambiguity.
https://github.com/smeldr/core
| github | https://github.com/smeldr/core |
| web | https://smeldr.dev |
We moved. Find us at @smeldr. Same product, sharper name.
smeldr.dev
Forge preview tokens are narrowly scoped. One token, one piece of content.
The link bypasses the Draft state for that item only. It does not expose any other drafts. Archived content does not get a preview.
Generate from the CLI, an MCP call, or an agent step. Valid for 12 hours by default.
forge.md is now in skills/. A complete working reference so your AI knows the Forge API before your first message.
Covers content type definitions, module wiring, routing variants, the signal bus, every MCP tool with its required role, and forge-social. The tricky parts are called out explicitly.
https://forge-cms.dev/devlog/forge-skill-public?utm_source=mastodon&utm_campaign=forge-skill-public
Share a draft for review before it goes live.
No staging URL that exposes everything. No account for your reviewer. One link, one piece of content, exactly as it will look when published.
When the link expires, it stops working. The rest of the site is untouched.
forge-agent v0.3.5 fixes a silent context cancellation bug on signal-triggered MCP connections.
The AfterPublish signal in Forge fires for every published item automatically. v0.3.5 ensures the agent reliably picks it up, reads the post body, and creates social drafts for operator review - no per-post webhook setup required.
AI agents guess at the Forge API and reset every session. Your team corrects instead of builds.
forge.md is now in the Forge repo. Add it and your agent knows content types, routing, MCP tools, and the signal bus before you write a line. Four skills now ship with Forge.
https://forge-cms.dev/devlog/forge-skill-public?utm_source=mastodon&utm_campaign=forge-skill-public
Your AI can now design the pages for your content types.
Describe what the page should look like. Forge gives the design tool your content structure and sample data. Claude Design or Google Stitch returns production HTML and CSS - no developer writing markup by hand.
The workflow is documented and the skills are in the repo.
https://forge-cms.dev/devlog/ai-design-workflow?utm_source=mastodon&utm_campaign=ai-design-workflow
Forge turns the post-to-social workflow into a typed pipeline with a human review gate at every step.
When a devlog goes live, an AfterPublish signal fires automatically. An agent reads the post via MCP and creates draft scheduled posts - never publishes directly. The operator reviews, adjusts, and schedules.
Most orchestration frameworks need a graph defined upfront. In Forge, the
workflow is the set of published agent jobs and their content type subscriptions.
To add a step: publish a new agent job. To pause one: archive it. The workflow
itself is manageable as content.
forge.SingleInstance() and forge.Standalone() landed in v1.23.0, covering URL patterns the module system could not handle before.
SingleInstance() registers GET /{prefix} only and serves the first published record. Standalone() places items at /{slug} while keeping the list at /{prefix}. CRUD, lifecycle, and MCP tools are unchanged.
