Recommended method of styling a child theme? [#2817545]

Looking at the libraries.yml file, it has the custom.css file inside of a "Custom CSS library for novice users". I'm assuming that this implies that the rest of the files should be edited instead of overridden whenever possible. However, when I dig into the UIkit and start editing, grunt/compass compilation takes forever on save since it needs to re-compile all of the scss files.

As such, from a development/workflow standpoint, I'm wondering what the recommended method is for styling a child theme that doesn't eat as much time?

Comments

Comment #1

13 October 2016 at 02:10

mrweiner created an issue. See original summary.

Comment #2

Jeff Burnz CreditAttribution: Jeff Burnz commented 14 October 2016 at 00:56

Later DEV versions use Libsass which is very fast. It's like 100 times faster (literally 100 times faster) than using Ruby Sass.

You could merge in those changes and switch over, it's basically all the in grunt file in DEV sub-themes and instead of using Gems and Bundler we use Bower to pull a small customised version of Compass Vertical Rhythm, Susy and Modular Scale. The grunt/npm install is the same etc.

Comment #3

mrweiner CreditAttribution: mrweiner commented 14 October 2016 at 22:34

Ah, I like the sound of that! I haven't started any sub-theming yet, so I'll probably just delete it entirely and re-install from dev. Is dev stable enough for production right now? Thanks for the input.

Comment #4

Jeff Burnz CreditAttribution: Jeff Burnz commented 15 October 2016 at 00:20

No, it's not stable enough, by the end of this weekend it will be, but right at this moment don't use it.

I mean it changes as I commit changes, but I know the current HEAD has a bug which I have fixed but not yet committed, I plan to commit tomorrow after some tests.