Blog Pro
Blog Pro is a functional workspace over native WordPress posts — it does not replace the post model. Open CoreX → Blog Pro. The native front-end blocks (sharing, newsletter) require CoreX Email and CoreX Newsletter to be active.
Reading figures
Section titled “Reading figures”CoreX does not collect reading data yet. Nothing on the front end records a view or a read today, so Blog Pro shows one line saying so where its figures will go, with no panel and no period. When a later release records reading events and a post has some, the panel appears with its aggregates (views, reads, share clicks, unique visitors, average read time, read rate) and the period they cover.
The store those events will use is already in place, with privacy built in: collection is consent-aware, visitor identity is hashed (no raw IP address or user agent), and events are kept for 180 days.
Editorial workflow
Section titled “Editorial workflow”Each post carries an editorial state mapped onto native WordPress post statuses:
| Editorial state | Native status |
|---|---|
| Draft | draft |
| Ready for Review | pending |
| Needs Changes | draft |
| Approved | pending |
| Scheduled | future |
| Published | publish |
Transitions use wp_update_post() and record the assignee, due date, scheduled timestamp, and author-written
review notes. The post itself is never swapped for a custom model.
There is deliberately no transition graph: any state may follow any other, because which moves make sense is an editorial decision, not a framework one. The screen therefore offers every state except the one the post is already in. The single constraint is that Scheduled requires a date — the workspace asks for it before it will submit, rather than letting the request fail server-side.
Comments and authors
Section titled “Comments and authors”- Moderation queue — comments held for review, each showing its text, author, arrival time, and whether
it is a first comment or looks like spam. The workspace offers approve, mark as spam, and move to trash;
the service also supports
replyandedit, which the admin screen leaves to the native Comments screen. Everything runs through the native WordPress comment APIs. Actions are hidden — not disabled — from anyone withoutmoderate_comments. - Authors — real author users with true published-post counts.
The workspace has no Sharing card: it listed networks from a setting no screen changes, which the front-end share row does not read. The share row on a post shows its own networks.
The admin workspace
Section titled “The admin workspace”CoreX → Blog Pro works on one post at a time, and says which. Choose it from the selector; the choice is
the URL (?post=<id>), so a view can be linked, bookmarked, and reloaded.
Every panel is scoped to that post. Reading figures, once there are any, state the period they cover — a count without a window means nothing — and a genuine zero is shown as one.
Opening the screen needs edit_posts. Moving a post needs edit_post on it, and moderating needs
moderate_comments — where you lack one, the control is not rendered rather than shown and refused.
Native front end
Section titled “Native front end”The theme ships a complete native blog experience. The single-post template (theme/templates/single.html)
renders post meta, content, tags, and:
- the social share row (
corex/social-share), - a newsletter signup (
corex/newsletter-signup), - the native comment thread and reply form, and
- a More from the blog related-posts query.
The index.html and archive.html templates render a responsive post grid with excerpts, a no-results state,
and pagination.