# Notion like Editor

**URL:** https://meta.discourse.org/t/notion-like-editor/273130
**Category:** Feature
**Tags:** composer, completed
**Created:** [July 28, 2023, 7:56am UTC](https://meta.discourse.org/t/notion-like-editor/273130 "2023-07-28T07:56:25Z")
**Posts on this page:** 9
**Page:** 2

<div class="post-metadata">

### Author: ![Arkshine](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/arkshine/32/298682_2.png) [@Arkshine](https://meta.discourse.org/u/Arkshine)
#### Post date: [May 20, 2024, 1:34pm UTC](https://meta.discourse.org/t/notion-like-editor/273130/24 "2024-05-20T13:34:34Z")

</div>

It doesn’t surprise me. TipTap looks really good and solid. 😄

On a side note, I noticed that TipTap is actually a wrapper around [ProseMirror](https://prosemirror.net/).

> Tiptap is a headless wrapper around [ProseMirror](https://prosemirror.net/) – a toolkit for building rich text WYSIWYG editors, which is already in use at many well-known companies such as _New York Times_, _The Guardian_ or _Atlassian_.
> 
> Create exactly the rich text editor you want out of customizable building blocks. Tiptap comes with sensible defaults, a lot of extensions and a friendly API to customize every aspect. It’s backed by a welcoming community, open source, and free.

I will give it a try later. It sounds really interesting. I have yet to see if the TipTap API, which I assume makes the ProseMirror API usage easier, can bring all the power ProseMirror offers.

* * *

EDIT: Actually I should read the topic, it has been already pointed out multiple times above 🤣

---

<div class="post-metadata">

### Author: ![almereyda](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/almereyda/32/367792_2.png) [@almereyda](https://meta.discourse.org/u/almereyda)
#### Post date: [June 21, 2024, 8:31pm UTC](https://meta.discourse.org/t/notion-like-editor/273130/25 "2024-06-21T20:31:00Z")

</div>

Outline implements a TipTap-based, block-like editor on top of the Y CRDT, very much like AppFlowy. The latter has its own block editor.

The AnyType editor seemed very powerful, when glancing at it. Yet I don’t know how tightly it couples to its underlying MongoDB storage.

Maybe their source codes can give inspiration in how to build something similar?

Unfortunately the low code Airtable and no code Notion alternative FLOSS scene is mined. Sometimes it’s only parts of the application, that are really FLOSS.

> **[BlockSuite | Content Editing Tech Stack](https://blocksuite.io/)**
>
> Content Editing Tech Stack for the Web

from AFFiNE seemed interesting, when playing with it.

Notea also has a nice and calm block editor.

The only implementation of the

> **[Block Protocol](https://blockprotocol.org/)**
>
> An open standard for data-driven blocks

on the other hand seems to be the overwhelming hash.ai?

There are many examples to learn from. How to do it right? What is the benefit over the versatility of plain text Markdown mixed with HTML and bbCode, plus autoboxes?

How would a block editor impact ActivityPub federation? What could it mean to federate individual blocks? Could this work potentially support the development of federated transclusion of blocks even?

---

<div class="post-metadata">

### Author: ![thoka](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thoka/32/115652_2.png) [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [October 8, 2024, 7:28am UTC](https://meta.discourse.org/t/notion-like-editor/273130/26 "2024-10-08T07:28:57Z")

</div>

fyi:

> **[ProseMirror vs Lexical performance test](https://discuss.prosemirror.net/t/prosemirror-vs-lexical-performance-test/7681)**
>
> Hey everyone, At Emergence Engineering we were curious about Lexical, Meta’s relatively new rich text editor framework. We’ve been working with ProseMirror for a long time, and a new contender in this space is always interesting, especially if...

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [October 24, 2024, 12:51am UTC](https://meta.discourse.org/t/notion-like-editor/273130/27 "2024-10-24T00:51:44Z")

</div>

> [@sam](#):
>
> The big tricky thing here is the 2 way. markdown ↔ html bridging. Giving up on markdown is something I would like to avoid with any experiments in this space.

It might be worth looking at the functionality of the editor that’s built into Obsidian. It’s a markdown editor that renders markdown as you’re editing. It only shows the markdown syntax for the text that’s under the cursor, otherwise you see the rendered text. That seems like the best of both worlds.

It seems that it might be built on top of CodeMirror: [CodeMirror 6.0 Stable Release | Hacker News](https://news.ycombinator.com/item?id=31666186).

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [October 24, 2024, 6:12am UTC](https://meta.discourse.org/t/notion-like-editor/273130/29 "2024-10-24T06:12:01Z")

</div>

And on mobiles/tablets it shows markdown how? Because if it fails with touch screens, then it is just for one environment and there must be another toggle for that.

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [October 24, 2024, 6:19am UTC](https://meta.discourse.org/t/notion-like-editor/273130/30 "2024-10-24T06:19:43Z")

</div>

> [@Jagster](#):
>
> And on mobiles/tablets it shows markdown how?

I have no idea, but you’re right that it could be an issue. I’m just suggesting it as an interesting implementation to look at.

Edit: it has more or less the same functionality on mobile as on the desktop - essentially a hybrid markdown/wysiwyg editor. I’m very partial to markdown, so am obviously biased.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [October 24, 2024, 6:34am UTC](https://meta.discourse.org/t/notion-like-editor/273130/31 "2024-10-24T06:34:12Z")

</div>

I’m just another end user in this matter 🤪 But until we get WYSIWYG at some poin in the coming future, another toggle button wouldn’t be any issue in UI/UX wise — coding such functionality would be totally another story. Even WordPress has that _show code_ button (editor system is awful mess in WP, though. It broke totally when Automattic decided go to _look first, content last_ vision).

I still see that the most important thing would be a setting to hide toolbar totally, except file uploading. Mobiles have it already (as an eastern egg 😏), though. I see that more important to do than editor improvements or changes.

We have two different user categories:

- a huge majority that almost never write anything and need really low threshold (is that right word…) to comment
- power users who need a big variety different tools and easy access to those

But of course that depends of niche of forums. But my bold claim is that is true on majority of forums.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 12, 2025, 11:51pm UTC](https://meta.discourse.org/t/notion-like-editor/273130/32 "2025-03-12T23:51:07Z")

</div>

Discourse is now shipping an experimental WYSIWYG composer 🎊

> [@Test our new composer!](https://meta.discourse.org/t/test-our-new-composer-on-meta/352347/1):
>
> We have been working on a new rich text editor mode for our composer so that it’s easier to write on Discourse. We’re now ready to start testing it out to get more feedback from our community on this feature! Our implementation builds upon the excellent [ProseMirror](https://prosemirror.net/) and its non-core [Markdown module](https://github.com/ProseMirror/prosemirror-markdown), using the module’s schema, parsing, and serialization definitions as the base for further Discourse-specific features. This topic will serve as both a guide to testing the new composer and a hub for…

This gives us all the building blocks for notion like experiences.

Given this this @TheDarkWizard do you consider your broad request complete.

I am going to close this so we can redo specific feature requests for the new composer like smarter context menus and so on.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [March 12, 2025, 11:51pm UTC](https://meta.discourse.org/t/notion-like-editor/273130/33 "2025-03-12T23:51:18Z")

</div>



[Previous page](https://meta.discourse.org/t/notion-like-editor/273130.md?page=1)
