tiptap v2

[philippkuehn]

First of all I would like to say thank you for the last year. You made tiptap to what it is today – probably the best rich text editor for Vue.js 😛

Tiptap hits 200K downloads per month now. Incredible!

However, there is always something to do and a new major version is a good opportunity to tackle some bigger challenges. I would like to say that I have officially started the development of tiptap 2! 🎉

In this thread I want to show the first new features and keep you up to date for new ideas. Please write your wishes here so that we can discuss them! ✌️

🏗 Some updates about the project structure

Move packages to its own organisation

tiptap -> @tiptap

Split tiptap-extensions into multiple packages

Splitting the extensions into separate packages has the advantage to better optimize its bundle size. Especially if there are some larger dev-dependencies like hightlight.js for syntax highlighting. It's also easier to release alternative packages like @tiptap/highlight-code-extension and @tiptap/prism-code-extension.

@tiptap/bold-extension
@tiptap/italic-extension
@tiptap/code-extension
…

Move Vue.js components out of the core

The Vue components will no longer be part of the core. Maybe I'll also try to release a React package – but I'm not quite sure yet if I want to do this to myself 😅

@tiptap/core
@tiptap/vue

Move core extensions out of the core

So they won't be core extensions anymore. Makes it easier to define custom documents like this.

@tiptap/document-extension
@tiptap/paragraph-extension
@tiptap/text-extension

Create extension collections

For a better quick start for people who just want to use the full functionality of tiptap, I can imagine putting together collections.

import extensions from '@tiptap/starter—kit'

new Editor({ extensions })

TypeScript #54

I see the advantages of TypeScript, so I will try to rewrite tiptap completely in TypeScript.

Combine landingpage and docs

The documentation is really awful at the moment. That will change. In my mind there is a guide with integrated demos.

E2E tests

At the moment there are just some function tests which is not enough. To provide better stability, I would like to write some E2E tests.

🔥 New Features

Chained Commands

Chain a list of core commands.

editor
  .focus('end')
  .insertText('at the end')
  .newLine()
  .insertText('new line')
  .toggleBlockNode('heading', { level: 2 })

Or register your own commands.

editor.registerCommand('log', (next, editor, text) => {
  console.log(text)
  next()
})

editor.log('hey!')
// 'hey!'

Commands can be asynchronous too.

editor.registerCommand('insertUserName', await (next, editor, id) => {
  let response = await fetch(`/api/${id}`);
  let data = await response.json()
  editor.insertText(data.user.name)
  next()
})

editor.insertUserName(123)

Global node attributes

Not sure about final syntax for this but basically I want to provide an option to add attributes to multiple nodes or marks at once.

