#ckeditor5 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #ckeditor5, aggregated by home.social.
-
Neuer Artikel im Blog:
TYPO3 v14: Rich Text Editor im Form Framework. Schluss mit Workarounds bei Checkbox-Labels
-
Neuer Artikel im Blog:
TYPO3 v14: Rich Text Editor im Form Framework. Schluss mit Workarounds bei Checkbox-Labels
-
Neuer Artikel im Blog:
TYPO3 v14: Rich Text Editor im Form Framework. Schluss mit Workarounds bei Checkbox-Labels
-
Neuer Artikel im Blog:
TYPO3 v14: Rich Text Editor im Form Framework. Schluss mit Workarounds bei Checkbox-Labels
-
Neuer Artikel im Blog:
TYPO3 v14: Rich Text Editor im Form Framework. Schluss mit Workarounds bei Checkbox-Labels
-
-
-
-
-
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Researching and testing moving @gamingonlinux.com from #CKEditor4 to #CKEditor5 and omg so complicated, everything is different. Having to totally rewrite the few custom bits we have, going to take a while <_<
-
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Please vote for this #CKEditor5 feature: https://github.com/ckeditor/ckeditor5/issues/14206
As for upgrading #TYPO3 instances to #v12, this is really necessary to keep the previous behaviour of #CKEditor4 that only one #style can be assigned to an element instead of multiple. #CKEditor -
Last week I finished up a first beta release of https://www.drupal.org/project/ckeditor5_markdown_editor which integrates the markdown output plugin (https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html).
When you have installed and enabled the module, you now can set a checkbox to enable the CKEditor5 instance to format the content to Markdown instead of HTML. -
Last week I finished up a first beta release of https://www.drupal.org/project/ckeditor5_markdown_editor which integrates the markdown output plugin (https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html).
When you have installed and enabled the module, you now can set a checkbox to enable the CKEditor5 instance to format the content to Markdown instead of HTML. -
Last week I finished up a first beta release of https://www.drupal.org/project/ckeditor5_markdown_editor which integrates the markdown output plugin (https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html).
When you have installed and enabled the module, you now can set a checkbox to enable the CKEditor5 instance to format the content to Markdown instead of HTML. -
Last week I finished up a first beta release of https://www.drupal.org/project/ckeditor5_markdown_editor which integrates the markdown output plugin (https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html).
When you have installed and enabled the module, you now can set a checkbox to enable the CKEditor5 instance to format the content to Markdown instead of HTML. -
Last week I finished up a first beta release of https://www.drupal.org/project/ckeditor5_markdown_editor which integrates the markdown output plugin (https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html).
When you have installed and enabled the module, you now can set a checkbox to enable the CKEditor5 instance to format the content to Markdown instead of HTML. -
Will #Drupal's #CKEditor5 config really not let you allow an html tag in the source without also enabling it as an explicit wysiwyg button?
Just because I want to allow some knowledgeable users to add code blocks doesn't mean I want all the users to see it as an option.
-
Will #Drupal's #CKEditor5 config really not let you allow an html tag in the source without also enabling it as an explicit wysiwyg button?
Just because I want to allow some knowledgeable users to add code blocks doesn't mean I want all the users to see it as an option.
-
Will #Drupal's #CKEditor5 config really not let you allow an html tag in the source without also enabling it as an explicit wysiwyg button?
Just because I want to allow some knowledgeable users to add code blocks doesn't mean I want all the users to see it as an option.
-
Will #Drupal's #CKEditor5 config really not let you allow an html tag in the source without also enabling it as an explicit wysiwyg button?
Just because I want to allow some knowledgeable users to add code blocks doesn't mean I want all the users to see it as an option.
-
Will #Drupal's #CKEditor5 config really not let you allow an html tag in the source without also enabling it as an explicit wysiwyg button?
Just because I want to allow some knowledgeable users to add code blocks doesn't mean I want all the users to see it as an option.
-
Bon j'ai fait la montée de version de mon site en #drupal 10, mais j'ai perdu la mise en forme de mes extraits de code. Vous avez un truc efficace qui s'intègre bien avec #drupal et #ckeditor5 ?
-
Bon j'ai fait la montée de version de mon site en #drupal 10, mais j'ai perdu la mise en forme de mes extraits de code. Vous avez un truc efficace qui s'intègre bien avec #drupal et #ckeditor5 ?
-
Bon j'ai fait la montée de version de mon site en #drupal 10, mais j'ai perdu la mise en forme de mes extraits de code. Vous avez un truc efficace qui s'intègre bien avec #drupal et #ckeditor5 ?
-
Thanks to some help of @wimleers on Slack (and looking into the contrib ckeditor_media_embed) I managed to load the Markdown output plugin (markdown-gfm) with CKEditor5. With this plugin the output is saved as Markdown instead of HTML.
I made a contrib and pushed the first dev release to: https://www.drupal.org/project/ckeditor5_markdown_editor
-
Thanks to some help of @wimleers on Slack (and looking into the contrib ckeditor_media_embed) I managed to load the Markdown output plugin (markdown-gfm) with CKEditor5. With this plugin the output is saved as Markdown instead of HTML.
I made a contrib and pushed the first dev release to: https://www.drupal.org/project/ckeditor5_markdown_editor
-
Thanks to some help of @wimleers on Slack (and looking into the contrib ckeditor_media_embed) I managed to load the Markdown output plugin (markdown-gfm) with CKEditor5. With this plugin the output is saved as Markdown instead of HTML.
I made a contrib and pushed the first dev release to: https://www.drupal.org/project/ckeditor5_markdown_editor
-
Thanks to some help of @wimleers on Slack (and looking into the contrib ckeditor_media_embed) I managed to load the Markdown output plugin (markdown-gfm) with CKEditor5. With this plugin the output is saved as Markdown instead of HTML.
I made a contrib and pushed the first dev release to: https://www.drupal.org/project/ckeditor5_markdown_editor
-
Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.
Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢
Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.
-
Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.
Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢
Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.
-
Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.
Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢
Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.
-
Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.
Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢
Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.
-
Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.
Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢
Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has its own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.
I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has it's own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.
-
Did you know you can add more attributes to embedded media in Drupal *and* get a nice UI for it in #CKEditor5 … with writing ZERO lines of JavaScript?
See @harumijang's article: https://dev.acquia.com/blog/drupalelementstyle-add-styles-drupal-media-ckeditor-5-using-only-configuration
-
Did you know you can add more attributes to embedded media in Drupal *and* get a nice UI for it in #CKEditor5 … with writing ZERO lines of JavaScript?
See @harumijang's article: https://dev.acquia.com/blog/drupalelementstyle-add-styles-drupal-media-ckeditor-5-using-only-configuration
-
Did you know you can add more attributes to embedded media in Drupal *and* get a nice UI for it in #CKEditor5 … with writing ZERO lines of JavaScript?
See @harumijang's article: https://dev.acquia.com/blog/drupalelementstyle-add-styles-drupal-media-ckeditor-5-using-only-configuration
-
Did you know you can add more attributes to embedded media in Drupal *and* get a nice UI for it in #CKEditor5 … with writing ZERO lines of JavaScript?
See @harumijang's article: https://dev.acquia.com/blog/drupalelementstyle-add-styles-drupal-media-ckeditor-5-using-only-configuration
-
Did you know you can add more attributes to embedded media in Drupal *and* get a nice UI for it in #CKEditor5 … with writing ZERO lines of JavaScript?
See @harumijang's article: https://dev.acquia.com/blog/drupalelementstyle-add-styles-drupal-media-ckeditor-5-using-only-configuration