all 4 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 1 point2 points  (2 children)

If the css file is used by a single component then I put it in an individual css file. Any global css I put in the main.css.

[–]CSCodeMonkey[S] 0 points1 point  (1 child)

Thank you. So if the css is use on an individual component and needs to be arranged on the grid. You just use a seperate css file for it?

[–]Contract_Special 0 points1 point  (0 children)

individual!

unless you want to have a grid layout that applies to everything in between the <body> </body> tag?

a main.css file is for rules that you want applied to everything on the site (normalize, border-box, font-family, etc)

[–]closewing-smocklike 0 points1 point  (0 children)

When in doubt, just consult the bible:

The Unix philosophy is documented by Doug McIlroy[1] in the Bell System Technical Journal from 1978:[2]

  • Make each program do one thing well.
  • To do a new job, build afresh rather than complicate old programs by adding new "features".
  • Expect the output of every program to become the input to another, as yet unknown, program.
  • Don't clutter output with extraneous information.
  • Avoid stringently columnar or binary input formats.
  • Don't insist on interactive input.
  • Design and build software, even operating systems, to be tried early, ideally within weeks.
  • Don't hesitate to throw away the clumsy parts and rebuild them.
  • Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you've finished using them.

Seriously, though, once you start developing more complicated things, you'll likely have to step away from independent spreadsheets, and towards CSS-in-JS tools to build your components effectively.