Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I suggest to create a custom theme on the side and try to concentrate your customizations in the smallest number of files possible that would satisfy your requirements. Also it is best to keep your theme files under the source code revision control. Seems to be manageable so far.

Start with adding the "extra.css" to your theme's media/style directory, then create customized templates one-by one in your theme's /templates directory.

The common issue that might arise when the code is upgraded - if some variable is removed from the context and your custom template is still using it there will be a template rendering error.

It is possible that we remove some template file or rename it - in that case your customizations will visually disappear.

Most likely there will be changes in the templates content and structure, but they will be gradual. Also, we will clearly list changed template files in the release notes.

I suggest to create a custom theme on the side and try to concentrate your customizations in the smallest number of files possible that would satisfy your requirements. Also it is best to keep your theme files under the source code revision control. Seems to be manageable so far.

Start with adding the "extra.css" to your theme's media/style directory, then create customized templates one-by one in your theme's /templates directory.

The common issue that might arise when the code is upgraded - if some any variable is removed from the context and which is still used in your custom template is still using it there will be cause a template rendering error.

It is possible that we remove some template file or rename it - in that case your customizations will visually disappear.

Most likely there will be changes in the templates content and structure, but they will be gradual. Also, we will clearly list changed template files in the release notes.