Adding Static Layouts to Your Theme
Requirements
- If you haven't already, please start here: Developers - Adding Content to SiteBuilder
This documentation is aimed at those following the Theme-creator route (please read this first if you haven't already).
It's not currently supported to include Static Layouts within the Module-creator Module-creator route.
Introduction
Static Layouts are HTML layouts which can be included in a Theme. They won't directly interface with the database in the same way as a Dynamic Layout and are likely to have their content edited by the Module-user, either in the code, or in the Siteglide Admin's Studio tab.
Where does the user access Static Layouts?
-
The Studio tab in Siteglide is one place that SiteBuilder Static Layouts will appear. They can be dragged and dropped into the page and edited there.
SiteBuilder Static Layouts will only appear in the Studio tab if the Theme to which they belong is attached to any installed Page Template on the site. It's not yet possible to only show Static Layouts which are an exact match to the current page's template, but we will implement this when we can.
-
PageBuilder will show Static Layouts as section blocks which can be added to the page within the SiteBuilder UI. These will only show for the currently selected Theme.
Siteglide's Static Layouts Webhook
Siteglide will be publishing a webhook allowing any Module to add Static Layouts to the Studio tab without going through SiteBuilder. SiteBuilder builds upon that API with behind-the-scenes code which merges all Static Layouts in the file structure and automatically builds their categories.
File Structure
Under your Theme folder, you'll need to create folders for each category of Static Layouts. The folder name will be capitalised and its underscores will be replaced by spaces within the UI e.g. "call_to_action" becomes "Call To Action".
Within each folder, each static layout gets its own file. The name of this file should be a number, which relates to the layout's ID in the static_config
file, see next step.
└───modules
└───module_<module_vanity_id>
└───private
└───views
└───partials
└───sitebuilder<secret_key_preceded_by_underscore>
└───theme_<module_vanity_id>
| static_config.liquid
└───static
├───hero
│ 1.liquid
│ 2.liquid
│
└───features
1.liquid
Adding Content to Files
At the present time, static content should be added inside each file as HTML only (including <style>
or <script>
tags if you like). It may be possible in future to include Liquid wrapped in raw tags, but it is not currently.
Static Config File
The static_config.liquid
file should be added inside the Theme folder in order to give SiteBuilder the metadata it needs to find your layouts and display them in either the Studio tab UI or the PageBuilder UI.
{
"name": "Studio", {% comment %}String. Required. The name of your Theme{% endcomment %}
"id": "theme_<module_vanity_id>", {% comment %}String. Required. {% endcomment %}
"categories": [
{
"name": "Hero", {% comment %}String. Required. The name of your category. Should match the folder name in the file structure, when converted to lowercase and spaces replaced with underscores.{% endcomment %}
"id": "1", {% comment %}String. Required. Must be unique within categories. {% endcomment %}
"layouts": [
{
"id": "1", {% comment %}String. Required. Must be unique within layouts and exactly match the filename of the layout it describes. {% endcomment %}
"thumbnail": "https://res.cloudinary.com/...hero-1.png" {% comment %}String (absolute path image URL). Required. While the image will be thumbnail sized in Studio, it should be large enough to display correctly in PageBuilder, so should be at least 800px wide.{% endcomment %}
},
{
"id": "2",
"thumbnail": "https://res.cloudinary.com/...hero-2.png"
}
]
},
{
"name": "Feature",
"id": "2",
"layouts": [
{
"id": "1",
"thumbnail": "https://res.cloudinary.com/...feature-1.png"
}
]
}
]
}