Now that 1.9 has been released, I think we need to step back from new features and start consolidating the developer experience. We have a *lot* of duplication in this project:
I know some of this is due to BC, but a lot of this can and should be fixed. I think the biggest offenders are the documentation and JS.
For docs, we don't have much of an excuse to have two of them still, other than we haven't had the time to migrate the old one. It's arguable that we shouldn't have launched the RTD version (even though it's an improvement) if we didn't have a time to properly migrate the existing docs.
For JS, I understand we needed to keep our Elgg JS object in 1.9 for BC, but we should have updated our JS to be AMD compatible. It's confusing for new devs to see us recommend using AMD but that not be reflected in our own code.
I know we're all interested in forward momentum toward 2.0, but we've been putting some of these off for so long that first impressions of Elgg to new devs are not what I think we would all want them to be.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
#Following this topic..
I agree on the need for consistency of all core plugins. So I hope that after the example plugin is made all other core plugins are made equally which will serve both users as well as developer experience.
- Previous
- 1
- 2
- 3
- 4
- Next
You must log in to post replies.