So as an update to my previous rant, this was the response as to why we're using webflow for a certain site that we really shouldn't be using webflow for. I know some none dev in the company are learning webflow. But if there going to push for an all webflow workflow then what's the point? I've told issues I was having in webflow but they've been brushed off. What. The. Hell.

It seemed kinda flashy when it first launched, but is it actually any good? Dreamweaver 2.0? Seems like the code would be a mess...

@ScriptCoded Basically Dreamweaver 2.0, there are a few things I dislike about it one being the combo class system if you are a designer I can see the appeal but from a developer standpoint I wouldn't used it but I'm having to use it, learn it and deal with the nonsense that comes with it. If you look at the wishlist the number of things (some very basic) that needs to be implemented is pretty surprising. https://wishlist.webflow.com/ Below is how assets are handled, no structuring whatsoever just drag and drop.

@ScriptCoded https://wishlist.webflow.com/ideas/... that is basically the combo class system, having to define classes twice, no :before or :after like really basic stuff like this is missing.

@HolyTeabags Whoa, that's pretty unholy... Perhaps some dya in the future :)

@ScriptCoded Also few things I forgot to mention. 1) You can't add custom code unless you pay for webflow, meaning the 940px drag and drop container can't be changed things like that the width option is actually locked visually so no changing the default grid system unless you pay. 2) Max 1440px breakpoint. Want to go higher? Pay to add custom code.

3) Toggling between visual and preview modes you might see a difference, elements moving etc.

So fun... fun.. fun

@HolyTeabags :/ Seems like fun...