What shipped tonight + what's worth building next, ranked by impact-per-hour. Pick which items to greenlight.
A single shared /portal-enhancements.js file now loads on every portal page. Self-contained, no build step, no backend.
All / Draft / Approved / Queued / Live chips below the toolbar. Click to filter visible asset cards by status. Live counts. Persisted in localStorage so the filter survives page reloads.[ for previous week, ] for next week.Ordered by impact-per-hour-of-work. Greenlight which items to build first.
Currently each asset is a full card stacked vertically. To review 35 assets you scroll a long way. The Linear / Superhuman pattern: a list view + a slide-in right panel.
What it looks like:
J / K) move down/up the list with the panel openA for approve, R for reject, Esc to closeWhy it's worth it: the highest-ROI single thing per the UX research. Doubles review throughput because you stop context-switching.
Currently filters persist in localStorage (per-device). Move to location.hash so you can:
Add a checkbox column. Select multiple assets. Floating bar at bottom: "12 selected — Mark queued | Mark live | Export". With optimistic UI (status flips instantly, undo toast for 5s).
Why it's worth it: when CM is queueing 12 LinkedIn posts at once, this collapses 12 clicks to 1.
Each asset gets a stable URL fragment (#jay-essay). Clicking copies a deep-link to that asset. Useful for sending CM a precise "look at this one" reference.
A toggle that collapses all inline markdown to summary-only. For days when you're scanning for which assets need verdict vs. days when you want to read each one carefully.
A new top-level view that shows ONLY what needs Jay's attention right now:
Pulls across all weeks. Single scroll. Massive time-saver as the engine accumulates weeks.
/cmCM doesn't need the full review portal. They need:
Single page, no brand tabs (they see everything). Tap-friendly on mobile.
Right now the anchor proposal flow is in chat between Jay + me. A real inbox view:
Probably the next major build after Phase 2. Closes the loop end-to-end.
Each week gets a metrics panel:
Requires the API integrations from the Automation page (HubSpot already wired; others need OAuth).
Each asset can carry tags (#actionable, #thought-leadership, #stage-tied, #faith-lane, #ai-skill). Filter by tag across all weeks. The actionable companion track shipped tonight is the first test of this — those assets are conceptually tagged but not yet filterable as such.
The research surfaced several mobile patterns worth implementing as we ship more weeks:
These would be a focused mobile sprint after Phase 2 ships.
Pick which Phase 2 items to build first. My ranked recommendation:
The rest can wait until you've spent 2-3 weeks actually using the portal and discovered what hurts most.