Thanks for the feedback, much appreciated!
About the nested html/css, I had to follow the spec here: https://github.com/gothinkster/realworld-starter-kit/blob/master/FRONTEND_INSTRUCTIONS.md
It's out of my control but I agree with you, I wouldn't nest html this way either.
Do you have any public link with this kind of dynamic CSS implemented?
I didn't use any global scoped state within components but I was on the fence about using in pages. Ideally every view would be a product of the parameters, but in the end I wasn't able to find a nice way to preload each route's state so I just left at that.
I think it does make sense to have some global state. A "current errors" cell is a good example, or a global route cell
It's always good when you can encapsulate it when the state is an implementation detail of a particular element
I don't have a good example of dynamic CSS handy, sorry