codeforboston / codeforboston/cliff-effects
Organize CSS through Project
- Dominant language
- JavaScript
- Stars
- 30
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Right now, we have inline styles and a css file. With approval from @knod, we'd like to standardize this to just the css file(s). There are three steps in our CSS journey, each better than the last, but all of which may not be necessary.
1. Move all inline styles to a CSS file.
2. Compact our myriad inline style blocks in the CSS class to reusable classes so that the CSS file is organized and not a mile long.
3. Introduce some sense of modules/scoping/variables (LESS?) or other tools that may help organize the complexity of a large amount of styling. This step is probably not necessary unless the CSS turns out to be unexpectedly gnarly.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.