You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have all content fields in content type YAML including defaults (e.g. title, body) for clarity (e.g. i news.yaml).
Would be useful to have a diagram of the flow of how content is generated from the frontend
Need to be able to change frontend content field names & enable us to make them different from the API (WordPress)
What happens with default content field? Is confusing as page.content.content
Can we whitelisting HTML?
Can we mark content types as HTML in the content type so we don't need to use raw filter
Can we get timezone for a Date field
Can we separate flexible content into separate files, e.g. a directory
Need to review with Marie how flexible components are templated on the front-end (and simplify)
Need to consider template field for pages from WP (page.template)
If a page has a different template it can have different fields (do we need to organise content fields by template too?) This is a bit like a sub-content type.
Can we add comments in Twig files to indicate where data is coming from?
The text was updated successfully, but these errors were encountered:
After discussion with Sean:
The text was updated successfully, but these errors were encountered: