how to insert images inside the markdown

[evil1morty]

on the markdown editor can we insert images like decap cms ?

[kyoshino]

Currently, you need to write raw Markdown to insert images, since editor components for the Markdown widget (image, code-block and custom components) are not yet supported in Sveltia CMS as mentioned in README. I’ll work on it next month. 🙂

[kyoshino]

BTW, I have never seen/used Toast UI, but it has everything I want to do with Sveltia UI, like an enterprise-level data grid component 😆

[CarloBu]

You’ll get an image selector plus the alt and title fields right out of the box. Basically, an editor component is a nested field in the text editor, and yes, it’s a bit complicated to implement.

Ugh, I can't even understand the pain of integrating a React-based text editor framework into a Svelte project.

I noticed that the last update for the Toast editor was one year ago, which is not ideal. :/

Did you check out the Svelte wrapper project for Lexical?
https://github.com/umaranis/svelte-lexical
Would this be useful for your use case?

Also, another cool text editor that supports Svelte is:
https://tiptap.dev/docs/editor/examples/default

I am not sure if it supports Chinese/Japanese/Korean text input well.

Page CMS, based on Vue, uses Tiptap for its text editor, which has a nice UI.

[CarloBu]

BTW, I have never seen/used Toast UI, but it has everything I want to do with [Sveltia UI](https://github.com/sveltia/sveltia-ui), like an enterprise-level data grid component 😆

yeah, too bad the project is not maintainable anymore :/

[kyoshino]

I know Svelte Lexical but decided to implement by myself because

• Svelte Lexical is not localizable
• Sveltia doesn’t need all the features
• Sveltia uses it’s own UI components, like buttons, dropdown menus, etc.
• Sveltia CMS has to implement it’s own editor components anyway, including image and code

Ohh, Toast UI Editor is no longer maintained? That’s sad. The last release is Feb 2023, and it does have Chinese/Japanese/Korean IME issues even though NHN is a Korean company.

The core of Lexical is vanilla JS and is maintained by Facebook, so it’s probably a safe choice.

[CarloBu]

I know Svelte Lexical but decided to implement by myself because....

ok, I see. there is a reason. Thank you for the explanation, from the outside it looks like plug-and-play, but it's not. :)

Ohh, Toast UI Editor is no longer maintained? That’s sad. The last release is Feb 2023, and it does have Chinese/Japanese/Korean IME issues even though NHN is a Korean company.

So it was a bad call then, sorry for the little distraction.

The core of Lexical is vanilla JS and is maintained by Facebook, so it’s probably a safe choice.

yeah, that's a smart move to bet on the biggest players to keep their projects going (except google :))