bytemd VS quill

The ByteMD issue looks like it might just be an issue with dev environment and not production. Did you try the workaround/s in the other issue linked from the ByteMD issue you linked? https://github.com/bytedance/bytemd/issues/162

Seems to be a known issue: https://github.com/bytedance/bytemd/issues/96

It is similar to https://bytemd.netlify.app/ , but styled differently. I suppose, it for use with a projector, where you will be able to hide unwanted content.

I'm trying to integrate the bytemd markdown app into my SvelteKit app. I figured there'd be some issues with SSR, so I tried two methods to mitigate issues on the server-side render but neither worked.

Take a look in the bytemd source code to get some ideas on how to set up the logic. It has file uploading logic built in.

ByteMD is pretty great. Highly configurable and easy to understand codebase.

> One thing I learned is that you should lean towards letting non-technical people choose their own tools like why we largely let developers choose their own tools.

IMHO: I think a more sustainable variant of this (for your own sanity) might be to ask them which tool(s) they like and then take some time to understand WHY. But then instead of just letting them use those directly, you would either vet them first yourself or else find a similar one to those that can satisfy their needs (as an editor) AND yours (as a dev).

If I let every client/friend/family member who came to me for this sort of advice just pick their own tools, I'd end up with a bunch of Word docs with embedded copied & pasted crap from five other tools and no easy way to clean and publish them or back them up and version control them for diffing and rollbacks, etc.

I guess the dev version of this would be like letting every individual dev set up their own production deploys however they like, even if it's just some rando FTP client, instead of having some sort orderly CI/CD process.

If it's just you and your buddy and you don't mind taking the time to clean up their docs every time there's a new blog post... that's fine, I guess. But it can quickly get pretty overwhelming if you have more than user/tool to support, or you just publish updates frequently. In that case, having a nice WYSIWYG for them that's good enough, but can also generate clean structured output for you (something like Markdown or a API, as opposed to RTF, Word XML, HTML, etc.) can make life MUCH easier for you. And anyone that comes after you.

You can also build your own system off something like https://quilljs.com/, https://prosemirror.net/, or https://github.com/ianstormtaylor/slate to customize it to their needs while still getting clean enough input.

SLATE is an excellent library for creating WYSIWYG editors in REACT, I find it superior to QUILL.

Quill is a free, open-source WYSIWYG editor designed for the modern web. Let's use Quill js in form element. You can check the final HTML code at the bottom of this post. (￣y▽,￣)╭

React-Quill is a React component that wraps the Quill rich text editor, providing a seamless integration with React applications. Quill itself is a powerful, customizable, and open-source rich text editor that offers a variety of formatting options, such as bold, italics, lists, links, and more. React-Quill leverages the flexibility of Quill while fitting perfectly into the React ecosystem, making it easy to manage and extend.

Speaking of text, here's another one for you. Quill is a rich text editor also built for compatibility and extensibility. The latest version prevents mistakenly overriding theme default toolbar settings, and Quill is now a valid ESM package for better ecosystem. There's nested Quill support, improved spelling support, and improved support for pasting from Google Docs and Microsoft Word. Check out all the changes on the Slab website.

Ontop of that this [issue](https://github.com/quilljs/quill/issues/3806) exists - which forces us to upgrade once primeNg lets us. Anyone knows a good alternative? I am done with quill and would love to use something more stable.