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 really useful to be able to write {{ post.content | cloudinary: presetName }} so that we can use different presets on the same content, in different layout places.
Currently, using {% cloudinary presetName image.jpg %} inside Markdown content means we can chose only one preset for each image, whatever the place it is inserted in layouts.
This filter would also enable writers to use Markdown's native image syntax in WYSIWYG tools.
Would this make sense?
The text was updated successfully, but these errors were encountered:
Should we be able to link a preset to a layout in defaults config or in layout's front matter while keeping basic Markdown and having a hook apply the corresponding transformation?
It would be really useful to be able to write
{{ post.content | cloudinary: presetName }}
so that we can use different presets on the same content, in different layout places.Currently, using
{% cloudinary presetName image.jpg %}
inside Markdown content means we can chose only one preset for each image, whatever the place it is inserted in layouts.This filter would also enable writers to use Markdown's native image syntax in WYSIWYG tools.
Would this make sense?
The text was updated successfully, but these errors were encountered: