Editorial-grade docs for the HermesAI platform
The operating manual for an AI newsroom built for modern media.
This wiki mirrors the current HermesAI product shape, runtime, and operational boundaries. It exists so engineers, operators, and product teams can work from the system that actually exists today, not an aspirational future.
Coverage
Tenant newsroom
Feed, story workspace, editorial board, monitoring, and settings — documented as one compact newsroom workflow.
Platform operations
Provider governance, queues, costs, deliveries, and cross-tenant admin surfaces stay separate from the newsroom UI.
Runtime + integrations
The hybrid Next.js, AI SDK, Drizzle, Redis, webhook, and WordPress boundaries — described from the current codebase, not guesswork.
Why this exists
HermesAI already has real product depth. The docs need to show the settled route model, the current platform boundaries, and the verified operational commands — not hand-wave toward a vague future version.
Start at the documented system, then expand with evidence.
01 / Getting started
Sign up, run onboarding, find your first feed.
Account, publication identity, vertical, and the path from a fresh workspace to your first localised draft.
02 / Newsroom
The daily editorial work.
Feed, story workspace, editorial review, monitoring, and publishing — what every reporter and editor does day to day.
03 / Roles
Who can do what.
Owners, admins, members, viewers — and the four newsroom titles. What each role can and cannot do.
Next.js 16 application shell and route model
AI provider modes, model routing, and runtime policy boundaries
Postgres + Drizzle durable state and Redis-backed runtime state
Webhook handling for billing and identity providers
Source catalog build, validation, and sync workflow
WordPress connector behavior and plan gating
Pricing, public-site trust pages, and commercial posture
Documentation paths to keep in sync as the product evolves
04 / Documentation stance
No shipcopter docs.
This site documents the HermesAI that actually exists today: the Next.js 16 application, the tenant and admin route split, the AI runtime policies, the catalog pipeline, the webhook flows, and the integration surfaces already in the codebase. When the product changes, the docs change in the same wave.
Use product docs for UX and role boundaries.
Use architecture docs for persistence and runtime truth.
Use operations docs for setup, webhooks, and catalog workflows.
Use commercial docs for pricing and public-site posture.
Open the documentation and start from the real system.
Use the quickstart if you are setting up the app, or jump straight into the product and architecture sections if you are making changes.