Skip to content
PowerAdvice CMS Docs

Start here

Start here

Section titled “Start here”

PowerAdvice operators use the CMS at /cms to manage public articles, multimedia, homepage programming, channels, advertising records, contributors, newsletter copy, lead review, and analytics review.

What the CMS controls

Section titled “What the CMS controls”
  • Articles and sponsored posts.
  • Multimedia entries for podcast, video, interview, transcript, and media-feed work.
  • Homepage curation for lead feature, latest rail, Of High Interest, featured partners, and right-rail programming.
  • Channels that power public section pages and top navigation.
  • Ads, sponsors, campaigns, creatives, company resources, and placement metadata.
  • Contributors, support pages, site chrome, newsletter settings, lead submissions, and analytics scorecards.

Daily operating pattern

Section titled “Daily operating pattern”
  1. Sign in to the correct CMS environment.
  2. Pick the left-rail section that owns the public surface you need to change.
  3. Search or filter to the record.
  4. Create or edit the record.
  5. Save draft.
  6. Resolve validation and permission blockers.
  7. Preview the draft state.
  8. Publish, schedule, unpublish, archive, restore, or remove only when the state change is intentional.
  9. Verify the resulting public URL or CMS status.

Tory and LeeAnn operating loop

Section titled “Tory and LeeAnn operating loop”

The launch-review loop should be simple:

  1. Pick one record or public surface.
  2. Confirm the expected state before editing.
  3. Make the smallest safe correction.
  4. Preview the result.
  5. Publish, schedule, unpublish, archive, or remove only when the owner intended that state change.
  6. Capture the exact route, record title or slug, expected result, actual result, and urgency if BFD needs to help.

Use the source audit when a page feels too generic: Tory and LeeAnn source audit.

Documentation standard

Section titled “Documentation standard”

Each maintained workflow page states the purpose, prerequisites, steps, resulting state, permissions, common failures, and recovery path. Authenticated screenshots use deterministic non-production content and must not include production personal data, subscriber data, cookies, Access tokens, or secrets. The visual rules live in Docs design standard.