Dominik Biedebach
@bdbch.com
🧑💻 Frontend Engineer → Core Maintainer @tiptap.dev
🎸 Music → Guitar and Concerts
🎮 Gaming → Game Dev & MMOs
I'm officially in 💙 with Bluesky
https://bdbch.com/
https://github.com/bdbch
Opinions and memes are mine, not those of my employers
🎸 Music → Guitar and Concerts
🎮 Gaming → Game Dev & MMOs
I'm officially in 💙 with Bluesky
https://bdbch.com/
https://github.com/bdbch
Opinions and memes are mine, not those of my employers
If you have more questions, feel free to hit me or @tiptap.dev up.
October 24, 2025 at 3:43 PM
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!
October 16, 2025 at 7:53 AM
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 for the kudos!
October 15, 2025 at 7:03 PM
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 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)
My biggest issue probably is understanding the syntax rules (when to use arrows, parentheses, when to use Ok/Some/None)
October 11, 2025 at 8:07 AM
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)
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.
October 11, 2025 at 8:06 AM
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.
I liked Affinity for selling their product once - but their business model was hard to be sustainable.
October 11, 2025 at 8:04 AM
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.
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.
October 10, 2025 at 8:42 AM
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.
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.
October 10, 2025 at 8:42 AM
"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.
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!
October 3, 2025 at 1:40 PM
Congratulations! You just unlocked your own Tulpa!
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
:::
::: nodeName {attrA="valueA" attrB="valueB"}
And non atomic block level nodes like this:
::: nodeName {attrA="valueA" attrB="valueB"}
Content
:::
October 2, 2025 at 3:41 PM
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
:::
::: 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"]
[tag type="bug" size="sm"]
October 2, 2025 at 3:41 PM
The "@" here is customizable - a Tag node for example could look like this:
[tag type="bug" size="sm"]
[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"]
Example: (Picked a Shortcode-like syntax for inline nodes).
[@ label="John Doe" id="@john"]
October 2, 2025 at 3:39 PM
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"]
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.
Having the option to come up with custom syntax however is really helpful to keep Markdown content readable / easily streamable.
October 2, 2025 at 3:39 PM
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.
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!
October 2, 2025 at 2:06 PM
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?
October 2, 2025 at 1:54 PM
Sounds great. I planned to check out Blocknote soon to see what you guys are cooking. Is this already released?
Oh thanks! Didn't notice. Didn't change anything, I guess maybe the connection to my domain is broken.
October 2, 2025 at 1:53 PM
Oh thanks! Didn't notice. Didn't change anything, I guess maybe the connection to my domain is broken.
I can just say I'm happy when it's out and people can use it!
See the screenshot, tried to put a youtube video and table in a nested bullet list item there
See the screenshot, tried to put a youtube video and table in a nested bullet list item there
October 2, 2025 at 1:52 PM
I can just say I'm happy when it's out and people can use it!
See the screenshot, tried to put a youtube video and table in a nested bullet list item there
See the screenshot, tried to put a youtube video and table in a nested bullet list item there
I got them working for BulletLists & TaskLists already (took a lot of time to get that right, specially with nested blocks inside list items) so getting OrderedLists right is just a matter of time! 😀
October 2, 2025 at 1:47 PM
I got them working for BulletLists & TaskLists already (took a lot of time to get that right, specially with nested blocks inside list items) so getting OrderedLists right is just a matter of time! 😀
I'm currently finalizing the Markdown Feature. I hang myself up (luckily) with writing 15-20 tests which a lot had failed.
Now I'm at 97% successful coverage and just try to fix this one bug that is bothering me a lot. (Nested Ordered Lists, Markedjs's default Lexer is parsing them differently).
Now I'm at 97% successful coverage and just try to fix this one bug that is bothering me a lot. (Nested Ordered Lists, Markedjs's default Lexer is parsing them differently).
October 2, 2025 at 1:36 PM
I'm currently finalizing the Markdown Feature. I hang myself up (luckily) with writing 15-20 tests which a lot had failed.
Now I'm at 97% successful coverage and just try to fix this one bug that is bothering me a lot. (Nested Ordered Lists, Markedjs's default Lexer is parsing them differently).
Now I'm at 97% successful coverage and just try to fix this one bug that is bothering me a lot. (Nested Ordered Lists, Markedjs's default Lexer is parsing them differently).