[Docs] Document how to customize TipTap extensions

[febsn]

I am trying to customize the extensions included in the TipTap instance (specifically, I'd like to remove tables and add lists). The readme lists some configuration options for tiptap (textColors, tableClasses,…), but doesn't state how to configure TipTap extensions. How can I accomplish this? I'll still try to figure out but would be happy if someone could give me a hint. I'd offer to add it to the readme later.

[fsbraun]

@febsn Extensions are compiled into the TipTap editor. But maybe you only want to remove items from the toolbar? This is easily done by adding to the editor configuration, e.g.:

DEFAULT_EDITOR.configuration["toolbar_CMS"] = [
    ["Undo", "Redo"],
    [
        "Bold",
        "Italic",
        "Underline",
    ]
]
DEFAULT_EDITOR.configuration["toolbar_HTMLField"] = [...]

You can get your inspiration from the default settings found for both toolbars in the file editors.py.

Hope this helps! It would be great, if you could add an explanation.

PS:
The difference between disabling the config and just removing it from the toolbar is that the user still can paste a table, for example.

[Grosskopf]

Extensions are compiled into the TipTap editor

So that means adding extensions like the details extension would need to happen in djangocms_text, right?

[fsbraun]

Currently, yes. I've been playing around with dynamic extensions that can be added by separate packages, say, inlining YT videos - let's see if I come up with a simple api. - Also in the context of this discussion or the CodeBlockLowlight extension, removing extensions might also be desirable.

Details might be a use case for the default, though. Interesting thought!

[febsn]

Thank you. Changing the configuration works as expected, I was rather hoping to add new extensions as @Grosskopf mentioned. For the moment I'm good with how it is – thank you so much for your effort, I appreciate it!

To add or remove extensions, irrespective of the concrete example, maybe it would also be a feasible way to allow for dropping in a self-compiled version of the editor instead of the shipped one?

[fsbraun]

@febsn You can do that any time. Just build it from the private directories. There's already some customization included (cms plugins, link, table, ...)

[febsn]

Great, I'll look into that, and maybe document it if I succeed. Thanks.

[petrklus]

Currently, yes. I've been playing around with dynamic extensions that can be added by separate packages, say, inlining YT videos - let's see if I come up with a simple api. - Also in the context of this discussion or the CodeBlockLowlight extension, removing extensions might also be desirable.

Details might be a use case for the default, though. Interesting thought!

+1 on the extension removal - would be great to make sure that only what we configure in the toolbar is what is allowed to be pasted in, for example