Gutenberg allows us to set predefined templates, but there is no way to validate their contents (e.g. enforce a headline). This often leads to problems in the react frontend where we don't want to deal with everything to be optional.
Idea: combine the gutenberg parser with the information in a graphql schema (which fields are mandatory, and which not) and validate blocks before they are sent through the API. If they are not valid, insert an "error" block instead. This way the error is displayed but the whole frontend does not necessarily break.
Gutenberg allows us to set predefined templates, but there is no way to validate their contents (e.g. enforce a headline). This often leads to problems in the react frontend where we don't want to deal with everything to be optional.
Idea: combine the gutenberg parser with the information in a graphql schema (which fields are mandatory, and which not) and validate blocks before they are sent through the API. If they are not valid, insert an "error" block instead. This way the error is displayed but the whole frontend does not necessarily break.