Oops. 😂

I also don't have anything personal against Theo even though his latest dramas and how he's using his viewerbase to rile up to defend his opinions made me unfollow him and doge his content, I still think he's good at what he's doing (if he's not into fueling dramas again).

Makes me sad to read this stuff. I always was/am fanboying for a lot of US tech companies / startups and love what they output but seeing how some people talk about us just because of our laws/continent leaves a bitter taste.

If you have more questions, feel free to hit me or @tiptap.dev up.

Btw, if you find time to test it - let me know how it went and what to improve!

Kinda! But I'm happy it's out. Now waiting for feedback/issues popping up so we can make it more bulletproof! :)

Thanks for the kudos!

Thanks! Currently going through their official guide already and also must say the console errors / warnings are really good at guiding you.

My biggest issue probably is understanding the syntax rules (when to use arrows, parentheses, when to use Ok/Some/None)

Looks super cool! Thanks for sharing! I love practical guides/tutorials so this is perfect.

I hope Gimp and Inkscape could get the Blender treatment and suddenly become way better when it comes to UX an quality in details.

I liked Affinity for selling their product once - but their business model was hard to be sustainable.

To this day I'm unsure when to do something as a major or minor. Even a minor typing change can break builds/releases for thousands of people.

"Users were ramping up and the way we were doing releases before, pressing that button was very scary because we didn't know if we could break many tools in the ecosystem". - @patak.dev

I feel this so much, I can't imagine how much worse this feeling must be at the scale the Vite team is/was at.

Congratulations! You just unlocked your own Tulpa!

Will do!

Atomic block level nodes are serialized like this:

::: nodeName {attrA="valueA" attrB="valueB"}

And non atomic block level nodes like this:

::: nodeName {attrA="valueA" attrB="valueB"}

Content

:::

The "@" here is customizable - a Tag node for example could look like this:

[tag type="bug" size="sm"]

A good example would be Mentions / small atomic elements in general. HTML is pretty verbose while a small Markdown tag is easy to read and write.

Example: (Picked a Shortcode-like syntax for inline nodes).
[@ label="John Doe" id="@john"]

I think having HTML Serialization/Parsing as a Fallback is important, looking into that as well.

Having the option to come up with custom syntax however is really helpful to keep Markdown content readable / easily streamable.

Sorry to hear that! Hope it's nothing too serious and you are fine though!

Sounds great. I planned to check out Blocknote soon to see what you guys are cooking. Is this already released?