Frequently Asked Questions
General
What is the idea of SPOT CSS framework?
Why did the SPOT CSS methodology was invented, why was the framework created and what is it actually good for?
What are the advantages of SPOT CSS?
Why is it worth using the SPOT CSS methodology and framework? What are the main advantages?
Are there any disadvantages of SPOT CSS?
Is it really suitable for every type of project? Are there any disadvantages of using the SPOT CSS methodology and framework?
Is it possible without the SPOT CSS framework?
I like the idea of SPOT CSS in how tidy the code is, but can't I use these principles without using a framework?
What are the benefits of rewriting code to SPOT CSS?
Can't decide whether to refactor your current project to SPOT CSS? Here are the benefits before, during and after refactoring.
How to refactor (S)CSS code into SPOT CSS?
How to refactor your current (S)CSS codebase on your project safely and quickly into SPOT CSS?
Best Practices
Do not style standard HTML elements as components
Creating components from the basic semantic elements such a <a>
, <p>
, <h1-h6>
, <img>
, <ol>
, <ul>
, <li>
, <strong>
, <table>
, etc. will lead to overload the component with many variants and contexts and it becomes unmanageable.