update Archetype to reflect changes made to normalize in Archetype-Utilities about archetype HOT 4 CLOSED

also need to test to be sure variable overrides are taking precedent

from archetype.

Integration of normalize.css has been an issue i've been consistently uncertain about. Normalize project documentation illustrates two distinct implementation methods: 1) integrate normalize into your project and modify to suit your needs - the downside here is difficulty in upgrading normalize after it has been significantly modified. 2) integrate as a standalone module and override rather than modify - this makes upgrading easy at the expense of potential code redundancy. After struggling with this for far too long, I think the best approach for Archetype is to include normalize as a standalone module. To accomplish this and also mitigate the redundant code issue, I believe the best way forward is to include normalize as a Sass module and breakup each of its sections into its own mixin. This will allow for easy 'disabling' of un-necessary sections of normalize on a per project bases or to test. Normalize should be kept in the base/ directory. Adding variables to normalize is a bad idea - any customizations should be isolated into their own component. Everything built ontop of normalize should be built as a component.

from archetype.

removed variables from Archetype-Utilities/archetype/_normalize.scss partial here

from archetype.

removed variables from Archetype/_settings.scss partial here

from archetype.