Skip to content

Use one document title bar for every content type - #266

Merged
getdave merged 1 commit into
trunkfrom
getdave/title-area-ui-normalization
Nov 20, 2026
Merged

getdave merged 1 commit into
trunkfrom
getdave/title-area-ui-normalization

Conversation

@getdave

@getdave getdave commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

This makes the document title bar in the middle of the canvas toolbar the same whatever you're editing. Until now a page had one design, the search-style bar, while layouts, system pages, the header and the footer had a separate, older one, a two-line purple title with an icon. Two designs for the same job means two things to keep up to date, and the older one had already fallen behind.

So every content type now uses one bar, PageSwitcher. Where layouts and template parts genuinely differ, the bar handles it with small variations rather than a separate design.

How does the one bar handle shared things?

Changing a layout or template part changes every page that uses it, and people still need to know that. The bar shows it in three ways.

  • In the spot where a page shows its status icon, a shared thing shows a purple globe. It's the mark Review changes already uses for site-wide changes, and its tooltip says where changes show.
  • The name is purple, in the colour the editor already uses for anything shared.
  • A short word after the name says what it is ("Every page", "Layout" or "System page"), in the slot where a page shows extra detail.

On the header and footer screens, the bar doesn't open the page finder (canSwitch={ false }). Those screens are about the part, so the bar just names it. It keeps the same shape and position.

What changes in the code?

  • PageSwitcher takes two new props. shared marks the bar as shared and holds the globe's tooltip, and canSwitch turns off the finder.
  • The layout canvas and the header and footer canvases now render PageSwitcher in place of their own title markup.
  • The old .is-global title styles are gone, since nothing uses them any more.

How do I test it?

  1. Open a page. Its bar looks and behaves as before.
  2. Open Site parts > Header. It's the same bar, reading "Header · Every page" in purple with a globe, and clicking it does nothing.
  3. Open Posts and switch to layouts (/types/post/list/all?content=templates). It's the same bar again, reading "Single Post · Layout" in purple, and clicking it opens Go to page.

Open question

Should layouts stop opening the finder too? I've left it on because layouts are listed under Pages and Posts, but I could go either way.

🤖 Generated with Claude Code

@getdave
getdave requested a review from scruffian November 19, 2026 13:40
@github-actions

Copy link
Copy Markdown

Try this branch in WordPress Playground, with a WooCommerce shop, for an AI agent to drive, or on a blank site with WordPress's default theme. All run the latest build of getdave/title-area-ui-normalization and update with every push, a few minutes after the Plugin zip build finishes.

To start in a workspace other than Default, open it in Writing, Builder or Selling.

@getdave getdave changed the title Use the page title bar for layouts and template parts Use one document title bar for every content type Nov 19, 2026
@getdave

getdave commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator Author

@scruffian this is a normalization effort in light of your chanegs to the overall chrome

@getdave
getdave force-pushed the getdave/title-area-ui-normalization branch from f15c33b to 33ed7f9 Compare November 20, 2026 23:07
Layouts, system pages, the header and the footer now show their name in
PageSwitcher, the bar pages use, marked as shared with a purple globe,
name and meta. The header and footer bar doesn't open the page finder.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@getdave
getdave force-pushed the getdave/title-area-ui-normalization branch from 33ed7f9 to 65be8c7 Compare November 20, 2026 23:15
@getdave
getdave merged commit e8fa03e into trunk Nov 20, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant