-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation on v2? #1400
Comments
Thanks for the question @akjackson1. It's true that not much has been happening in AlloyEditor of late. I don't think there are any plans to archive it as such. We continue to merge bug fixes when they are made (either via contributions by external contributors, or fixes that we prepare internally in response to customer support tickets), but it's not something we're actively pushing on. Having said that, the main place that Liferay itself uses AlloyEditor is inside Liferay DXP, where it is just one of several rich text editors that one can make use of. Given that one of the other integrations is CKEditor, and AlloyEditor itself is just a wrapper around CKEditor, we have lately found ourselves tending to concentrate more and more on improving the base CKEditor integration, as it seems to be a more impactful thing for us to do. This is why there is nobody presently working on adding new features to AlloyEditor, or filling in the gaps in the documentation that you have highlighted. I can't predict what things will look like 3, 6 or 12 months from now, but that's the current situation. I'll leave it to others to comment on your questions about similar editors as there are quite a few good ones out there if you didn't want to continue with AlloyEditor. |
Thanks for the quick response @wincent and for the transparency. I look forward to seeing if others have any suggestions so we can determine what the best choice is moving forward. |
Hey @akjackson1, thanks for reaching out and for using AlloyEditor. We're glad it's served you well so far! As @wincent said, we're slowly leaning towards a simpler integration directly on top of CKEditor. In the time since we released AlloyEditor, CKEditor has caught up in many of its missing features at the time. One example is the Ballon Toolbar support that comes already out of the box. That's what we're thinking to leverage in the future.
Our own product that uses AlloyEditor is very long lived, so AlloyEditor is likely to be at least minimally maintained for several years. I wouldn't count on new developments or improvements, though.
That's entirely up to you, of course! Something I wanted to do before we stepped out was to see if we could find other maintainers to pick up the project. If you or others are interested, we could figure out the options and how to properly do such a thing... 🤔
Please, don't take this as endorsements, but some similar editors might be: |
We've been using Alloy Editor for quite a while in version 1 where we have quite a few modifications. It's worked very well for us and we've greatly appreciated the work many developers have put into this wonderful editor. Though now v1 no longer seems to be building due to numerous deprecation errors, and we decided to update to v2 but noticed the documentation doesn't seem to be updated. For example: https://alloyeditor.com/docs/develop/create_buttons.html. Is there documentation anywhere for v2?
Additionally, it seems like alloy isn't seeing a lot of activity recently, is the project likely to be archived soon? Should we start looking for an alternative? If so, are there any recommendations on similar editors out there?
The text was updated successfully, but these errors were encountered: