Epic - Consolidate editorial metadata in the CMS editor​

[AmnestyAM]

Overview

What are we doing?​

Consolidating editorial metadata used across pages and posts into a single, unified interface within the CMS editor.​
​

What is it?​

Currently, various pieces of post and page metadata are stored and accessed in different locations throughout the editor. This work reviews the existing metadata fields and restructures how they appear in the CMS so that editors can access and manage this information in a clearer, more consistent way.​
​

Why is this a priority?​

As we introduce additional features for Amnesty, the amount of metadata associated with content will increase. Establishing a clear and coherent interface now provides a scalable foundation that will make future functionality easier to use and maintain.​

Sprints allocated

Number of sprints: 1

Description

We are bringing page and post metadata into a single place in the editor so it is easier for CMS users to find and manage. This provides a scalable foundation for upcoming Amnesty features.​

Goals

• Improve the editor experience, in particuilar when working with custom settings
• Reduce the complexity of creating content

Tasks

• Think about AIDAN class sub class year region etc.
• Translations (new feilds and descriptions)
• Capatilistions
• Uniformity in titles, labeles, descriptions, grouping, case
• Looks at margins and padding
• Look at bringing in some core WP stuff, like taxonomies and feature image
• Think about potential features in the other roadmap items and consider where they may be situated
• Think about training
• Think about comms

[carolinejcourtney]

repeating content types in featured content types feature (now say that 10x fast...)

[jaymcp]

just pushed a fix for that 🙂