Using theme extension
Add to website
In the BO go to your website and on the left sidebar, you now have "Theme Extensions" (below "Settings").

Using the "ADD" button at the top right, you can add new theme extension to your website, where you can select your extension.
Your extension is now in the website! So for example, if it offers new page templates, they will be available.
Use new page template
New pages are added the usual way, by clicking on the button "ADD" on the listing of pages. The pages templates of the extension are at the bottom of the page.
Also, from the listing of pages you can see pages created with a page template from an extension

Use new block inside composer
The composer modal has a new tab "Extensions" with the blocks coming from an extension
Edit design settings
Design settings are in the same section as "Theme" design settings.

With the "Map Design Settings" feature, you can link your theme design settings and the extension design settings
Design Settings (extension)Edit locales
The locales of extension are not the same as the themes one: you can use the same key, but they will have separate translation
Extension default translation for locales
Like for a theme, you can define default translations for all languages.
Galaxy > Design > Theme, then in the filters of the page, select the type "Extension" (by default this shows only the themes) to show extensions
Choose your extension, go to the tab "Local", translation should be in the field Value (or you can use the export / import feature)
Website level locales
To have a custom translation only at website level, you can edit the locales, they are in the same section as usual locales
As for the list of pages, the listing allows you to know where is the locale coming from (theme / extension)

Dev team - Auto update CMS
On dev environments only, when editing the extension, you have a switch "Auto Update CMS"
If you enable it, each time you reload the page, the extension will be automatically updated from the code. This allows easy development, without needing to click on the "update" button on testeur.
This is only necessary if you are currently writing code on the extension.
If you are not changing the code (for example on a staging environment to test it), you don't need to enable this (it would only slow the process)

Last updated