Data Definitions: Normalize CMS Content Types

[rosy1280]

Normalizing the data definitions is an attempt to make the naming of things more standardized across all page types. Normalization within Cascade should include but not limited to:

• [ ] Normalization of field labels across page types
• [ ] Normalization of help text for identical fields across page types
• [ ] Renaming of field groups to more closely reflect the Pattern Library's naming schema
• [ ] Implementation of shared fields when and where applicable

[laurenhamel]

@rosy1280, I'm working my way through the data definitions, and in addition to the field names needing normalization, I'm also noticing there are many identifier naming discrepancies as well (field IDs). While this isn't entirely a deal-breaker, I imagine this may lead to some confusion with Hannon Hill since similar design patterns may ultimately end up having different field IDs across different page types. In terms of development and maintenance, normalizing these would make the most sense, especially since we could easily identify like patterns, irregardless of page type, and reuse the same transformations (Velocity code) in the long run. Normalizing field IDs could also help us closer align the Pattern Library's data models with the XML data that Cascade produces. However, the issue that we'll run into if we proceed with normalizing these fields at this time is that we may end up losing some of the content that's already been entered into these pages. I wanted to get your thoughts on this.