search

liferay / alloy-editor

WYSIWYG editor based on CKEditor with completely rewritten UI
http://alloyeditor.com
GNU Lesser General Public License v3.0
1.4k stars 279 forks source link

Need stronger documentation on configuring editor #842

Open duracell80 opened 6 years ago

duracell80 commented 6 years ago

Documentation is lacking any detailed examples of how to configure alloy editor successfully, both stand-alone and within Liferay. The process also seems overly complex in creating an OSGI module, most front end developers will not have this knowledge and committing two or three people to configuring an editor seems resource prohibitive.

One thing that could help is recipes, or better termed "examples" of adding functionality that is already there like "strikethrough".

jbalsas commented 6 years ago

Hey @duracell80, thanks for the feedback. We don't usually deal with Liferay aspects in this repo. Do you find any particular documentation lacking in the http://alloyeditor.com/ site?

I understand that you're saying that, on Liferay Portal side, https://dev.liferay.com/en/develop/tutorials/-/knowledge_base/7-0/modifying-an-editors-configuration is not clear enough or a good mechanism?

duracell80 commented 6 years ago

From DXP to AE the documentation link 404's and there's no redirect to the 1.5.x API. But following the DXP documentation doesn't often result in success and users may choose to disable AE and go back to CK, if CK offers far more features and a better UX.

duracell80 commented 6 years ago

It's just not a very developer friendly editor in general and users beyond Liferay have the same issues ... http://share.ez.no/forums/ez-platform/how-to-configure-the-available-tools-in-alloyeditor

I must say I'm a suprised that this is so cumbersome when the functionality is already in the Alloy editor. Hopefully eZ will make more features available as default in future releases. Does anyone know about future plans for this?