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
Bowerizing #73
Bowerizing #73
Conversation
Just had a quick look on it, here are my comments:
|
Thanks so much for the commit! Separation LGTM at the moment but need to have a closer look. We haven't discussed including Grunt plugins other than we have. We don't need the tasks that you included, it's just something that is opinionated and I don't think we should add to much of this stuff in there. We could try to remove something tho…
We don't want to add any complexity for developers. They should use it with Bower or just as a drop in, so there is no real space for prefixer or something. We had the sass-mixins repo as dependency in the early stage of this project and this didn't proof to be a good way to integrate with existing websites. Again, thanks for the great work. We really appreciate it :) |
Actually |
I can remove the grunt options and just send back with the separated Sass (config, core and theme). LMK. |
Sounds perfect :) |
@drublic Thanks. G2K 🤘 |
@drublic Updated commit when you're ready. Thanks again for the tip above, |
Thanks for your work @grayghostvisuals. I've merged your changes into the wip-1.1.0 branch. Great stuff. |
Changes and adjustments based on Issue #66 which also includes aspects from #58.
A couple of notes:
!default
flag allowing authors to override them from an outside source.@extend
placeholder (this can be improved upon as we go). The%modal-theme
is your general/global defaults. Other separated placeholders can become more specific.Gruntfile.js
) and Live Reload because, hey, we like instant feedback right?Ok now lets discuss 🤘