Clean up content model

[peterschewe]

Fixes #23

• Merge page and t-default into t-page
• Rename seo to d-seo
• Rename name fields to internal_name
• Add help text for internal_name fields
• Make internal_name fields required
• Remove content type section
• Limit the entries in m-columns (each column max. 1)
• Bump cssg packages to latest versions (especially contentful-migrations with the new field grouping feat.)
• Remove t-default Storybook example (open issue: page templates cannot be created in Storybook)
• Disable lazy load option of c-image and m-media for editors
• Update t-page migration and use field grouping (Compose only) to separate page and seo settings
• Disable theming option of t-page and all modules for editors
• Align naming of headlines with ui/ux (e.g. headline instead of title)
• Use HUGO_ENV instead of HUGO_ENVIRONMENT
• Remove the ability to change the logo via Contentful
• Disable theme option of t-page
• Disable hero content in m-stage
• Rename m-editorial to m-hero

[peterschewe]

Hi @bezoerb, there is still a breaking change here that we need to resolve. If the content type is t-default (legacy), then it tries to get the .Params directly, as it would be correct for t-page. But they are in data and would have to be fetched via utils/get-data. With the hasPrefix $content_type "t-" we take t-page and t-default in the same way, which was fine in other places, but not here.

Can we differ the legacy templates (data/) from the new ones (content/) at this point? Or do you have another idea?

Maybe just check if this file exists in data and only then use utils/get-data. Then we could omit the check for the content_type.

[peterschewe]

I have completely removed the check on page type. Instead I try to get page params directly and if they are empty I use get-data.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
11.4% Duplication