Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should we provide an SCSS version? #2

Open
mrwweb opened this issue Mar 3, 2020 · 0 comments
Open

Should we provide an SCSS version? #2

mrwweb opened this issue Mar 3, 2020 · 0 comments

Comments

@mrwweb
Copy link
Owner

mrwweb commented Mar 3, 2020

My current intention with the project is to provide useful copy-and-pasteable files for WordPress themes.

Since CSS is valid SCSS, these files can be dropped into an .scss file without any issue. So, are there any ways in which a SCSS version of these files could provide extra value?

The likely changes I can think of would be:

  • Use a single layer of nesting for unqualified element selectors like .wp-block-quote cite
  • Provide some conveniences such as looped output of color classes

Are these improvements worth the extra maintenance cost? Could the CSS version be output cleanly from the SCSS version for easier upkeep? I lean toward yes on both questions but would love some more feedback!

@mrwweb mrwweb added question Further information is requested Seeking Feedback and removed question Further information is requested labels Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant