In Progress

Thank you for the idea, votes, and feedback, here's the current status for the new Schema column, planned for an upcoming release of SDL Tridion Sites. Slight smile

This includes the ability to sort and filter on the Schemas in a given list. We will drop the separate "Type" column as the information is available via the icon and in the information for the item. The item types as well as Schema column will also be filterable.

Folders will include the Schema name and Pages will show any default Schema they have set as well.

Details and interactions are subject to change. Please continue to offer your examples and votes to other ideas you're interested in as they've been helpful in understanding the enhancement request!

Add Schema Name Column to the Explorer View

Currently the CME interface has columns for name, type (component, folder, etc), publication, and modified date.

It would be helpful if there was also a way to display what the schema for a component is. This could take the form of a new column.

Or augmentation of an existing column.

This can be done by custom GUI extensions, but it seems like a no-brainer for a native feature.

Parents
  • In most of my implementations I had the team limit the number of Page Templates (PTs), regardless of rendering approach. So you might see a PT for the majority of pages with some special options for the homepage or navigation. The variation of page types is handled by what content is placed on the page.

    I'd still recommend a small set of PTs with a few matching Page (Region) Schemas. In this case showing either Page Template or Page Schema would make sense in the type column. If Page Schema is somehow slower to display, go for PT.

    The initial introduction of Regions may encourage a bigger variety of region arrangements and thus more PTs. Well least until users can create and add their own Regions to pages.

    What would ECL items show? And does Type matter more or less in the Favorites list?

    Ideally "Type" would show the original "Page Type" an XPM page is based on, but that's probably a bit more involved than this idea. :-)

Comment
  • In most of my implementations I had the team limit the number of Page Templates (PTs), regardless of rendering approach. So you might see a PT for the majority of pages with some special options for the homepage or navigation. The variation of page types is handled by what content is placed on the page.

    I'd still recommend a small set of PTs with a few matching Page (Region) Schemas. In this case showing either Page Template or Page Schema would make sense in the type column. If Page Schema is somehow slower to display, go for PT.

    The initial introduction of Regions may encourage a bigger variety of region arrangements and thus more PTs. Well least until users can create and add their own Regions to pages.

    What would ECL items show? And does Type matter more or less in the Favorites list?

    Ideally "Type" would show the original "Page Type" an XPM page is based on, but that's probably a bit more involved than this idea. :-)

Children
No Data