Admin roadmap

The admin area should become a real control plane: protected, auditable, analytics-aware, and still manual by default until the workflow is proven.

What is already in place

What must come next

  1. Protect /admin/* with Cloudflare Access before exposing it publicly.
  2. Add protected manual webhook triggers for run-loop and deploy actions.
  3. Connect Cloudflare analytics and request-log classification for human versus crawler reporting.
  4. Add article-state transitions with audit history: draft, review, approved, published, corrected.

Traffic plan

Human traffic should come from Cloudflare Web Analytics. Crawler traffic should come from server-side request classification, not client-side code.

Publishing policy

Keep publishing manual until review actions, logs, and protected controls are fully in place. The right sequence is manual terminal control, then manual n8n, then authenticated UI triggers.