Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

CSS Refactoring #794

Closed
6 of 11 tasks
jglovier opened this issue Nov 10, 2016 · 3 comments
Closed
6 of 11 tasks

CSS Refactoring #794

jglovier opened this issue Nov 10, 2016 · 3 comments
Assignees
Labels
core-team indicates that the issue will be completed by a core team member

Comments

@jglovier
Copy link
Member

jglovier commented Nov 10, 2016

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

  • currently the CSS is unwieldy and inconsistently organized
    • this makes it harder to maintain for those who do know the codebase
    • and harder to contribute to when you are new; i.e. how do I know where to put the styles, or if there are existing styles for this thing? (although we need to address that with a Styleguide, too)
  • we are using bootstrap, a bootstrap theme, and a bunch of custom styles
    • not optimal for contributing and maintenance
    • constraining because of existing implementation and paradigms of the framework

Opportunities

  • move us to more modular and utility class/atomic CSS approach
    • will make it easier for maintainers and contributors by reducing the amount of CSS developers need to write
    • will make it easier for maintainers by keeping the total CSS light
  • move off of Bootstrap for styles, and use only it for the javascript behaviors we need
    • will give us more flexibility in how we want to approach the styling, from class name structure to property choice and order, etc

Gameplan

  • tidy up the structure of the files CSS refactoring #793
    • get the temp styles into the appropriate partials
    • reorganize stylesheets accordingly
  • Implement a component/utility class solution Add Basscss utility classes #797
  • Remove custom Bootstrap theme styles into our own partials Remove bootstrap theme file #804
  • Implement utility classes on things that don't need to be components
  • Make existing styles more componentized
  • Port our custom Bootstrap stylesheet into components or utility class approach
  • Remove Bootstrap for styling
  • Implement Flexbox based layout

Work is taking place on the css-cleanup branch.

🛠 💻 ⚖


cc @HospitalRun/core-maintainers

@jglovier jglovier added the core-team indicates that the issue will be completed by a core team member label Jan 17, 2017
@billybonks
Copy link
Contributor

what do you think about separating route stylesheets from general reuse component stylesheets

@billybonks
Copy link
Contributor

i can extract basscss into an ember addon

@jglovier jglovier changed the title The Great CSS Refactoring of 2016 The Great CSS Refactoring of 2017 Jul 6, 2017
@jglovier jglovier changed the title The Great CSS Refactoring of 2017 CSS Refactoring Mar 11, 2018
@stale
Copy link

stale bot commented Aug 7, 2019

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 stale bot added the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@stale stale bot removed the wontfix indicates an issue/pull request will not be worked on label Aug 7, 2019
@fox1t fox1t closed this as completed Aug 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core-team indicates that the issue will be completed by a core team member
Projects
None yet
Development

No branches or pull requests

4 participants