So instead of repeating attributes (like text-align #180)…

class Paragraph extends Node {
  schema = {
    attrs: {
      textAlign: {
        default: 'left',
      }
    }
  }
}

class Heading extends Node {
  schema = {
    attrs: {
      textAlign: {
        default: 'left',
      }
    }
  }
}

… you can register global attributes.

editor.registerAttribute(['paragraph', 'heading'], {
  textAlign: {
    default: 'left',
  }
})

More ideas?

Comment here and let’s discuss your ideas! I will also go through the existing issues soon and tag with v2 if possible.

☠️ Things I'm not gonna do in v2:

Markdown support

After playing around with ProseMirror and CodeMirror, I absolutely don't see any point in integrating Markdown support. Just use CodeMirror (or something else) and export/import from/to tiptap.

[k2042]

Please make text alignment an out of the box feature.

[rasliche]

This is a great update. I'm glad to see you are still excited about working on the project. A lot of how TipTap works is out of my wheelhouse, though every time I leave and come back to it on my own project I dig a little deeper and learn a little more. I'm overall very impressed with the work you've put into it and the implementation (at least by limited working knowledge).

The only negative feedback I have, and I admit it's pretty reactionary is: forget React. Focus 100% on making this the best damn text editor in the frontend landscape. React has enough of everything their ecosystem needs. Unless you have a plan or need to monetize tiptap that involves reaching into React pockets, don't dilute the work too much. Even after you've pulled the core out, I think I can speak for a lot of people when I say we'd much rather have some better documentation and examples.

This is obviously just my opinion, and it's your project that you use for a business so I know you're going to do what you have to and that is 100% understandable. But I say forego React implementations unless you've got a killer reason to do so.

Chained and custom commands are 🔥🔥🔥. Looking forward to that.

Documentation is not excellent, but it's pretty good. The source code is hard for me to parse though, but I'm not super familiar with Class syntax, so maybe that'll change when I learn more. There were some good examples in the github issues that I think could be put to use in the documentation (looking at you, iframe/image examples).

Also examples of how to style an editor would be neat, but I don't want TipTap to have an opinion, more like the Vue.js Cookbook examples where those are opinionated by the author, but not the framework, necessarily.

EDIT Again: to emphasize even more that I super appreciate your creation, and open-sourcing, of TipTap so far. I've learned a bunch from it and it's an excellent project that I love using in my own work.

[hanspagel]

We are big fans of Vue, actually giving something back to the Vue community was the biggest motivation to open source tiptap.

Nevertheless, separating the core from the Vue part and making it available to the React community could be a big benefit for everyone. It means more discussion, more examples, more contributors and in the end, helping more people with tiptap.

[b4umchen]

thx for your great work!!! realy nice.

Multiupload for Images (carusell) would be a great feature.
We have a lot of trouble to get this work 😉

[Chrissi2812]

If all packages are separated a config tool (cli or gui) would be nice to give project starters a little help.
Maybe like vue-cli where you select which packages you want.

A nice listing, on the new landing page, of all core and community extensions would be nice too.

Otherwise im excited about tiptap 2.0 😍

[deepaksisodiya]

Hi, just want to add one thing which might be interesting for you. We should add live article support in some way. Currently I do not see a way to do it in tiptap.

Example. If we change some paragraph then from CMS then front end should reflect that.

One way to do it is to add id in each block of JSON so that if any block of given id is updated we can change it accordingly.

Correct me if i am wrong. Or do you know some other way to support live article updates?

[laurensiusadi]

Hi, just want to add one thing which might be interesting for you. We should add live article support in some way. Currently I do not see a way to do it in tiptap.

Example. If we change some paragraph then from CMS then front end should reflect that.

One way to do it is to add id in each block of JSON so that if any block of given id is updated we can change it accordingly.

Correct me if i am wrong. Or do you know some other way to support live article updates?

This don't have anything to do with Tiptap itself.

It depends on your backend technology whether it supports realtime or not. Usually you can use websocket to achieve that. Vue and tiptap itself already reactive on the front-end.

I use Feathers JS on server and client and I can change the data from a client and it will be reflected to another connected client.

[deepaksisodiya]

@laurensiusadi Make sense...Thanks for the reply.

[connecteev]

@philippkuehn Big thanks for the work that you've put into this. To help you ideate on the roadmap, here are a few of my thoughts (I'll add as much relevant and helpful information as I can, thanks for the consideration!)

• Forget about React support

I could not agree more with @rasliche here. It's only going to lead to a lack of focus. React gets enough love anyway, and there are plenty of editors in React. We really need a solid community for vue plugins like this....and building something like this requires talent, focus and is not in everyone's wheelhouse. I fear that doing a react version would dilute efforts and TIpTap will never truly reach the potential it can. I do believe there's a lot that can be done with Tiptap within the Vue ecosystem (see below).

• Better Examples / Documentation:

It's great that TipTap is renderless, but very frustrating that we can't reproduce the examples from https://tiptap.scrumpy.io/ . Right now when I try, it's a painful experience.
I agree with your decision to make TipTap renderless, so the dev has full control. But why not have a barebones repository of the examples you've already put up on https://tiptap.scrumpy.io/ ? Just put them up, make them lean and reduce bloat / unnecessary code. Before you know it others will start contributing to it with PRs. So to reiterate, have (at least) 3 repos: the core, the extensions (or perhaps one for each type of extension, though that could get overwhelming), and an examples repo that has examples of everything, from most basic to most advanced.

• Examples of Image Upload:

