We have two fields with the field type "Text (formatted, long, with summary)"
Purpose (body) on Centralized content
Body (body) on Full Width Alert (aka Banner)
Body (body) on CMS announcement
In a decoupled site where summaries are not used (yet) this adds some technical debt and needless diversity of field storage types, and makes CMS-wide changes harder (eg #7011).
Acceptance Criteria for the epic
[ ] No fields are set to use "Text (formatted, long, with summary)" field type
[ ] Existing fields with this type are converted to "Text (formatted, long)
[ ] Any existing content in these fields is maintained.
[ ] We have a runbook (or two?) that includes any
[ ] Content migration
[ ] FE dependencies
CMS Team
Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.
Description
We have two fields with the field type "Text (formatted, long, with summary)"
body
) on Centralized contentbody
) on Full Width Alert (aka Banner)body
) on CMS announcementIn a decoupled site where summaries are not used (yet) this adds some technical debt and needless diversity of field storage types, and makes CMS-wide changes harder (eg #7011).
Acceptance Criteria for the epic
CMS Team
Please leave only the team that will do this work selected. If you're not sure, it's fine to leave both selected.
Platform CMS Team
Sitewide CMS Team
⭐️ Content ops
⭐️ CMS experience
⭐️ Offices
⭐️ Product support
⭐️ User support