We should move Blog Posts to a new Content Model in Contentful Headless CMS.
@heathergreerklein I removed the previous "Blog Post" Content Model in Contentful, and replaced with a new Content Model which is easier to parse on the front end, and includes some best practices when creating Content Models. For example...
Before
After
Best practices when creating Content Models
Keep field names short and tight. For example if the Content Model is "Blog Post", the Title field should be "Title", not "Blog Post Title".
All long, descriptive content should be data type "Rich Text", not "Long Text". This way our app can process the Rich Text content (links, perhaps images, etc.) included in content returned by Contenful.
Done looks like
[x] All new Blog posts are entered in Contentful Headless CMS, and will display on the site.
[x] New blog posts will have a new UI design pulled from TailwindUI
[x] Previous Blog posts will display previous content and not be imported into Contentful (this would be a huge job)
We should move Blog Posts to a new Content Model in Contentful Headless CMS.
@heathergreerklein I removed the previous "Blog Post" Content Model in Contentful, and replaced with a new Content Model which is easier to parse on the front end, and includes some best practices when creating Content Models. For example...
Before
After
Best practices when creating Content Models
Titlefield should be "Title", not "Blog Post Title".Done looks like