Oct 16, 2018 8:39:44 AM
Currently, in our Third Generation Editor we do not allow access to edit the HTML and have no immediate plans to do so. We want to provide our customers with the abilities to be able to use a user-friendly interface instead of having to rely on a code view to get their desired results. With all the feedback we have been collecting we are planning on making improvements to padding and adding some line spacing elements in the UI. I know this doesn’t solve all use cases, such as adding tables, but we will continue to make strides towards improving the editor.
I understand allowing HTML would increase the ability for more control of your content but it can also have a negative impact on your newsletter’s display in email clients. If we provide access to HTML for every block, changing some of the default styles or content could break display when sent to an email client. Also being able to manually adjust width could have a negative effect. We have a team of amazing engineers constantly testing our templates in all email clients, so you can be certain your email displays consistently across the board. With that in mind, we want to make sure we make it easy to provide the best look and feel not only on the desktop but on mobile. With a majority of opens now leaning towards mobile over desktop we take that as a priority.
Please continue to let us know your thoughts on HTML and what exactly you're trying to do so even if we don't have HTML access we will be able to give you the tools to get your desired outcome.
It would be very helpful to have this functionality. I'm relatively new to Constant Contact and was really surprised to learn that it is no longer included in this version of the editor. I have a background in web development, so the fact that one can't edit code is absolutely bizarre. I did some quick research and it seems users have been requesting this for over a year, but the same stock responses are being sent by CC without any idea of whether this feature will ever be reintroduced or not.
Give users a definitive answer either way. It's as simple as "We do not currently have plans to reintroduce HTML editing" or "Yes, we are planning to reintroduce HTML editing and will have it deployed by XX date." Giving the same reply "Your request will be routed to the product team" over and over again for over a year is simply a bad UX.
I will be moving to and suggest others to do the same.
Ditto ErieBar's point. HTML access just allows a lot more control & flexibility for end users familiar with using it. I am still using the 2nd generation editor for my campaigns because it has html access.