...
The custom themes should be created with the defined structure (its recommended to use the default theme as a template) and compress (GZIP) the folder into a file with the name ThemeName.zip where ThemeName is the name of the Theme. There is also a solution that is included an option available to make the theme design phase easier (see On external server as folder structure).
...
The theme folder (not zipped) should be available to the Meridix server on a public accessible URL where each individual resouce can be accessed with the url [ThemeBaseUrl]/[ThemeName]/[ThemeResourceRelativePath] ex: http://mycompany.com/Themes/CustomTheme/css/base.css where the http://mycompany.com/Themes is the Theme base URL part and CustomTheme is Theme name and css/base.css is the ThemeResourceRelativePath.
In this case each time a resource is requested (and not found in the server cache) the system loads the resource from the external resource url internally and the caches the resource for future requests.
This method is only recommended during developent of new themes because it requiers the Meridix installation to make several HTTP requests to get the theme content. But its the easiest way to design new themes since you can change the content on a server controlled by you and it will be used by the Meridix installation.
| Note |
|---|
| Should not be used in a production environment since it forces the server to make several HTTP requests to get the resources. So when you have used this method during the design phase compress the folder to a zip file with the name [ThemeName].zip and change the Theme package type setting from folder to Zip file. |
...