While it's good to follow best practices to organize CSS even though the project is small, I think the current structure can still be improved in some ways:
All of the files under layout directly are styling for some forms and their elements only, should they be put under the components directory instead of layout?
Besides that, the form name (in _form.scss) is too generic.
Also, if the files were created as components, should each file contains one component only? e.g. components/_form_signin.scss to contains .form-signin component only.
While it's good to follow best practices to organize CSS even though the project is small, I think the current structure can still be improved in some ways:
UI element - modifier
, e.g.form-signin
,form-signup
, should the remaining class names follow that convention as well?form-user
instead of.user-form
https://github.com/pkordel/multisearch/blob/69d95b52581c40d1a4b4946fe397b24763eea630/app/assets/stylesheets/layouts/_forms.scss#L1layout
directly are styling for some forms and their elements only, should they be put under thecomponents
directory instead oflayout
?form
name (in_form.scss
) is too generic.components/_form_signin.scss
to contains.form-signin
component only.This is our convention just in case you want to have a look https://nimblehq.co/compass/development/code-conventions/css/#stylesheets-structure