Tory and LeeAnn source audit
Tory and LeeAnn source audit
Section titled “Tory and LeeAnn source audit”This page maps the PowerAdvice CMS documentation to the submitted stakeholder record. It keeps the docs focused on the people doing the work, not on internal implementation language.
Audience
Section titled “Audience”| Operator | What the docs optimize for |
|---|---|
| Tory Miller | article review, sponsor placement, homepage rotation, multimedia workflow, field meaning, and advanced settings |
| LeeAnn Roy | article loading, image handling, copy editing, contributor corrections, and daily publishing handoff |
Source evidence
Section titled “Source evidence”| Source | What it contributed |
|---|---|
Gmail FOR WEDNESDAY: PowerAdvice CMS comments |
Tory and LeeAnn had direct CMS review feedback before the July 15 planning pass. |
Gmail PowerAdvice.com Change Requests |
Sponsor/channel/design requests were copied to Tory and LeeAnn and shaped sponsor placement guidance. |
Gmail One more thing to add to the CMS list |
Deletion/removal readiness and September 1 launch confidence had to become explicit documentation. |
Gmail Metrics data points |
Analytics guidance must support storytelling and value demonstration, not just raw counts. |
Gmail Footer navigation deliverables |
Static/support page ownership belongs in the CMS mental model even when it is not a daily nav item. |
Google Doc PowerAdvice CMS checklist and operator guide - June 10 |
Launch-review checklist, status definitions, article review cautions, and feedback format. |
Google Doc PowerAdvice CMS Walkthrough - 2026/06/10 |
3,040 migrated articles, podcasts, ads, formatting, preview, schedule, and save-state issues. |
Google Doc Hold for PA CMS Review - 2026/07/17 |
image upload/paste, sticky formatting, homepage rotation, sponsor status, preview links, and documentation gaps. |
| PostHog route readback | Authenticated CMS usage is not visible in tracked events; public route usage emphasizes homepage, contributors, channels, multimedia, search, articles, and static pages. |
Coverage map
Section titled “Coverage map”| Concern | Maintained documentation |
|---|---|
| Migrated article review | Articles, Publishing states, Recovery paths |
| Multimedia and podcasts | Multimedia |
| Ads and sponsor placements | Ads and sponsors, Channels |
| Homepage rotation | Homepage |
| Contributor and sponsor status | Contributors |
| Image handling | Articles, Multimedia, Recovery paths |
| Preview, scheduling, publishing | Articles, Publishing states, Recovery paths |
| Analytics and storytelling | Analytics |
| Deletion and removal | Publishing states, Recovery paths |
| Support handoff | Start here, Recovery paths |
Remaining proof required before AD-376 closes
Section titled “Remaining proof required before AD-376 closes”- Authenticated UAT/staging screenshots must replace or validate every maintained screenshot state.
- UAT, staging, and production docs URLs must have runtime receipts.
- CMS Help links must resolve to the right docs environment.
- Cloudflare Access challenge and authenticated route behavior must be verified.