Define with XML
In the Define with Admin UI section, we covered creating Class Extensions, Extended Attribute Sets, and Related Content Sets using Mura's back-end administrator user interface. In addition to using the administrator's UI, Mura can parse a special XML file to create Class Extensions, as well as create custom image sizes, and more.
config.xml.cfm
Whenever Mura experiences an application reload, it scans for the config.xml.cfm file, and if found, will attempt to parse the file to create any pre-defined Class Extensions and custom image sizes. As you'll see in the Mura Modules section and Plugins section, if the file is located under a modules or plugin directory, Mura uses the file to obtain various settings and information about the module or plugin too.
Convention-Based Lookup
The config.xml.cfm file will be discovered in any theme directory, module directory, content type directory, or plugin directory.
For example:
{context}/themes/{ThemeName}/{context}/themes/{ThemeName}/content_types/{Type}/{context}/themes/{ThemeName}/content_types/{Type}_{Subtype}/{context}/themes/{ThemeName}/modules/{Module}/{context}/sites/{SiteID}/themes/{ThemeName}/{context}/sites/{SiteID}/themes/{ThemeName}/content_types/{Type}/{context}/sites/{SiteID}/themes/{ThemeName}/content_types/{Type}_{Subtype}/{context}/sites/{SiteID}/themes/{ThemeName}/modules/{Module}/{context}/plugins/{PluginName}/plugin/{context}/plugins/{PluginName}/modules/{Module}/{context}/plugins/{PluginName}/content_types/{Type}_{Subtype}/
As covered in the Mura Rendering section, you can nest additional module directories and content type directories within each other, and Mura will automatically search for the config.xml.cfm file in those too.
Please refer to the Elements of the "config.xml.cfm" File section for details about the file itself.