inyono

I see, thanks for the feedback. Going to check that out.

Additionally to the sibling comments: you can also check out the demo at demo.edtr.io that contains way more plugins. It’s pretty much what we use on Serlo.org.

Definitely a good point. Just wanted to note that you could write a renderer in some server language that outputs static HTML. And only use the editor to make that static content editable (loaded asynchronously or on a different route). The serialized state is easy to parse by design.

What you’d prefer they do? Moving rows around?

Kinda. You can integrate it into your existing CMS to make the editing (for your end users) easier, especially for “enriched” content (think interactive content, complex layout)

Would love to hear from you on how it goes :)

That’s one of the reasons we only rely on Slate for our text plugin. So we could swap Slate for some different rich-text editor in the future if we need to. Though I have to say, we are very happy with Slate.

IMHO still the best there is, at least in the React space. But yeah, stuck in beta for what feels like forever.

Yes, it’s Backend-agnostic and designed to be embeddable into any web app. It’s basically an editor framework to define your own editor and you write the glue code to your web app.

As specified in their comment and in our GitHub repository, the code is licensed under MIT.

Nope, sorry. If you send us an email, we can work something out :)

It’s pronounced Editor IO.

Web editor in the sense that the editor runs as a web app, and the default rendering output is React (although other output formats are possible).

Mobile kinda works (minimum goal is to let users do simple edits from mobile), but we mostly focused on the desktop so far.

Yes, landing page only mentions Open Source, maybe we should clarify that.

You can reach us at edtr-io@splish.dev

Core contributor of Edtr.io here:

Slate works well for editing text. Anything with a more complicated layout / UX gets really messy though, since with Slate, you always have to deal with the DOM / Slate's wrapper around contenteditable. And at least before Slate 0.50+, we (& the developers of Schul-Cloud independently of us) ran always in bugs, etc. This is why Edtr.io (similarly to ReactPages, fka ORY Editor) builds it own state management & layouting outside of Slate. And let Slate do what they do best, editing rich-text.

Also WIP: https://github.com/edtr-io/edtr-io/. Focuses on defining an easy-to-use editor with constraints for content