SCSS-Library

常見問題集

Performance

This plugin adds many extra steps for something as simple as printing a style link tag inside a site:

• Check the creation time of the compiled file.
• Interacts with the database.
• Converts a SCSS file into a style file.

Obviously it will add a few millisecond to the loading time of the site.

How much will performance be affected?

It depends on how many SCSS files you add to the list of styles and how complex they are.

So I shouldn’t use it in production?

Of course you can use it. If you are looking for a fast site then you should also add a cache or optimization plugin to your production environment, although it is very likely that you have already done so. Personally I have worked with Comet Cache and Autoptimize without any inconvenience. Any problems you encounter with another cache plugin don’t hesitate to write down the details to replicate the error. Remember that the more information you include in the report the easier it will be to fix it.

Then what are you looking for with this plugin?

What I want is to emulate for the style files the ease of development offered by Timber. Let SCSS-Library be to SCSS what Timber is to Twig.

My goal with this plugin is to be able to change the SCSS file directly and see the result immediately. No previous compilations or commands in a terminal. It is intended for development teams that include graphic designers who understand CSS and HTML but prefer not to have to open a terminal; and to support lazy programmers who like me prefer to leave repetitive tasks to the machines.

Is this plugin bug free?

I don’t think so. Feedbacks would be appreciated.