So, I worked a bit more with Webflow today, and there’s a lot of weirdness going on. For instance styles you cannot see in the editor, that can only be seen when publishing the page and inspecting the elements. The container element, the one that gets class w-container, works this way.
It’s incredibly hard to teach non-technical people how to use Webflow with such hidden and inconsistent behavior. I highly recommend that you set the styles visible and editable on the default elements users pick from the Add Elements functionality. That means: When a user picks a Container it should be possible to reset ALL styles to make it a div. There’s no way, except for the container icon, to tell that it has container styling on different break points.
Not sure if anyone at Webflow reads this, but I guess some of the idea with this software is to give users who doesn’t know anything about DOM,html,css, etc to be able to build semantically correct and somewhat clean pages. By e.g. mixing Section with the
<section> tag it gets incredibly confusing, and hard, for our developers to teach non-technical people about the web.
You should really aim to build this software much more like the element inspector in a browser and let users see the actual classes, styles instead of building a weird hybrid between Figma, PowerPoint and a webpage editor that use odd and confusing terminology. Your users aren’t stupid, even though they don’t know what a div is (yet). If you talk to them like smart people, they will quickly learn what a div is, and be able to communicate with more professional web developers.
Just my two cents…