This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
CSS Refactoring #794
Labels
core-team
indicates that the issue will be completed by a core team member
Comments
This was referenced Nov 10, 2016
Merged
jglovier
added
the
core-team
indicates that the issue will be completed by a core team member
label
Jan 17, 2017
what do you think about separating route stylesheets from general reuse component stylesheets |
i can extract basscss into an ember addon |
jglovier
changed the title
The Great CSS Refactoring of 2016
The Great CSS Refactoring of 2017
Jul 6, 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stale
bot
removed
the
wontfix
indicates an issue/pull request will not be worked on
label
Aug 7, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It's time to level up our CSS game. Our current CSS is not up to best practices for CSS authoring, and has a lot of room to improve it with some newer CSS approaches that have developed since I started writing the CSS a few years ago. There has a number of problems, or areas for improvement. Here are the highlights:
Problems
Opportunities
Gameplan
Work is taking place on the
css-cleanup
branch.🛠 💻 ⚖
cc @HospitalRun/core-maintainers
The text was updated successfully, but these errors were encountered: