Every mappable item must be its own element.
When you map a text element to a field in the Salesforce app, all of that element’s content will be dynamically replaced by the contents of the field. This means that each item of text you want to map should be a distinct, separate text element in Brandcast. For example, if you want to create a template that has mappable items for a rep’s name, email, and role, you’d need to create three separate text elements (rather than putting three lines of text inside a single element.)
Avoid using inline styling for mapped text.
Brandcast allows you to apply styling at the global level (via the Global Styles panel), the block level (by selecting an entire element), or at the inline level (by directly selecting a piece of text.) If you apply inline styling to text, then map that element to a field in Salesforce, your inline styling will not be preserved on the published site. So, avoid using inline styling with any text that you intend to map, and rely on block-level and global styles instead. (You are still free to use inline styling with non-mapped elements.)
Use Master Pages for recurring elements.
If you want a piece of dynamic text or imagery to appear on more than one page of the template design -- a company logo, for example, or a rep’s contact information -- place it on a Master Page, and apply that Master to the desired pages of the site within Brandcast. This avoids the need to create the same mappings over and over again in the Salesforce app; instead, you’ll only need to map once to the Master.
Provide descriptive names for the dynamic elements of your design.
Content Mode provides the option to name each element on the page. These are the labels that will appear in the Salesforce app when mapping the template, so they’re essential for providing the user with information and context about what the target elements are. For example, you could label a text element “Price (with dollar sign)”, or “Description (about 50 characters)”. Labeling elements, in conjunction with locking static elements (see below), are essential for making the mapping process much easier and faster within Salesforce. This is done in the page structure of the Design Studio.
Use the Page Structure panel to lock items you don’t want changed.
Your template design will probably have many elements that you’ll want to remain static, and not mappable. These elements can be “locked” using the Page Structure panel, which will prevent them from appearing as potentially mappable items in the Salesforce App. This helps ensure that your template design remains intact. It also allows you to avoid being presented with an overwhelmingly long list of targets when creating your mappings in Salesforce. The page structure panel has a “Lock All” option which is particularly helpful for quickly locking elements on the page.
More information on locking content can be found here.
Be careful with absolute positioning.
Changing positioning from “normal” to “fixed” in Brandcast is often necessary for certain kinds of layouts, but one consequence is that content can sometimes be cropped if it overflows the element. If you’re mapping to a text element, and you expect a lot of variation in the content that’s going to populate it, make sure the text element is normally positioned to its parent, so that longer pieces of text don’t accidentally get cut off.