ContentForge started as an attempt to replace scattered content spreadsheets with one workflow that teams could actually operate.

The Backstory

Many content teams still manage keyword ideas, briefs, drafts, approvals, publishing, and refresh timing across disconnected tools. We wanted a system that kept those states together instead of turning every batch into another spreadsheet exercise.

So the product grew around projects, matrix rules, section-based drafts, publish targets, and refresh windows.

Our Engineering Philosophy

Instead of treating content generation like a single prompt, ContentForge separates discovery, structure, drafting, editing, linking, and publishing into explicit steps. That makes the workflow easier to inspect, review, and improve over time.

How We Describe the Product

Implemented workflows only

No placeholder product claims

Public copy is meant to describe routes, automations, and integrations that exist in the codebase today.

Review before publish

Automation with editorial control

The system helps generate and organize work, but useful content still depends on good inputs and thoughtful review.

Current Scope

Today the product centers on projects, matrix generation, AI drafting, WordPress publishing, Stripe billing, and Brevo-backed notifications. If new public capabilities are added, this page should expand only after the underlying workflow ships.