Difference between creating mail template using custom code editor and Template builder?
SOLVE
Need to know the differece between them and which one is best to create a mail template ? Does custom code editor support edit content from user side ?
The template builder is a drag and drop page creator. Custom coding is creating your own code.
In the template builder the structure is pre-determined and generated by your actions in building the template. The template builder runs on a stripped down version of bootstrap 2 for structuring, which is a 12 column responsive grid system.
Building with custom code allows you to control all aspects of the build, but you forfeit any Hubspot default structuring unless you use the same classes and etc. If you do that then you might as well use the template builder.
Emails are tricky. The browser itself does not render the email. instead, the email client acts as a browser and renders the email. All browser are created by different people who approach feature implementation differently and with different priority, which is why you sometimes run into issues with cross browser compatability on website pages.
The same goes for email clients except you have to see most of them as really old browsers who developers do not care to implement features and do not allow for third party asset dependency (stylesheets, javascript, ect.). Because of this the general rule is to create your email using tables (like you did for websites in the 90s), inline styling, and styling in the head. Also you are limited on the css you are allowed to use because not all email clients support all css rules.
This being the case, you have two options in Hubspot:
1. Code the email template yourself, esentially creating a detailed mess of nested tables and inline styles (I do this from time to time as the code can be leaner).
2. Use the drag and drop template builder where the structure will automatically be set and navigation is easy.
The template builder is a drag and drop page creator. Custom coding is creating your own code.
In the template builder the structure is pre-determined and generated by your actions in building the template. The template builder runs on a stripped down version of bootstrap 2 for structuring, which is a 12 column responsive grid system.
Building with custom code allows you to control all aspects of the build, but you forfeit any Hubspot default structuring unless you use the same classes and etc. If you do that then you might as well use the template builder.
Emails are tricky. The browser itself does not render the email. instead, the email client acts as a browser and renders the email. All browser are created by different people who approach feature implementation differently and with different priority, which is why you sometimes run into issues with cross browser compatability on website pages.
The same goes for email clients except you have to see most of them as really old browsers who developers do not care to implement features and do not allow for third party asset dependency (stylesheets, javascript, ect.). Because of this the general rule is to create your email using tables (like you did for websites in the 90s), inline styling, and styling in the head. Also you are limited on the css you are allowed to use because not all email clients support all css rules.
This being the case, you have two options in Hubspot:
1. Code the email template yourself, esentially creating a detailed mess of nested tables and inline styles (I do this from time to time as the code can be leaner).
2. Use the drag and drop template builder where the structure will automatically be set and navigation is easy.
