Hi ​@Mho Salim 

Thanks for sharing this! Just to better understand your concern — when you say “rich text editor,” are you mainly looking for advanced formatting options (like headers, colors, bullet styles), or more of a document-style editor within a board? Also, can you share a bit about your use case — for example, are you trying to draft long-form content directly on a board, or just need richer styling for short notes?

Hello Eca,

thank you for attending to this inquiry. I believe the answer to your question is broadly yes. Below I am providing a simple example. 

<simple example>

Title

Heading 1

Heading 2 

1. List item
   1. Sub item (these are a. b. in Google Doc)
   2. Sub item

Normal text about the adventures of the quick brown fox in Arial font

Those same adventures in a Courier font (still shows up as  default font but beggars can’t ...)

</simple example>

I entered this text into Google Doc and then copied and pasted it here.  Notice that the mapping is not perfect (All fonts and unknown styles map to default text )  but the structure of the text broadly resembles its source. This would be sub-optimal but may be workable. Presumably these objects that we move around on the Miro board are fungible at some level and these widgets are relatively easy to include (as evidenced by this one I am using to enter this message that has different styles and some sort of mapping to generally used styles (H1, H2, ...)  It is unlikely that no one at Miro has already implemented a way to associate a text object with a stylesheet so I am guessing the question is how do we encourage Miro to expose that capability .

Again thanks for looking at this.

Mho

As for your question about if I am thinking about the length of the content I think a having a size limit is quite reasonable given what Miro is about. So If I am composing a text it is not a big deal to break it up into a bunch of smaller pieces or if I am copying something from a formatted document I can live with looking at one piece at a time.  

Hi ​@Mho Salim,

Thank you so much for walking through your example — that context is super helpful 🙌. You’re right that text objects in Miro currently support only limited formatting (size, colors, basic styling, bullets), so things like true heading styles, multiple fonts, or deeper list structures aren’t available today.

The best way to move this forward is to add your idea (with your example!) to our Wish List. I’ve converted your post to a Wishlist post so our product team can review and prioritize based on demand, and other community members can upvote your post to help surface interest.

Thanks again for the thoughtful feedback and for helping shape Miro!

I infer from your text that the underlying structure (technical, organizational, operational or even emotional) is not setup to support expanding Miro’s ecosystem beyond the code that comes out of Miro’s software team. That is certainly not uncommon even if it is unfortunate for a concept that shows this much promise. In any case, your product your rules.

I will offer three observations just in case there is more resilience (or ambition) under the hood that you imply:

1. Miro documentation recommends using multiple text objects if we want to highlight something or include a code snippet. This widget I am entering this text into, is clearly available to you and adds fits the l”lightweight, visual collaboration” criteria much better than instantiating multiple text objects. 
2. Objects are clearly fungible in this platform. Miro can provide an API for custom objects, (if you are paranoid you can limit it to integrators) so that delivers content from other end points.   The board can still stay a light weight aggregator for collaboration without insisting that all collaborators must be humans. 
3. Not offering a way to parametrize template design does not do anything to keep the weight down but limits opportunities for your ecosystem to add value. I have to use a dozen templates where I could have just one with a drop-down selector and I have to label each frame by hand when it may be auto indexed. This is inconsistent with the criteria you indicated.  

Mho