217 posts
  • Bought between 10 and 49 items
  • Exclusive Author
  • Has been a member for 3-4 years
  • Referred between 1 and 9 users
  • Sold between 1 000 and 5 000 dollars
  • United Kingdom
NuclearThemes says

When I’m creating WP sites for clients I have a strong urge to break down my CSS files into separate areas. For example, reset.css, typography.css, and so forth. The only thing that stops me is knowing that it negatively affects load speed. In a number of themes I’ve purchased I have found this to be quite common. Is it considered good practise to do this in the themes I sell?

491 posts
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • Won a Competition
  • Referred between 1000 and 1999 users
  • Author had a Free File of the Month
  • Author had a File in an Envato Bundle
  • Bought between 10 and 49 items
+3 more
pixelentity says


You could just do it this way and then compress all css files into one min.css at the end. Therefore you can work as you are most comfortable and once compressed the page speed issue will not apply.

Using this method, you will need to included an uncompressed example head section in your download package and also a section in your docs explaining how to replace the compressed css with the uncompressed if your buyers wish to make css changes. If not done right though it could lead to lots of support requests.

This is the way we work it in our TF & CC files because we usually have reset, main & skin stylesheets, plus all of our js functionality is developed as plugins for ease of reuse & hence lots of individual import statements. Then we compress both css & js for the live sites and include the above instructions & example for any buyer who wants to get their hands dirty in the css / js code.