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
It would be great to provide users with a resource for modular templates, rather than to go your own. It could be used as a starting point to handle every node and mark.
This is for the users who want 100% control over their content, but still shouldn't need to spend an age getting their templating ready to go.
A current starting point is the above, which we'd split out into individual templates for each node and mark. We cannot template Vizy Blocks without knowing in advance what fields are present.
The tricky thing about modular templates is the need to split marks' start and end tags around the text content of a node. We might have to have something like:
{% formarkinnodeContent.marks %}
{% include'vizy/marks/'~mark.typewith { start: true, mark: mark } only %}
{% endfor %}
{{ nodeContent.text }}
{% formarkinnodeContent.marks %}
{% include'vizy/marks/'~mark.typewith { end: true, mark: mark } only %}
{% endfor %}
And in the vizy/marks/bold include, we could have:
This could either be a generator within the plugin settings, or an example repository (or folder in this repository). I'm leaning towards the former out of the "cool" factor, and possibly more easier to maintain than a separate repository.
The text was updated successfully, but these errors were encountered:
It would be great to provide users with a resource for modular templates, rather than to go your own. It could be used as a starting point to handle every node and mark.
This is for the users who want 100% control over their content, but still shouldn't need to spend an age getting their templating ready to go.
A current starting point is the above, which we'd split out into individual templates for each node and mark. We cannot template Vizy Blocks without knowing in advance what fields are present.
The tricky thing about modular templates is the need to split marks' start and end tags around the
text
content of a node. We might have to have something like:And in the
vizy/marks/bold
include, we could have:This could either be a generator within the plugin settings, or an example repository (or folder in this repository). I'm leaning towards the former out of the "cool" factor, and possibly more easier to maintain than a separate repository.
The text was updated successfully, but these errors were encountered: