The current default "new form" experience is pre-populated with fields which have an "unset" or "empty" value for the Label Width and Field Width inputs (below, top). When the form...
The current default setting for the Root Block Elements in Email is set to "<p>" and Landing Pages is set to "<div>". This is problematic for folks that are new to Marketo and didn...
The current default setting for a new form theme is "Simple (1of7)" which adds a layer of styling that most folks end up having to work around in one way or another.
The "Plain (7...
Currently, (top image) there is functionality for links in the Advanced Tab that allows you to edit the ID, Style and Class of the link element. This creates a "code-free" interfac...
The warning:Note: Editing Code outside of editable elements will break this email from its templatecould be much more pronounced in the UI - I've seen it come up a few times in th...
It's really crude, but you could open the Inspector console in Chrome and use the [+] icon in the top right of the elements panel to create a new "inspector stylesheet" in your ses...
Justin Cooperman any word on this coming to LP templates? I love the "controlled flexibility" this brings to Email 2.0, when can we expect to be able to take our Landing Pages to ...
Hey JD-Here's a look at something we've used to make complicated HTML stuff easy for the end-user to implement (kinda like the dropdown idea might help accomplish). On the surface,...
Would it be possible to have a " Token Display | Rendered-Token Display" boolean somewhere in the interface (much like the Desktop/Mobile view in the EMail 2.0 Editor) which would ...