Considering Roots contains Bootstrap 3.x and it only includes LESS, I want to again bring up the discussion about using Sass/Scss for Roots theme in the future. With this functionality being integrated into WordPress, even a fix to work out the dependence on Ruby, having Roots Theme work with Sass in addition to LESS would be a really good idea and solidarity to WordPress’ future as well.
I’m sure a lot of developers including me would be happy to see a Sass fork of this that’s regularly maintained and supported by the same Roots Github account.
I’d like to have a Roots generator that would allow you to do things like:
choose a different CSS framework (e.g. Foundation)
choose a preprocessor (LESS/Sass)
In the meantime, if someone wants to maintain a Sass fork (@kalenjohnson) and keep it up-to-date with the Roots repo, we can put it under the Roots org.
@benword@kalenjohnson I’d be really interested in seeing a SASS/Compass fork of Roots using the official Bootstrap SASS fork. Is there any progress on this? I’d like to contribute if there’s one in progress.
Even moreso I’d like to see a fork using Foundation, but I know that’s a bit more work in keeping things up to date. I’ll have a look into that this weekend since I am a little more familiar with Foundation than I am with Bootstrap and I was planning on using one of them with Roots for a project in the next week.
How might a Roots generator work? I guess it would have to change CSS class names in templates depending on the option selected, to start.
Currently, it’s using grunt-contrib-sass, as grunt-contrib-compass does not read the json “files” option correctly, and compiling to app.css, not main.min.css. Not a big deal, as you could change this in the gruntfile and in the script.php file, but I wanted to keep it as similar to the stock Roots theme for the time being.
As Ben has mentioned, this is all hopefully temporary until some type of generator can be coded that will allow us to choose which pre-processor and potentially choose from different frameworks to use when starting development. I think we’re all still trying to figure out the best solution to that though.
Kudos to @kalenjohnson for creating this fork that turned into a cool repo and @ben for hosting it in the roots org. Maybe a bower config will be coming soon “wink”.
Yep! It was me. I was making a hint to @ben to consider the bower branch we were discussing. I have already applied that same methodology to a couple projects I am working on.