Add an example of image upload to that example repo (basically an official version of what people are hacking together right now: https://gist.github.com/slava-vishnyakov/16076dff1a77ddaca93c4bccd4ec4521)
Everyone wants to upload images, and everyone wants to upload images to a server. Making this dev experience painless should be a key workflow imo. Again, this code would not go in the core (renderless) repo, but in the example repo that makes use of it. As you said here, there are 3 possibilities: "drag and drop file", "add a button for selecting from your local file system" and "paste external image URL" - all of them should all make it into this repo.

• Image position (with examples):

Right now, it's not possible to specify the size / dimensions or position (left align, center / full-width, right align, fixed etc) of an image from the editor.
But you can do so in CK Editor, if you see the examples here: https://ckeditor.com/ckeditor-5/demo/#balloon
https://ckeditor.com/ckeditor-5/demo/#document
You can also specify alt text / image captions for images. I would strongly consider adding this to the core and examples to the examples repo.

• Image manipulation (with examples):

Also allow cropping (and other transformations) of uploaded images in tiptap-core.
See the examples here: https://www.tiny.cloud/docs/demo/full-featured/
In the case of TinyMCE, when you click on an image, you are shown icons to flip image horizontally / vertically, and to edit the image. If you click the 'Edit Image' button, you are further given options to crop, resize image, rotate, change brightness, blur /sharpen, contrast, color, gamma, invert.

• Support for Liquid Tags:

I added more detail on this here #553
Imo, a lot of devs would find this to be a killer feature that would get a lot more of us using TipTap. Common use cases involve embedding other articles from our sites, embedding user profiles, embedding external content (YouTube videos, StackOverflow questions, etc). A couple of examples on how to do this (for both internal and external content) would be great.

• Have 2 Editor modes:

Markdown and HTML, similar to the Markdown / WYSIWYG modes seen here. Re: Markdown support: I am a bit confused by this because markdown kind-of already works at https://tiptap.scrumpy.io/ Can you please clarify what you meant by:

After playing around with ProseMirror and CodeMirror, I absolutely don't see any point in integrating Markdown support. Just use CodeMirror (or something else) and export/import from/to tiptap.

Btw please see https://github.com/showdownjs/showdown and https://markdown-it.github.io/

• Live preview:

Like https://stackedit.io/app I would add support for this in core, so the dev can enable it if need be, and an example to the example repo that makes use of the core repo.

• Live HTML code preview:

Like https://github.surmon.me/vue-quill-editor/ I would add support for this in core, so the dev can enable it if need be, and an example to the example repo that makes use of the core repo.

• Text highlighting in different colors:

As seen here:
https://ckeditor.com/ckeditor-5/demo/#document
Once again, I would add support for this in core, so the dev can enable it if need be, and an example to the example repo that makes use of the core repo.

• Text alignment (left, right, center, justify):

As seen here:
https://ckeditor.com/ckeditor-5/demo/#document
Once again, I would add support for this in core, so the dev can enable it if need be, and an example to the example repo that makes use of the core repo.

• Multiple font families:

As seen here:
https://ckeditor.com/ckeditor-5/demo/#document
Once again, I would add support for this in core, so the dev can enable it if need be, and an example to the example repo that makes use of the core repo.

• Better support for tables:

There is absolutely no comparison between https://tiptap.scrumpy.io/tables
and the tables feature of CK Editor here: https://ckeditor.com/ckeditor-5/demo/#document
CKEditor kills it in this domain - adding / deleting rows or columns, merging cells / columns up/down works seamlessly, and the result is beautifully clean.
So once again, I would add support for this in the extensiond repo, so the dev can enable it if need be, and an example to the example repo that makes use of it.

• Extension to support charts / visualizations:

(this would be an extension of the core), similar to what is seen in the demo here: https://nhn.github.io/tui.editor/latest/tutorial-example03-editor-extensions . For the charting library, I would support the best ones out there:

1. Chart.js: https://www.chartjs.org/ (most popular, see https://github.com/apertureless/vue-chartjs/)
2. Apexcharts, demo: https://apexcharts.com/vue-chart-demos/mixed-charts/line-column-area/
3. Roughviz: https://github.com/jwilber/roughViz , demo here and here

and I should be able to do something like this in the editor:

```chart
,category1,category2
Jan,21,23
Feb,31,17
Mar,22,37

type: column
title: Monthly Revenue
x.title: Amount
y.title: Month
y.min: 1
y.max: 40
y.suffix: $

Btw, this editor experience to copy and paste from excel is amazing: https://uicdn.toast.com/tui-editor/tui-editor-preview-1520325258239.gif

• Extension to support UML diagrams:

as seen here: https://nhn.github.io/tui.editor/latest/tutorial-example03-editor-extensions
and I should be able to do something like this in the editor:

partition Conductor {
  (*) --> "Climbs on Platform"
  --> === S1 ===
  --> Bows
}

partition Audience #LightSkyBlue {
  === S1 === --> Applauds
}

partition Conductor {
  Bows --> === S2 ===
  --> WavesArmes
  Applauds --> === S2 ===
}

partition Orchestra #CCCCEE {
  WavesArmes --> Introduction
  --> "Play music"
}

Once again, @philippkuehn thanks for the great work you, @hanspagel and the rest of the contributors are doing. I hope some of these ideas (if not all) will make it into 2.0 and make TipTap even more amazing!

[Alecyrus]

@connecteev I disagree with you. Tiptap should be stay clean and concise. All the features you have mentioned above are very easy to implement by using some apis provided by tiptap. And we should do more work for powering developers to build their own editor other than implement more node/mark/extension/plugin. Specifically, tiptap are supposed to make developing node/mark/extension/plugin easier.

[ryanbliss]

One enhancement I'd love to see is a more flexible implementation of SuggestInserts. It isn't too hard to copy and paste the existing node and make a new one with a character matcher, but it'd be really nice if I could instead map certain matcher characters to certain nodes in a single place.

For example, a common use case is supporting @ mentions, # hashtags, and / commands.

The other thing I ended up writing a custom node for was a commands menu, which works really similarly as SuggestInserts, only it only works if entered in the first character of a line. The matcher filters down items that can then dynamically enter in different nodes, depending on what was selected. For example in our app, you can insert in inline inputs to update Salesforce fields, but also insert in GIPHY images and note templates. This is becoming a common behavior in advanced note-taking apps such as Notion and Quip, and it would be cool to see a baked in approach for this.

Great work @philippkuehn! So excited to see what you come up with, let me know how I can help!

[habitate]

I feel that the server side rendering support can be much better in the next version. This would make the dev experience much better.

[connecteev]

@ryanbliss +1 on your suggestion. Would you be willing to share the code from your custom node (for suggestinserts and the custom commands menu)? I'd be interested in seeing what you have come up with.

[jonasdumas]

Thanks for your amazing library! We use it and are big fan. Looking forward to see next release !

[Neophen]

It would be awesome to have a nicer way to position menu bubble.
As there is quite a few caveats with menu-bubble positioning.
I'm trying to work this out now with popper.js and vue-portals. If anyone has any clue on how to achieve this please ping me :)

[Chrissi2812]

Hey @connecteev, some thoughts on your ideas

• Forget about React support
  If the core gets split from the Vue stuff (most should be examples only anyway) we would also get some React-devs in that would contribute to the core. And add extensions which can then be ported to Vue if they require React.

• Better support for tables:

  There is absolutely no comparison between https://tiptap.scrumpy.io/tables
  and the tables feature of CK Editor here: https://ckeditor.com/ckeditor-5/demo/#document
  CKEditor kills it in this domain - adding / deleting rows or columns, merging cells / columns up/down works seamlessly, and the result is beautifully clean.
  So once again, I would add support for this in the extensiond repo, so the dev can enable it if need be, and an example to the example repo that makes use of it.

  I cant find anything tiptap can't do that ckeditor offers regarding tables. (Correct me if I've missed something in the linked example)
  Merging of cells is even simpler in tiptap than in ckeditor as you just have to select cells and press the button to merge them.
  The only thing missing from the example is the modal to predefine the size of the table (should however be not that hard to implement)

• Live Preview
  tiptap is a WYSIWYM-Editor so a Preview doesn't make much sense (you have kind of a preview) , or should be implemented by the dev

• Have 2 Editor modes
  You should be able to switch tiptap off like in this Example of Prosemirror
  https://prosemirror.net/examples/markdown/
  Would require some work to adapt it to tiptap however.
  Would also be possible to implemnt a CodeMirrorView to have the HTML Preview you asked for.

Most of the other Ideas (imho) should become separate extension (not everybody needs an image editor) as mentioned by @Alecyrus most of them just don't belong in the core.

[Neophen]

Also would be awesome to have a discord/gitter some sort of community chat where people could ask for help and talk about other stuff.

Whenever i find a package/plugin and it has a chat it's amazing as you can ask for more intricate cases which sometimes the docs don't cover. and you get more people participating in updating docs :)

just my two cents :)

[rasliche]

I've come around quite a bit from my first comment, but I'd still really like to see some extended documentation like yesterday. It seems like some of them are just plain wrong? Examples don't work or there isn't enough context for me to get started, personally. Fully willing to admit it could be a problem with my lack of knowledge. But I know I've got the time and excitement to start contributing some standalone extensions, but I'm not sure it's very clear where to even get started with doing that.

I fully agree that some place for the community to congregate and share is needed like @Neophen said.

[robguthrie]

Thanks for your incredible work!

I think you've made the right choice about Markdown. It's a completely different thing and users who want MD don't want WYSIWYG features. I'm working on a converter/alternative interface right now and I'm really happy with the results so far.

[guotie]

what about font color, font size and font family

[amanharwara]

Is there any ETA on when we can expect this update?

[BrianHung]

I think you've made the right choice about Markdown. It's a completely different thing and users who want MD don't want WYSIWYG features. I'm working on a converter/alternative interface right now and I'm really happy with the results so far.

I sort of agree with not supporting Markdown as text input, but the ability to define Markdown imports and exports explicitly within each node would be nice. Currently, I know TipTap supports HTML and JSON export, but Markdown as a data format is more familiar for non-developers (there's a lot of Markdown editors).

[stritti]

Would be great if pasted HTML could be sanetized eg. by using vue-sanetize. This could prevent from damaging by pasing funy things ...

[philippkuehn]

@stritti can you show me an example for breaking things on paste?

[stritti]

@stritti can you show me an example for breaking things on paste?

hi @philippkuehn ,
for example you define an editor for content without a-links. Just text. Then you are able to copy&past HTML-content having links although. Not sure what's happening if you paste something containing iframes or scripts.

[philippkuehn]

@stritti nothing happens ;) it will be stripped.

[StefKors]

@hanspagel might just become a sponsor so I have something to play with during the winterbreak 😄 super excited to see the new features 🚀

[hanspagel]

@StefKors I might be biased, but do it! 🙃

@philippkuehn is doing an amazing job, and it’s definitely worth a few $ per month. Right now, we’re trying to fund the development through our own company, but every sponsor is a huge motivation to keep the pace. Just a few numbers:

• 1,500 commits (v1 has 1,100)
• 515 hours of development (188 hours last month alone)
• 200+ tests (v1 has not even 20)

[gavinhewitt]

@StefKors I might be biased, but do it! 🙃

@philippkuehn is doing an amazing job, and it’s definitely worth a few $ per month. Right now, we’re trying to fund the development through our own company, but every sponsor is a huge motivation to keep the pace. Just a few numbers:

• 1,500 commits (v1 has 1,100)
• 515 hours of development (188 hours last month alone)
• 200+ tests (v1 has not even 20)

@hanspagel You could in addition do paid extensions. Just a thought...

[kollol-dev]

How about Inline Delete/Remove Floating Button?

I think this will get more user friendly. Users don't have to press undo / redo button so many times if there inline floating delete button like editor.js.

[Alecyrus]

Thanks @Auxxxxlx for sponsoring our work! We want to make sure to have enough time to gather feedback from everyone as personally as possible, so we’re inviting 2-3 people per week only. You have been around here for so long, and have been so helpful to others, I invited you today. Excited to hear your feedback! 🙃

To everyone else: Thanks for your patience! 🙌 All sponsors will get access this month, everyone else in January/Februar. A short newsflash:

• The documentation is coming together nicely, we’ve written 60 pages or so and 2 are missing.
• We’re ironing out glitches in the behavior that existed for too long in tiptap 1.
• Node views became so powerful, we dedicate them a few examples and an own guide now.
• We took the collaborative editing experience to a whole new level, including a provided backend. 🤯
• Also, we’re working on a few really amazing examples. 👀

Thanks, glad to see that. I want to know how to get the access to tiptap v2 repo...

[hanspagel]

@Auxxxxlx I’ve sent you multiple invites, but they don’t seem to reach you. Please send me an email to humans@tiptap.dev and we’ll set you up.

[lofcz]

Jeez, waiting for TipTap v2 be like:

[ShenQingchuan]

I am a college student and I would like to use TipTap v2 in my graduate design project.
May I access that repo? [ Already done sponsored plan payment. ]

[hanspagel]

You’re all so supportive, thank you so much! We hit the $1,000/month milestone thanks to all the lovely sponsors! This will help us to fund the ongoing maintenance of tiptap. 🤯

I’m starting to go through all open PRs and issues. Don’t expect us to add new features to v1, but we’ll make sure to add regression tests to v2 for every open bug report. Also, we will fix a few of the most annoying bugs for v1 for all the people that need to stick with v1 for a while.

Regarding the release date of v2: We’re aiming for February.

Regarding invites: All new sponsors should get an invite to the tiptap 2 repository automatically. If you didn’t receive yours, reach out to humans@tiptap.dev. I’ll set you up! 💖

[HelloAlexPan]

Hey @hanspagel, is the team at @ueberdosis still on schedule for v2 release this month? Can't wait to try out the new tiptap!

[BrianHung]

Regarding invites: All new sponsors should get an invite to the tiptap 2 repository automatically. If you didn’t receive yours, reach out to humans@tiptap.dev. I’ll set you up! 💖

@hanspagel Would it also be possible for contributors / those who have submitted PRs to tiptap v1 to get early access to tiptap v2?

[hanspagel]

@AlexFromStoripress It’s hard to give time estimates, but I expect a public beta in March. 👀 A little bit more insight:

Yes, Philipp and I are basically working full time on tiptap v2. To date we tracked around 800 hours. To put this into perspective: We hoped to publish v2 after 300 hours and that already felt like a huge commitment. 😬 The whole project got way bigger, but a lot better too. It’s definitely worth taking the time.

Also, there is already a tiny but pretty active community with around ~120 people (sponsors, regular contributors …) having access and that’s a great way to have enough feedback to build something really good, but also not too much so we can get back to everyone personally and in time.

It feels like a great way to build something – what I think is already – outstanding.

But yes, we can’t wait to share it with all of you! There is a short list with things that eventually lead to breaking changes. We’d really like to get at least those right before transitioning to a public beta where all of you can test the new version and give feedback.

In the end, that’s what we’re building it for. For all of you, so you can build cool things with tiptap. ✌️

[hanspagel]

I’ve put together a blog post describing the current state of tiptap 2, including an interactive demo:
https://blog.ueber.io/post/tiptap-2-0-beta/

TL;DR

• We transitioned from alpha to beta!
• Vue 3 support!
• Tons of new extensions!

We’ve set an ambitious sponsorship goal of $5,000/month which would help us to keep the pace to work on the hundreds of amazing ideas we still have in our backlog. If your company uses tiptap, please convince them helping us with the sponsorship goal. Reach out to humans@tiptap.dev if you need help with that. 🙌

[literakl]

Would it be too difficult to implement a switch between WYSIWYG editor and source code editor? Some mark down editors have such functionality.
Thanks for a great product.

[hanspagel]

Good news: Thanks to 187 sponsors we already reached our goal by 75 %. 👀

Looks like we need to hurry and prepare everything for a public release of tiptap v2. 😊

[milu2003]

hello，我希望你们的例子像这个一样丰富
I hope examples are as rich as this one：
https://editorjs.io/

[guotie]

Hi, guys, what's things going on?

how about emojj suports?

how about social supports like @ #

[hanspagel]

We plan to release the tiptap 2.0 public beta next week, probably on Wednesday. 👀

It’s written in TypeScript, will come with a handful of new and amazing extensions, hundreds of tests, an extensive documentation, chainable commands, first class collaborative editing support, integrations for Vue.js and React, guides for Svelte, Alpine, Nuxt.js, a modern CDN build, SSR utilities, more than 60 interactive demos … I think you’ll like it. 👍️

Make sure to follow our Twitter account.

@guotie The @Mention support is amazing in v2, official #Hashtag and :emoji: extensions will follow with v2.1.

[guotie]

great news!

tiptap v2 is the most great editor in the world!

[planktonrobo]

Is it possible to use placeholder extension in React? v2 looks awesome by the way!

[hanspagel]

It’s here, the public beta of tiptap v2: https://www.tiptap.dev 🎉

Here is a little bit more background: https://blog.ueber.io/post/tiptap-public-beta/

And if you like what we’ve built, sponsor us so we can keep going: https://github.com/sponsors/ueberdosis

Thanks all for following this long, I think it’s time to close this issue. 😅

[chinela]

@hanspagel So I have been trying to look for an appropriate documentation on how to dynamically search for users when trying to do the @ mention features.

Because it doesn't make sense trying to like fetch all my entire users before doing such.

If you have a documentation pointing to this, I will appreciate

[andreasvirkus]

@chinela a new Discussions thread would be more appropriate for this request

[fyeeme]

Paste image is indeed really a very great idea, ths