Export/Import - What for?

We can think of couple reasons why but you can probably image many more.

You can export your RZ Design in several different formats. Typically your intentions are to use the code somewhere other than ReatlyZapp. We try to accommodate as many scenarios as possible. We provide three different formats, each with a specific purpose.

It is also possible to import code into a RZ Design. Again we try to accommodate as many scenarios as possible.

Export

We can imagine a couple of scenarios 1) exporting code you intend to use in an external system and 2) exporting code that you intend to use in RealtyZapp e.g. another design. We provide the following formats...

• HTML - A raw HTML version of your design. Check the merge data box if you want a your data merge with any/all {{...}} tokens. Otherwise the resultant HTML code will still contain all of the {{...}} tokens. The HTML code is intended for use other than re-importing into another RZ Design, for this you should only use the JSON code. 
• MJML - Only appears if working on a Blast design. The MJML code version of your design is intended for use outside of RealtyZapp and in some application that supports MJML code. It is not intended that you use the MJML code to re-import into another RZ Design, use the JSON code for that. However, you may have occasion to copy a small portion of the MJML code and utilize it in another RZ Design. 
• JSON - A proprietary, and very verbose, version of you design. JSON code is best choice if you intend to re-import inot another RZ Design. THe JSON is practically useless outside of RealtyZapp.

Import

Attention! Importing code into a RZ Design WILL REPLACE its entire contents. We wanted to shout that out because we don't want you accidentally stomping on your own foot. 

You can paste in either HTML code or JSON code. If working with a Blast design, you can import MJML code or JSON code but not HTML code. Got it?

When importing HTML code, it is assumed the code comes from somewhere besides RZ Designer. RZ Designer will do its best job to import HTML code and recreate it in a new design. However, it is hard to accomodate all possibilities. You will just have to try it and see what works and what does not. Let us put it another way, should your HTML contain stuff that is not supported e.g. wild and crazy plugins, it might not turn out well when imported into a RZ Design. 

Now that we have made that little disclaimer. We think RZ Designer is very capable of handling some pretty crazy HTML code. So, don't be shy, try it. Obviously, a Web Page design can accommodate the most craziness. A PDF design is not a Web Page, so anything other than static HTML content probably won't work in a PDF. But again, try it. You can't hurt anything by trying. 

As for Blasts, we decided to go with the MJML framework instead of raw HTML so you can't import plain old HTML code, it has to be MJML code. Sorry but we value the quality of your email blasts too much and we decided that we can't afford supporting possibly crappy HTML email code from who knows where.

A special note about JSON code. When we say JSON code we mean the JSON code version of a RZ Design, not any old JSON code. Our designer's proprietary JSON code is intended for export/import among RZ Designs. We think you will find our JSON code useless anywhere outside of RZ Designs.