Articles Manager

The canonical article store for the CMS — one place where pipelines drop articles and the public site reads them back.

What It Does

Articles Manager unifies every article source on the site into a single backing store. AI pipelines, hand-curation, and imports all write here; shortcodes, home pages, and search all read here. You get a registry (admin/data/Articles/index.json) plus one JSON file per article, and an admin UI for CRUD, preview, and social sharing.

Getting Started

1. Open Articles Manager from the admin menu.
2. Browse the list to see what’s already published. The registry drives the public article listing URL.
3. Click an article to view, edit metadata, or open its public page.
4. Use the Share modal to push an article to social with pixel tracking attached.
5. To add new articles, run a content pipeline that targets this site — Articles Manager stores whatever the pipeline produces.

Storage Model

Each article is a JSON file under admin/data/Articles/ plus an entry in index.json. The index is the source of truth for listings. Archived articles move to _archive/ but stay readable. Because everything is flat files, articles survive any database-free restore and diff cleanly in git.

Pipelines Write, Manager Presents

Articles Manager doesn’t generate content — pipelines in AgentScheduler do that. The clean split: pipelines produce, Articles Manager stores and presents. If an article looks wrong, check the pipeline’s output first; if it’s missing from the public listing, check that the registry got updated.

Social Share & Tracking

The share modal generates social-ready links with tracking pixels so you can measure click-through. Use it to distribute new articles without hand-crafting URLs.

Gotchas / Tips

• Additive only. Never overwrite index.json — append. A pipeline that resets the index wipes history.
• Verify visibility. After a pipeline run, open the public article-listing URL and confirm the new piece is there. Don’t trust the data layer alone.
• Article JSON files must have matching entries in index.json or they won’t show up on the public listing.
• Do not hand-edit index.json to delete articles — use the admin UI so the article file moves to _archive/ cleanly.
• Content-gen failures silently produce empty articles sometimes. Always eyeball new entries before calling a run successful.