Help Center/Admin Operations/Write, schedule and archive articles in Articles & News
Admin Operations•Last updated: 2026-10-20•5 min read

Write, schedule and archive articles in Articles & News

Articles & News stores long-form articles and news posts in the database. An article moves DRAFT, IN_REVIEW, SCHEDULED, PUBLISHED, ARCHIVED; archiving is the only removal.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

In the admin sidebar open "Universal Studio" then "Articles & News" (/admin/studio/articles). The tiles count Drafts, In review, Scheduled, Published and Archived articles from the database. An empty table means no article has been written yet.

2

Create a draft

Click "New Record". Enter a Title (required) and optionally a Slug (lowercase letters, numbers and hyphens; made from the title when blank, and fixed afterwards), a Summary (up to 500 characters), the Body, comma-separated Tags (up to 12) and a Cover image (a Media Library link such as /api/v1/media/med_... or an https URL). Click "Save Record". The article is saved as a DRAFT and you are recorded as its author; a slug already in use is refused.

3

Edit and move it

Click the pencil on a row. Change any field and/or choose "Move to". Allowed moves: DRAFT to IN_REVIEW; IN_REVIEW to SCHEDULED, PUBLISHED or back to DRAFT; SCHEDULED to PUBLISHED or back to IN_REVIEW; any status to ARCHIVED; ARCHIVED back to DRAFT. A move the lifecycle does not allow is refused with the reason.

4

Schedule it

Choose "Move to" SCHEDULED and enter "Schedule for" as an ISO date and time in UTC in the future (for example 2026-11-01T09:00). To go live an article needs a title, a summary and a body of at least 20 characters. Nothing publishes by itself when the time comes: use the Publishing page.

5

Archive it

Click the trash icon, give a reason (at least 5 characters) and confirm. The article is archived, not deleted; its history stays. Edit it and "Move to" DRAFT to restore it.

Expected Operational Outcome

The article appears with its new status after each save, and every change is kept in its history (shown on the Publishing page).

Troubleshooting & Failure Modes

Symptom: The page says tables are not created
Likely Cause: The database tables for the Studio consoles have not been applied in this database.
Resolution: An operator runs "npm run db:apply:studio". Until then the page is read-only.
Symptom: Members cannot see a published article
Likely Cause: There is no public articles page in this build; Articles & News stores and manages articles only.
Resolution: Do not announce a published article as visible to members; a public page has not been built.

Was this guide helpful?

Help us refine our platform documentation