Often there is a need to have a static snippet of HTML at the start and end of a content flow. Currently these are placed before the content flow and after the content flow, but specifically outside of the content flow. This raises issues with regards to CSS formatting as we can no longer use the next element selector in CSS to format spacing between common snippets/components.
Can we look at adding the ability to ignore a static HTML snippet added in the template within the flow by applying a data attribute to it (e.g. data-cf-snippet-ignore), which tells the editor to ignore that snippet?
Often there is a need to have a static snippet of HTML at the start and end of a content flow. Currently these are placed before the content flow and after the content flow, but specifically outside of the content flow. This raises issues with regards to CSS formatting as we can no longer use the next element selector in CSS to format spacing between common snippets/components.
Can we look at adding the ability to ignore a static HTML snippet added in the template within the flow by applying a data attribute to it (e.g.
data-cf-snippet-ignore), which tells the editor to ignore that snippet?