Publishing Flow

This covers the manual publishing path — an editor creates an article in the dashboard and publishes it to one or more child sites.

Steps

1. Create — Editor opens /articles/add and fills in title, body (via CKEditor), tags, category, and section.

2. Save — Dashboard calls POST /api/v1/article. The article is stored in MongoDB with a status of draft.

3. Assign sites — Editor selects which hosted sites should display this article. Dashboard calls POST /api/v1/article/host-site/:id.

4. Publish — Editor clicks Publish. Dashboard calls PUT /api/v1/article/publish/:id. The article status changes and it becomes available on the client API.

5. Child sites display it — Any child-site frontend polling GET /api/v1/client/posts will now include this article in results.

Tag-Based Routing

Note

Articles are routed to child sites based on tag matching. An article with tag bitcoin will only appear on sites configured to receive bitcoin content.

Key API Endpoints

Method	Endpoint	Purpose
POST	/api/v1/article	Create new article
PUT	/api/v1/article/:id	Update article
POST	/api/v1/article/host-site/:id	Assign article to hosting sites
PUT	/api/v1/article/publish/:id	Publish article
GET	/api/v1/client/posts	Child-site reads published articles