![]() I'm just saying that this was the path html went down a long time ago and it has the drawbacks mentioned above but its too late for html. Using handlebars and then creating a html server which serves up the transformed mjml then try to point the dev tool at a url instead of the file system, use source maps to get the editor to map back to the original source files. #Contain image mjml generator#Then the display tools could use a lorem-ipsum generator to generate objects which can be used to dynamically expand what is visualized into a fully static content. #Contain image mjml code#There are no built in semantics for data binding, conditionals or loops therefore tools can't be made to view templated mjml files easily and all the current tools are designed to edit or view the final product not the actual source code in the project.Įither just pick handlebars as a first class citizen or implement your own syntax to allow data binding.Īdd a tag which be used to describe sample data for use by tools when rendering but is ignored at runtime. Is your feature request related to a problem? Please describe. #Contain image mjml manual#Same for the desktop tool.Ĭurrently the examples appear to be geared towards people creating completely static templates with hand rolled sample data and you cannot simply use that as is and now you have a disconnect between people making email templates and the files that actually need to go into the file system, resulting in manual translations. It won't work on files with handlebars syntax mixed in and if I'm looking at the files my build step produces I won't be able to edit it in the left because its not the right code. Therefore if you try to edit that output it will be lost and somehow needs to be translated back into the original source.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |