Css

[ghost]

Hi!
Can you please explain how css per component works. Right now it seems like i have to introduce a new file for every component and include it with a link tag on my index.html and then refresh the page for changes to take place. Is this the right process? Am I doing something wrong?
Thanks

[kaiomagalhaes]

@Andreasi I've been doing the same, I think that it is the right way as we are not using any kind of assets injector.

[Granze]

@Andreasi @kaiomagalhaes I'm thinking about improving all the CSS part of the starter kit. I'll take a look in the next days.

[kaiomagalhaes]

@Granze I`m just waiting an answer about the dockerfile merge to add a scss and a js+react lint

[Granze]

@kaiomagalhaes I know and I'm sorry for the delay. I just came back from San Francisco. In the next days, I'll sort this out as well.

[ghost]

Thanks a lot you guys! Love the kit!!!

[Granze]

So it seems I'll have some time in the next days to look at how to improve the CSS part of the starter kit.
Of course, the main goal is to stay minimal and as less opinionated as possible.

[kaiomagalhaes]

@Granze A really good thing to add would be some lints for scss and js

[Granze]

There is a JS linter already in place.

On Wed, Mar 9, 2016, 17:33 Kaio Cristian Costa Porto de Magalhães <
notifications@github.com> wrote:

@Granze https://github.com/Granze A really good thing to add would be
some lints for scss and js

—
Reply to this email directly or view it on GitHub
#32 (comment)
.

[TimKraemer]

I'd really appreciate if this awesome kit also could handle modularized css. Unfortunately I'm not able to understand and modify the watchify/gulp workflow in a way to achieve this yet.

It would be great if we could have something like import btn from './button.css' inside an example button component, having the button.css lying in the same subdir like the button component itself.
(example: https://css-tricks.com/css-modules-part-3-react/#article-header-id-3)