- Issue created by @jurriaanroelofs
- Status changed to Closed: won't fix
2 days ago 9:29am 13 May 2025 - 🇩🇪Germany marcus_johansson
This is done by @juurianroelofs in https://www.drupal.org/project/ckeditor_ai_agent → , so will close.
I'm just posting this to get feedback, my CKEditor API skills at this point are not good enough to create an implementation plan and develop it but I hope more people are excited to collaborate on this and take the CKEditor AI module to the next level.
The current selectbox implementation is useful but it is not the most efficient UI, especially for people who are getting accustomed to more powerful AI writing tools. Using commands in a text editor is already becoming an accepted UI pattern, for example it is used in:
Having slash commands as a secondary interface option that leverages the existing plugin system.
Some example commands:
etc.
1. Create the command, we can see how the CKEditor premium plugin manages this and then develop our own connection to the AI ecosystem.
2. The Drupal integration part is going to be complex, that's not low-hanging fruit and needs more refined user stories and implementation plans.
Addition of command interface to the editor
An additional layer to expose commands that auto-complete. Like typing /link might summon a plugin that autocompletes internal linking commands.
Active
1.0
User interface
This is done by @juurianroelofs in https://www.drupal.org/project/ckeditor_ai_agent → , so will close.