Looking best wysiwyg html editor for free Options

[calmabubbasst]

Hi folks

usually I use Microsoft office share point designer 2007 in order to play with my web sites html files,

unfortunately the preview isnt good and i'll love to change software with ones who give to me a real "wysiwyg".


What software could you suggest to me to reach that?

^__^

[Jason Knight]

"Best" and "WYSIWYG" do not even belong in the same sentence. They are nonsensical garbage that lulls people into THINKING they can make a website. The results are ALWAYS broken incompetent inaccessible trash that tells large swaths of users to go F*** themselves!

The very CONCEPT of it is as bass wackard as the fraudsters who call themselves "designers" when all they know how to do is spank their crank in Photoshop or Figma. Treating design as if it is art to the exclusion of all other concepts. They're artists, not designers and the fact they start out with appearance is 99% of why they're bunko peddling fools... preying upon ignorance and wishful thinking.

Design is engineering that incorporates art as one if its many facets. Far more important are specifications, guidelines, UX, accessibility, and dozens of other things WYWIWYGS, paint programs like Photoshop, wireframes like Figma, and all the other hoodoo-voodoo flips the bird at.

Content dictates markup. Content + markup + device and user limitations dictate markup, THEN do your paint-over (which these days doesn't even involved paint programs! Thanks CSS3!)

1) Start out with content of value or a reasonable facsimile of future content in a flat text editor as if HTML doesn't even exist. Put it in an order that makes sense.

2) Mark it up to say what things ARE... structurally, grammatically, as per professional writing conventions. If you choose ANY of your HTML at this point based on what you want things to look like? Then you've failed to divine HMTL's purpose and entire reason for existing!

3) Bend that markup to your will to create the screen media desktop layout using CSS. Add classes, id's, and semantically neutral containers like DIV and SPAN only as absolutely needed, and in the case of classes and ID's ONLY to say what things are or why they might receive some sort of style, NOT WHAT THAT STYLE IS!

If you can't come up with a class that explains WHY it might get "some" style, or there's no corresponding HTML tag that says WHAT it is, not what you want it to look like? Then you probably shouldn't be styling it....

Which is why bootcrap and failwind are ignorant incompetent garbage monuments to the HTML 3.2 / 4 Tranny mindset!

4) Narrow the window until the layout breaks. If you did your job stuff like flex-wrap or natural page flow will have handled 80%+ of this, since a quality layout should be semi-fluid (has a max width) and elastic (designed in EM/REM NOT PX!!!). But for the remainder throw media queries at it to strip off columnar behavior and resize elements.

5) repeat step 4 until you're down to around 16em.

It's called progressive enhancement, and it's how you build gracefully degrading accessible layouts.

As opposed to dicking around dragging and dropping stuff about in utter ignorance of the fact that what you see is not what everyone else gets.

As to preview/testing, that's what browsers are for. You can test most files locally after all... and most things you can't it's no big deal to install something like XAMPP. And don't forget to not just test in one browser, test in multiple engines! Remember that gecko, blink, and webkit all handle rendering differently... which is another reason trusting whatever junk browser fork they use in a WYSIWYG is foolish.

This post has been edited by Jason Knight: Apr 21 2024, 06:21 AM