Seems to be a Day of text editing today :smile: A...

# feed

[Sergey Drymchenko]

Seems to be a Day of text editing today 😄

About three months ago, I shared the first release of Cascade Editor here. Since then, I’ve continued developing it around one main idea: an editor should work for a simple rich-text field today without limiting how complex that editing experience can become later.

Some of the larger additions since the initial release:

• undo/redo, nested indentation, links, and code blocks
• HTML-like import/export with customizable profiles for backend-specific dialects
• read-only mode and support for completely external toolbars
• full support of Android, iOS, and Desktop targets
• crash containment and structured warnings for malformed imported content
• interactive custom blocks
The last item is the newest extensibility feature. Custom blocks, like tables or images, can render complex Compose UI, handle user interaction, inspect available editor capabilities, and safely update, replace, insert, delete, or focus blocks and all of this without touching editor internals.

Repo: github.com/linreal/cascade-editor

Live demo: linreal.github.io/cascade-editor

I’d be glad to hear feedback from developers working on notes, task descriptions, knowledge bases, document editing, or other rich-text experiences. I’m especially interested in what requirements or integration constraints Cascade Editor does not cover yet. If you’re evaluating it for a real product, I’d also be happy to help with the integration, API configuration, custom blocks, or backend format support.

[Sri Harsha Chilakapati]

This is amazing! The only thing I'd miss here is intra-block selection. If that is solved, then it can become pretty much an opensource Notion style editor that is unrivaled.

[Sergey Drymchenko]

Thanks! Cross-input selection turned out to be extremely complicated to implement, I'm still trying to find a correct approach here

[Michal Harakal]

@Sergey Drymchenko The HTML-like profiles + scoped custom blocks are the part that really stood out to me. They look like a surprisingly good seam for a spec-backed format like AsciiDoc, especially around tables/admonitions and a supported import/export subset. I’ve been building KMP AsciiDoc tooling on my side - happy to compare document models if that sounds interesting.

[Kashismails]

This is amazing thanks for sharing @Sergey Drymchenko, just what i was looking for