You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Document and set some standards what css goes where, naming policy, global styles vs local etc. At this moment I am trying to keep each section's css code separate so everything is easily swapable. Also we are trying to stick to kind of BEM (block - element methodology) Each section has its name which is the first part of the name of any css class indicating to which section it belongs. Then after __ we have the element's name and its details. We are avoiding names like -red or -blue, instead indicate -button or -link to suggest the elements use instead of style.
It is not perfectly done but makes reading the css code way much easier for the future.
More on: https://en.bem.info/methodology/
The text was updated successfully, but these errors were encountered:
Document and set some standards what css goes where, naming policy, global styles vs local etc. At this moment I am trying to keep each section's css code separate so everything is easily swapable. Also we are trying to stick to kind of BEM (block - element methodology) Each section has its name which is the first part of the name of any css class indicating to which section it belongs. Then after __ we have the element's name and its details. We are avoiding names like -red or -blue, instead indicate -button or -link to suggest the elements use instead of style.
It is not perfectly done but makes reading the css code way much easier for the future.
More on:
https://en.bem.info/methodology/
The text was updated successfully, but these errors were encountered: