Continuing the discussion from Classes not registering:
I've noticed this too.
I disagree with @Arthur in that "its a little thing".
For Webflow to cater to those coming from HTML/CSS coding, or agencies wanting reusability, it really needs to iterate its style support and what "global" objects mean and how they interact with other sites under your account.
The fact that Webflow creates "compound" classes, in which you can't explicitly modify a "parent" of a compound class while on the compounded element, is a big bummer. You end up having a "style guide" with a ton of orphaned (or temporary) div's with your specific styling on it, and then chaining these individual classes in order to be able to reuse common things.
Although I appreciate the fact that the community has been asking for an integrated CMS, and I'm happy to see that Webflow has listened (but a bit concerned that everyone is ecstatic and drooling over just a cool animated video), I truly hope that there has been engineering effort put forth towards other (what I consider) fundamental items that the community have been asking for:
Number 1 for me: variables (at least) for use in classes. Eg: being able to define variables that contain styling in themselves, and apply those variables to multiple Webflow classes (similar to SASS and Less.) To "workaround" this, one has to create standalone/random/orphaned divs (see above), in order to properly cascade styles. If there were variables, and you wanted to change the definition of "primary-color", you could do it in one spot.
Having the ability to copy "Global Objects" to other sites. The big argument here was always "well, it may override classes on the destination site", and to that I say "so what, it's an advanced feature, learn how to manage your workflow properly or don't use it". Imagine having a "master" site that has all of your symbols, classes, etc. that you can copy and paste freely to other sites (yes, I know a "workaround" is to keep duplicating your "master" site, but that's at best pretty lame, and at worst a ton more upkeep.)
Proper asset management. I mean, we still can't delete or rename assets? At least there is a cool After Effects video hyping up the CMS, though.
Now, I'm a big fan of Webflow, and have faith in their ability to eventually deliver, but I really hope that some of the 20-person staff have been tasked with some of these basic/core features that have been requested for just as long as the CMS features.
I'm looking forward to the CMS beta so I can see if Webflow has addressed these items -- not because of the pretty video.