PowerAdvice · Pascal system review

The design work is about control, not decoration.

Pascal has been moving PowerAdvice from a page-by-page redesign into a repeatable system: one visual language, one channel template, one Ask pattern, and one story Doug can stand behind.

What changedshared rules
Whyfewer surprises
Resultdemo confidence
PowerAdvice homepage
Current PowerAdvice direction: sponsor-ready, editorial, measurable
Black Flag Design
Doug / Suzanne brief · June 24, 2026
What Pascal has changed

The site now has repeatable parts instead of one-off pages.

The visible work was not a random font pass. It was a foundation pass so the homepage, channels, articles, and Ask experience stop drifting apart.

AreaWhat changedWhy it matters
TypographyType now has roles: product UI, metadata, and editorial story titles.Doug gets a consistent answer when a font is different.
Site chromeHeader, nav, date, footer, and Ask entry were split into reusable pieces.The top of the site can be tuned once and carried everywhere.
HomepageMajor homepage sections were separated into reusable modules.Layout decisions become maintainable instead of fragile.
ChannelsChannel pages now follow one template instead of each acting like its own design.Approved centers can scale without redesigning every page.
AskThe Ask bar and Purple Wonderland are being brought into one consistent pattern.AI feels like a product feature, not a bolted-on experiment.
PowerAdvice homepage editorial modules
Black Flag Design
Already changed · typography, chrome, homepage, channels, articles, Ask
The system answer

A change should move through the system once.

This is the answer to JP's system question and Doug's confidence problem. The site should not require a new debate every time a font, card, ad, channel, or Ask control appears somewhere else.

01

Role

Each visual choice gets a job: title, label, metadata, action, article, channel, ad, or Ask.

02

Rule

The job becomes a shared rule, not a private page-level decision.

03

Template

Homepage, channel, article, and Ask surfaces use the same rules in their own context.

04

Review

Review asks whether the rule supports the story, sponsors, readers, and mobile behavior.

05

Repeat

Future centers, articles, sponsors, and Ask states inherit the same system.

What this prevents

Whack-a-mole design.

One page looking fixed while another page quietly drifts.

What this enables

Stable sponsor demos.

Doug can show the site without caveating every visible inconsistency.

What to ask

Does this help the story?

That is the right altitude for final launch decisions.

Black Flag Design
System principle · change once, carry everywhere
Doug's concerns, translated

The right response is a decision, not another open loop.

Doug is reacting to real demo risk: he wants to know why the site looks the way it does before he shows it. These are the concerns now mapped to system decisions.

Fonts changedAnswer with roles: product UI stays quiet; published story titles carry the editorial voice. The goal is hierarchy, not taste.
White space and article countAnswer with purpose: space, article density, and ad position are balanced against above-the-fold sponsor visibility.
Ask toolbar mismatchPlanned alignment: the homepage Ask control should match the preferred Purple Wonderland treatment without turning the whole homepage into Wonderland.
Channel inconsistencyAlready moved into one channel template: title scale, no unnecessary hero image, cleaner ad cadence, and article rows that stay article-only.
Clickability questionsAnswer with affordance: buttons, tabs, Ask controls, and article actions need to signal what they do before Doug has to explain them.
Ask anything toolbar

"This is not about selling a font."

The review should stay focused on trust, sponsor visibility, content clarity, and the story PowerAdvice is now telling.
Black Flag Design
Doug concerns · answer with purpose and status
What Pascal still plans to tighten

The remaining work is launch story polish, not a new redesign.

The foundation is in place. The next pass should make the public site feel finished, commercially credible, and easy to review against the PowerAdvice story.

1 · Public story

Lock the v5 site narrative.

Homepage, menu, channel naming, author treatment, right rail, Ask, and static pages should all feel like PowerAdvice.

2 · Visual pass

Resolve final look-and-feel drift.

Spacing, mobile behavior, micro-type, and page rhythm get fixed or consciously parked.

3 · Image strategy

Make launch images fast and reliable.

Cards, channel art, lead images, and article images should load cleanly without changing the content system.

4 · Hardening

Move from good to great.

Finish color, spacing, radius, and shadow rules so future pages inherit the system automatically.

PowerAdvice channel system
Launch boundary

CMS operator polish is separate unless it blocks July use.

The public site story matters first for demos. Signed-in CMS usability still matters, but it should not reopen the public-site design story unless it blocks LeeAnn or Tory from operating.

Black Flag Design
Remaining work · finish the story, then harden the system
What Doug can say

PowerAdvice is becoming a smarter editorial platform.

The design system supports the business conversation: clearer demos, stronger sponsor value, and final review focused on what drives trust and revenue.

A concise version for Doug

"PowerAdvice is moving from a legacy article library into a modern editorial and intelligence platform. The new design gives content a clearer hierarchy, sponsors visible placements, and readers a trusted way to explore articles, channels, and Ask PowerAdvice."

1
Lead with the business.PowerAdvice is not just a rebrand. It is a more useful product for readers, sponsors, and the editorial team.
2
Explain design as structure.Fonts, spacing, cards, ads, channels, and Ask each have a role in the system.
3
Talk about trust.AI is not replacing editorial judgment. It is a guided layer on top of PowerAdvice content and expertise.
4
Use metrics as proof.The system is being wired so search, email, article reads, shares, sponsor views, and sponsor clicks can be discussed with confidence.
5
Keep final asks concrete.Anything that does not strengthen demos, sponsor value, reader clarity, or July operations belongs in the backlog.
Black Flag Design
Doug talk track · story first, design supports it