They all were. HTML was so limited that producing it visually from a WYSIWYG editor was guaranteed to be totally wrong or exceedingly verbose.
With flex and grid I imagine creating such an editor is easier today, but I also imagine those consumers are happy to work off of templates and people who work on front and know HTML and spend most of their time building react components.
My first gig was hand crafting html pages and the guy I replaced (a "programmer") used one of these WYSIWYG tools.
It wasn't that uncommon in the early days of web shops
If HTML could be used as a collection of widget akin to Windows Forms, with an easy grid system (somewhat like XAML), there building an UI page creator would be easy, and user could edit the output unlike with the current tech.
I have no idea how i had frontpage, but i'm sure it lead into acquiring "real skills".
There's a lot more to apps like dreamweaver, frontpage, etc. than it seems. They are bad tools, but also comes with a linear learning curve that has its advantages.
There was also quite a bit of elitism and protectionism about it, because for a while a lot of people were actually more or less making a living from writing nothing but plain HTML. If anyone can make a web page, what good are HTML skills? Quickly, let's find something bad about it and save our jobs!
I just looked into the nightmarish tree of nested div's and span's (of which FrontPage and DreamWeaver are innocent) that's a Twitter feed. JFC, I don't want to ever have to scrape one.
You could have it produce outstanding markup, but that meant spending a lot of quality time, playing with the templates.
Want to write documentation, or a personal website full of text and pictures? Maybe a simple text site for your restaurant or small business without much fluff? Then it's alright.
Want to do a professional-looking site that looks like the ones you pay money for? Maybe look for something else, or at the very least start with a handcrafted template, instead of "faking it" with sliced images and javascript hover.
The reaction against Dreamweaver was IMO understandable because there were definitely some people in the industry who were convinced that Dreamweaver was enough for anything.
Just like to add that from what I've found they're also generally way "too technical" for technical/programming users too. Each time I try to set one up, I waste 1-2 hours of my time trying, git pulling, refreshing, testing, reading docs, etc before realizing what a ginormous time sink it is with their various weird DSL's and hierarchical organization methods and templates and whatnot.
Today's 22MB main.min.js bundled an empty index.html script loader is much, much worse.
Wix is a nightmare.
I do see some pretty good stuff, from Wix. The new static generators create great sites, but they are way too technical for most users. Wix and Weebly are -sort of- like that.
I am not a fan of sitebuilders in WordPress. I think they are just reincarnations of FrontPage. I've had to fix a couple of borked sitebuilder sites, and the "fix" was a complete, top-to-bottom rewrite, without the sitebuilder.