Content Studio · Blog module · Design brief

Blog Automation Redesign — UX Spec

Designed by Jill
Jilly · Sage Coast Realty. Card-based pipeline, stage names, and button copy come from her live use of the platform, July 2026. This is her design, adopted as the Blog module brief.
Status: ✓ Adopted — module 1 of 8 Replaces: the current Blog Calendar table as the default landing page Answers: board item CS-222
Why this matters beyond the Blog page. Jill's design isn't just a Blog fix — it independently proves the redesign rules. Her card home is Rule 4 (navigation that matches itself). Her pipeline is Rule 2 (one status language). Her "no silent unscheduling, confirm first" is Rule 3 (nothing goes out by accident). Moving "Sync with WordPress" out of sight into Settings is Rule 1 (hide the plumbing). She got there from using the product, which is the strongest signal the rules are right. We build Blog to this spec, then reuse the same shapes across the other seven modules.

The pipeline at a glance

Create
how you start
My Drafts
write & polish
In Review
preview the live post
Schedule
pick a date, or go live
Published
live on the site
My Drafts write and polish In Review preview the live post Schedule or post now pick a date, or go live Scheduled goes live on its date Published live on the site Looks good, let's review it Looks great Schedule ahead Post now auto-publishes on its date Needs more work Needs more work (confirm first)

Every post sits in exactly one stage. It moves forward with one clear button — the user never touches a status dropdown. Backward moves are always confirmed, never silent.

1 · The problem

The current Blog Automation page is a power-user dashboard: stacked filter rows, six action buttons, and a dense data table. For the target customer — realtors, dentists, plumbers, people who don't do marketing for a living — this is intimidating and unclear. Users shouldn't need to understand "statuses" and "filters" just to publish a blog post.

2 · The core idea

Replace the table-first landing page with a card-based home screen built around a simple pipeline: Create → Draft → Review → Schedule → Post. Every blog post lives in exactly one stage at a time, and each stage is a card on the home screen. Posts move forward through a single clear button at the bottom of each screen. The user never touches a status dropdown.

3 · Home screen — five cards

CardWhat it holdsCount example
Create New BlogEntry point for all creation methods
My DraftsPosts being written or edited"11 in progress"
In ReviewPosts being previewed before approval"6 waiting on you"
ScheduledApproved posts queued for a future date"21 posts queued"
PublishedLive posts"4 live"

4 · Create New Blog — drill-in

CardFunction
YouTube to BlogTurn a video into a post (existing feature)
Article to BlogReframe an existing link (existing "Reframe a Link")
Create My OwnWrite from scratch
60-Day PlanGenerate a full content schedule (existing, relocated)
Import CSVBulk-import posts (existing, relocated)

All creation methods land the new post in My Drafts and open the Edit screen.

5 · The pipeline, screen by screen

5a · Edit screen (Drafts)

The existing editor — title, body, category, SEO, featured image. Bottom button: Looks good, let's review it moves the post to In Review and opens the Review screen. Posts can also be closed and left in My Drafts to finish later.

5b · Review screen (In Review)

A true preview: the post rendered exactly as it will appear on the live website — featured image, formatting, the works. Not the edit screen with toolbars hidden. This is the whole value of the step: "this is what your readers will see." Bottom buttons: Needs more work returns the user directly to the Edit screen for this specific post (not just the drafts list) and moves it back to My Drafts; Looks great opens the Schedule or Post Now screen.

5c · Schedule or Post Now screen

Post now publishes immediately and moves the post to Published. Schedule ahead lets the user pick a date/time and moves it to Scheduled. Scheduled posts publish automatically on their date and move to Published.

5d · Editing a scheduled post

Clicking any post in the Scheduled card reopens it in the Review screen with three context-aware buttons:

The payoff: users only ever learn one screen for "look at my post and decide what happens to it."

6 · Help chatbot NEW FEATURE

A chat widget pinned to the bottom of every page that answers "how do I use this?" — grounded in Content Studio's own help documentation, not general questions. It's context-aware: the bot knows which page the user is on, so "what do I do here?" from the Review screen gets a Review-specific answer. At minimum it should cover the five-card pipeline, each creation method, scheduling/rescheduling, and where relocated features now live (CSV import, 60-Day Plan, WordPress sync).

Note: this is a new capability, not a Blog cleanup — it spans the whole app. Tracked separately on the redesign map as a cross-cutting item pending an Erick build-vs-embed decision. The help content itself still needs to be written; this spec is a starting point.

7 · Open questions for Erick

  1. Status mapping. How do today's statuses map to the new cards? Proposed: Draft → My Drafts; Pending → In Review or Scheduled (depends what "Pending" actually means today — needs confirming); Published → Published.
  2. Is there a real review workflow today? If "Pending" just means "scheduled but not live," those posts belong in Scheduled, and In Review starts empty for existing content.
  3. Newsletter flag, categories, NL column. These stay in the Edit screen sidebar as-is? Confirm nothing users depend on in the current table is lost.
  4. Chatbot. Build vs. embed a third-party help widget? Where does help content live, and who maintains it?
  5. Calendar view. Does the Scheduled card's detail need a visual calendar, or is a date-sorted list enough for v1?

8 · Design credit

Jilly — Sage Coast Realty

Card-based pipeline concept, stage names, button copy ("Looks good, let's review it" / "Needs more work" / "Looks great"), the scheduled-post-reopens-in-Review behavior, and the help-chatbot requirement — all from live use of the platform, July 2026.