This feature is available on Beefree SDK paid plans only.
Overview
With Content Defaults, you can define how content looks when dragged into an email or page.
When adding new content elements through the Content tab, you may want a default style that matches one of these options:
your application’s color scheme;
your user’s branding guidelines;
the look & feel of the template used to create the message or page.
For example, here is how a button dragged into the stage looks by default:
The background color is always light blue (HEX code #3AAEE0).
The font size is always 16px.
The font is Arial, unless a different Default font was set for the template loaded in the editor.
The border radius is set at 4.
The CTA is a formally correct, but laconic “Button”.
Instead, when applying Content defaults, the button dragged by your users could look out of the box like this:
We’ve used a dark grey color (HEX code #555555), an Ubuntu font at 22px in Bold, with a border radius of 10 and a nice “READ MORE” call-to-action.
Content Defaults are part of the Configuration parameters passed to your Beefree application during startup, so you can have different sets of them for different users.
Use cases
By setting up your Content defaults, you’ll be able to address styling and branding needs for you and your customers.
Create a more consistent UX between your application and the editor
If your application uses dark grey for the primary CTA, then you probably would want a default button in the Beefree builders to follow that style.
Match your customers’ branding
If your application has brand settings that are used for your app’s UI or for assets managed in your application, you may want those to apply also to default content in the Beefree editors.
Create a more consistent experience within the editor
If you’ve customized how the editor looks like, either through Themes or Custom CSS, you may want default content to adhere to the same style.
Define custom social blocks
Since the Social block is one of the available Content defaults, you can define what social platforms – either present in the Beefree editors or added by you – are included when a social block is added to a message or page. For example, you can have a default social block with three platforms defined in the Beefree system and a fourth, custom one (Messenger):
How it works
To set up the content styles you will need to add the contentDefaults object to beeConfig:
You can add all the content styles, some of them or just one. It is up to your application to create them for all the users or for a segment, as there are no related server-side settings; basically you can customize them each time the editor starts.
All the contents use the same pattern, but the object must match the content schema for the type of content (described in the following section).
Note: If content defaults are incorrectly formatted, the following onWarning will be triggered and the default table will be used instead:
{code:1730, message:'Content defaults for [Table] module is not valid'}
If the user tries to load a template that contains a malformed Table (for example if a row in it does not contain all its cells), the template is not loaded, and the onError is triggered.
The following code displays an example error for this scenario.
{ code:2250, message:'Bump template validation error', detail: 'page/rows/0/columns/0/modules/0/descriptor/table/rows: malformed field (each row must contain the same number of cells)',
}
