How SystmNews and Content work together to publish useful guides

Separate the writing workflow from the reading experience

SystmNews is the public reading experience for system updates, practical workflows, and field guides. The Blog plugin presents the article index and individual article pages. Content manages the article records themselves: titles, summaries, body text, draft or published status, and publication timing. Keeping those responsibilities distinct lets editors work on an article without making every saved change immediately public.

The public index asks Content for published articles. A scheduled article becomes eligible for display when its publication time arrives; a draft remains out of the public list. Opening an individual article also uses the published-content service, so an unpublished slug does not become public simply because someone knows its address. The index is intentionally bounded to a recent set of articles, with the newest available items first.

A practical editorial handoff

Start by agreeing on the reader, the problem the article helps with, and the plugin behavior that can be verified. Draft the headline and summary, write the article in Content, and keep it in draft while product claims and links are reviewed. Add a permitted hero image only when it is ready. An editor can then choose whether to publish now or schedule the article for a later time.

For this first SystmNews series, the plugin articles are being prepared as drafts. They are not public yet. When each article is approved, the Blog presentation can place it in the public index and provide its own article page; the editorial record remains managed through Content.

This workflow supports review and publication control. It does not automatically verify product claims, create a LinkedIn post, or distribute an article to other channels.