While developing an own add-on, which uses plonetheme.onegov as dependency, I figured out that in my add-on configure.zcml I need to put the "include" directive after the one for the additional css file, like:
<configure
xmlns:theme="http://namespaces.zope.org/plonetheme.onegov">
<theme:add_scss path="resources/custom.scss" />
<include package="plonetheme.onegov" />
</configure>
Otherwise the reversed order described in here https://github.com/OneGov/plonetheme.onegov would include the plonetheme.onegov configuration above the custom.scss, therefore "appending" the custom.scss as last sass file to the plonetheme.onegov files. So the variables of e.g. resources/sass/variables.scss seems to have more weight than the ones of custom.scss and custom.scss would have no effect than. Seems it work's like the other way around than the CSS cascade here.
While developing an own add-on, which uses plonetheme.onegov as dependency, I figured out that in my add-on configure.zcml I need to put the "include" directive after the one for the additional css file, like:
Otherwise the reversed order described in here https://github.com/OneGov/plonetheme.onegov would include the plonetheme.onegov configuration above the custom.scss, therefore "appending" the custom.scss as last sass file to the plonetheme.onegov files. So the variables of e.g. resources/sass/variables.scss seems to have more weight than the ones of custom.scss and custom.scss would have no effect than. Seems it work's like the other way around than the CSS cascade here.