Changes between Version 27 and Version 28 of DeveloperGuidelines/Themes/SCSS

Timestamp:

07/05/18 13:02:09 (7 years ago)

Author:

Dominic König

Comment:

--

DeveloperGuidelines/Themes/SCSS

@@ -63 +63 @@
 Note that modifying any of the SCSS configurations or sources in {{{default/scss}}} would require to rebuild ''all'' themes based on it (including default itself, of course), in order to propagate the changes.
 
-While this is a good way to let all themes benefit from fixes and enhancements developed for the default theme, major changes in the default theme ''could'' also conflict with the design of derivative themes. In some cases, this can be solved by introducing additional settings in {{{_config.scss}}} - but over time such enforced backwards-compatibility could lead to undesirably complex SCSS that becomes hard to maintain.
+While this is a good way to let all themes benefit from fixes and enhancements developed for the default theme, major changes in the default theme ''could'' also conflict with the design of derivative themes. In some cases, such conflicts can perhaps be resolved by introducing additional settings in {{{_config.scss}}} - but over time, enforced backwards-compatibility could lead to undesirably complex SCSS that becomes hard to maintain.
 
-To not let such dependencies prevent future development of the default theme, they can be resolved by simply copying the original SCSS source from {{{default/scss}}} into the dependent theme's {{{THEME/scss}}}, before changing the SCSS in default.
+To not let this kind of dependencies prevent future development of the default theme, they can be resolved by simply copying the affected, original SCSS source from {{{default/scss}}} into the dependent theme's {{{THEME/scss}}}, before changing the SCSS in default.
 
 In the same way, a theme can be made entirely independent of default SCSS by simply copying all remaining SCSS sources from {{{default/scss}}} into {{{THEME/scss}}}, before changing the SCSS in default.