Is there a way to convert my existing HTML messages/templates into BEE-compatible messages?

Follow

Comments

4 comments

  • Avatar
    Sergio M.

    Hi Johnpaul, it's not ideal to embed your templates as a "huge block of html" in the JSON since it gets converted into HTML by our Email Parser, which adds all of the responsive code.

    My advice would be to use and customize one of our default JSON templates and use it to convert your templates or at least some of them. Some of our SaaS customers have chosen to keep their WYSIWYG editor (for editing older messages) along with the BEE editor, but if you wish to provide the BEE editor alone you'll need to think about how to convert and make your messages and templates compatible with BEE.

    We can definitely talk more about our integration tips and answer any technical questions you may have. We'll reach out via email :)

    0
    Comment actions Permalink
  • Avatar
    Johnpaul Burbank

    Would it be possible for HTML of a pre-existing email template be able to slotted into the JSON structure of a template? Some page or template type that has minimal to no styling on its own. It would obviously not be possible for new content to dragged into the middle of this "pre-existing HTML" block and editing would be limited to the WYSIWYG editor. Thoughts?

    0
    Comment actions Permalink
  • Avatar
    Sergio M.

    Hi Johnpaul, it's currently not possible to convert an HTML template into a usable JSON template for the BEE editor. The process from HTML to JSON is very complex and cumbersome. We recommend to build your JSON templates directly. As a starting point, you can use our BEE Free templates and customize them into your own: https://github.com/BEE-Plugin/BEE-FREE-templates


    Hope this helps!

    0
    Comment actions Permalink
  • Avatar
    Johnpaul Burbank

    Thanks for the response Sergio. I really appreciate the amount of documentation you all put into this. Its impressive and useful.


    I full get and understand the difficulty in translating a HTML doc into JSON. What I suggest is something else. Putting a large chunk of HTML (the contents of a whole template) into a block of the JSON. Something like this.


    Template = {
    "page":{
    "title":"Template Base",
    "description":"Test template for BEE",
    "template":{
    "name":"template-base",
    ...
    },
    "body":{
    "type":"mailup-bee-page-proprerties",
    "container":{
    "style":{
    "background-color":"#FFFFFF"
    }
    },
    "content":{
    "style":{
    "font-family":"Arial, 'Helvetica Neue', Helvetica, sans-serif",
    ...
    },
    "computedStyle":{
    "linkColor":"#0068A5",
    ...
    }
    },
    "webFonts":[


    ]
    },
    "rows":[
    {
    "type":"one-column-empty",
    "container":{
    "style":{
    "background-color":"transparent",
    ...
    }
    },
    "content":{
    "style":{
    "background-color":"transparent",
    ...
    }
    },
    "columns":[
    {
    "grid-columns":12,
    "modules":[
    {
    "type":"mailup-bee-newsletter-modules-text",
    "descriptor":{
    "text":{
    "html":"



    I'M A HUGE BLOCK OF HTML",
    "style":{
    "color":"#555555",
    ...
    },
    "computedStyle":{
    "linkColor":"#0068A5"
    }
    },
    "style":{
    "padding-top":"10px",
    ...
    }
    }
    }
    ],
    "style":{
    "background-color":"transparent",
    ...
    }
    }
    ]
    }
    ]
    }
    }


    Please see the area around the string "I'M A HUGE BLOCK OF HTML". My problem is this. We have hundreds and hundreds, if not thousands of templates that have been already been created with another tool and we are storing. We would find it totally fine if we could do no more than edit simple markup with the WYSIWYG editors within Beefree plugin. We just don't want to have to have two editors though, one for new template creation and a completely different one for editing older ones.


    Thanks


    0
    Comment actions Permalink

Please sign in to leave a comment.