The rule scoping for the various CSS rules as it related to the various components was hyper localized to the Index Project and has several messy overlaps that need to be rectified.
Description
Once resolved, the CSS should provide better routes for expanding, and dissecting out new components in a stable fashion.
For example, there are several contexts which overlap in function, and should be combined into one series of rulesets. In other cases the naming of various components is inconsistent and needs to be corrected.
The header and footer rulesets were originally written in a more stable and isolated fashion, but the remainder of the areas mostly fall into these categories:
rulesets written specific to the Index Project homepage
rulesets written for components that generally appear across sub-pages
rulesets for items that appear only on certain individual sub-page contexts in a hyper specific way (that should be more generalized)
All three of these are intertwined in how they are specified, organized, written, and scoped in ways that don't make additions or subtractions to functionality or featureset stable enough to be considered a "design system".
Implementation
[x] I would be interested in implementing this feature.
Problem
The rule scoping for the various CSS rules as it related to the various components was hyper localized to the Index Project and has several messy overlaps that need to be rectified.
Description
Once resolved, the CSS should provide better routes for expanding, and dissecting out new components in a stable fashion.
For example, there are several contexts which overlap in function, and should be combined into one series of rulesets. In other cases the naming of various components is inconsistent and needs to be corrected.
The header and footer rulesets were originally written in a more stable and isolated fashion, but the remainder of the areas mostly fall into these categories:
All three of these are intertwined in how they are specified, organized, written, and scoped in ways that don't make additions or subtractions to functionality or featureset stable enough to be considered a "design system".
Implementation