Details View → Page

[mtias]

The page details panel in the site editor currently contains a permalink and generic description:

This panel could be more useful if we surfaced page details and pathways to edit them:

• Featured image.
• Excerpt.
• Title (should be editable)
• Slug / URL (should be editable).
• Published and modified date at the bottom (next to save action).
• Template (only if there are more than just the default page template).

Special pages may need unique treatments:

• Homepage (displays posts)
• Static home page
  • Posts page

Ellipsis actions (next to Edit button)

• Delete
• Duplicate

Mockup

Here's an updated design with a couple of additional details:

[SaxonF]

The page detail panel offers a great space to provide a quick view into the makeup and performance of a page. We’ll start simple with the most basic of information (e.g. treated similar to OG link previews) but should also design it such a way that allows for extension by plugins (e.g. page statistics).

We can take some inspiration from other tools that give you an insight into a document/record/file e.g. finder or Craft

• Show day was first published if published
• OR show day draft was first created if not published
• Show featured image if it exists
• Show post excerpt if it exists
• Show’s which template a page is currently using. Clicking on the template name takes you to the template details panel.
• Clicking back on the template details panel takes you back to the page panel
• Secondary actions include “Delete” and “Duplicate” which can be accessed via a DropdownMenu ellipsis next to edit

As we build this view out, along with any other view on the dark canvas, we should ideally by updating any primitive components to make use of the new theme provider .

@mtias I've purposely stripped this right back for 6.3 which means read only, no editing. We have a bit of work to do around componentry, mixing read vs write info (e.g. plugins), and how we handle localised saving which makes editing certain fields a bit more complicated. Thoughts on creating follow-up issues for any high level editing needs as we come across them?

[jameskoster]

Here's an updated design with a couple of additional details:

I removed the excerpt affordance as (afaik) pages do not make use of them in the same way as posts. Easy to add back if needed.

@WordPress/gutenberg-design what do you think? Is this one ready for dev?

[paaljoachim]

I got to say that this looks great!
Being able to drill down into a page and later on posts and seeing the most important things is very helpful!
Personally I would not care about time to read in a page. Perhaps I would in a post.

What is important here is status.
Featured image if the page has one. Might just not have one as it is not needed for a page.
Details.
Template, Parent, Words, Time to read.

Last modified is very helpful.

All in all this is very very nice!

[SaxonF]

@jameskoster development has already started :)

[jasmussen]

Since it's already underway, I've triaged it as such 🚀

[jameskoster]

Being able to drill down into a page and later on posts and seeing the most important things is very helpful!
Personally I would not care about time to read in a page. Perhaps I would in a post.

Yeah some of the details feel foundational while others (like time to read, word count) will be more subjective.

Outside of the foundational items, it might be worth exploring toggle-ability of some of the less-important details. Kind of like the "Screen options" affordance in wp-admin.

[jasmussen]

Outside of the foundational items, it might be worth exploring toggle-ability of some of the less-important details. Kind of like the "Screen options" affordance in wp-admin.

Always an option, but also an option I would punt until we have a high degree of polish and solidity of the initial items, so we get a higher confidence in what to keep vs. what to remove.

[jameskoster]

Yup, definitely something to look into later.

[ramonjd]

I think we can close this now that #50767 is merged?

There's a minor follow up to refactor a few things, but it's only code-related and the UI/UX isn't changing.

Feel free to reopen if there are outstanding issues related to the page details view.

[mtias]

Sounds good to close, we'll have smaller follow ups to do.