๐ง๐ถ๐ฝ๐ง๐ฎ๐ฝ ๐๐ ๐ก๐ผ๐ ๐๐ฟ๐ผ๐ธ๐ฒ๐ป. ๐ฌ๐ผ๐๐ฟ ๐๐ ๐ฝ๐ฒ๐ฐ๐๐ฎ๐๐ถ๐ผ๐ป๐ ๐๐ฟ๐ฒ.
Umbraco 16 now ships with TipTap as the default rich text editor. This change happened because TinyMCE 7 has a license that does not match Umbraco.
Many users find this switch difficult. You might see new HTML tags or struggle to add specific styles. You might miss how TinyMCE worked.
If you are in the middle of a project, you can use the TinyMCE community package for Umbraco 16. Use it to keep your project running. But do not make it a permanent solution. It is not an official product and lacks long-term support.
Instead of forcing TipTap to act like TinyMCE, change your approach.
Stop trying to make the editor do everything. Rich text editors work best when they handle basics like bold text, italics, and links. When you give editors too much freedom, things break.
If you need a button or a callout, do not use raw HTML or CSS classes inside the editor. This is error prone.
Use blocks instead.
- Need a link that looks like a button? Use a Button block.
- Need a pull quote? Use a Quote block.
- Need a code snippet? Use a Code block.
Blocks provide structure. They give editors simple fields to fill out. This keeps your data clean and your frontend predictable.
If your CSS breaks because of how TipTap handles list items, fix your CSS. TipTap uses a strict schema to make editing reliable. This creates more consistent markup than older editors.
A new tool is a chance to improve your system. Moving complex elements into blocks makes your site easier to maintain. It also makes future migrations easy. If Umbraco changes editors again, your content stays safe because your important data lives in blocks, not in editor quirks.
Stop fighting the tool. Work with it.
Source: https://dev.to/luukpeters/tiptap-is-not-broken-your-expectations-are-5h8m