Remove ckeditor_templates_ui from Project page

Bumping to critical to avoid others having to waste time evaluating this and getting lost.

You are talking about a patch wich is not committed yet, postponed until ✨ CKEditor 5 support for Content Templates Needs review

This module now support Ckeditor 5 in the 2.x version, it's now depend on CKEditor 5 Template →

I'm not sure I understand the justification of how this is marked fixed. No docs updates were made, no mention on Project summary page of the fact that the features of this module are being included into the main CKEditor Template module with the work going on in ✨ CKEditor 5 support for Content Templates Needs review .

The owners of the ckeditor_templates → module decided to include the features provided by this module in their module, so this module will not be needed when they fixed the mentioned issue.
At the same time, there is a new module ckeditor5_template → which provides the CKEditor 5 feature, we integrated ckeditor_templates_ui module with ckeditor5_template in a separate branch, and this is mentioned on the module page.

ckeditor_templates_ui maintainer is not interested in flagging this for folks. Therefore, lets take a different approach. I'm reopening and moving this to the ckeditor_templates issue queue as a documentation task to update the project page, and include accurate release notes that indicate that ckeditor_templates_ui should be uninstalled once ✨ CKEditor 5 support for Content Templates Needs review lands. There may even need to be an update hook added to automate uninstall the module as part of #3273358.

Thanks for moving the issue to ckeditor_module, I'm really sad to see that the owners of ckeditor_module decided to take the features that I did on this module and include them in the ckeditor_module without any notice

I could be wrong, but my understanding is that they added the UI because they're updating the architecture to use entities which facilitates admin UI's more or less for free. Also, consolidation and reducing overlap and module soup is – in general – a good thing in the Drupal ecosystem.

It feels kinda forward for a module to uninstall another module. I don't think I have experienced that before. It's especially weird if it occurs without the users knowledge.

But if it was a notice/warning post-install and on the relevant pages and in the docs I think that would suffice no?

Agreed. But your comment might be better served on the other issue ✨ CKEditor 5 support for Content Templates Needs review .

I'm really sad to see that the owners of ckeditor_module decided to take the features that I did on this module and include them in the ckeditor_module without any notice

I don't think this was an active decision by the maintainers - this was just what the person who provided the original patch did.