Discover the MODX3 project updates

The MODX Meetup in Amsterdam is approaching quickly, with around 150 people attending. MODX3 will also be a hot topic during the event. A preview!

We're thrilled to release our first build of MODX3. This build represents months of work from the MODX3 team, the community, and all the generous sponsors. Read the full project statement now!

Nearly everything for MODX 2.7 is merged and we're getting to a final build. We're working on the last pull request for the MODX3 design. That will be the first (finished) version of the design, which is then ready for testing.

MODX 2.6.4 was released last week! The integrators are making an amazing effort on 2.7! at the moment and we're on schedule to have 2.7 ready in about 2 weeks. We have new Setup-designs, which could use your feedback.

This week was a MODX Meetup week, where a status report was shared about MODX3. We're sharing the slides of all the progress we made during the project.

This week, we got together with the MODX Integrators team to talk about our current progress and what to do with the 2.6 branch and the 2.7 branch.

Testing is progressing slowly, so we need your help!

We need photos for our new login screen. Four photos to be precise: winter, spring, summer en autumn. For this, we are doing a MODX3 Photo Contest!

We finished the Template Picker this week. As most of the development work is ready, we spend this week on acquiring testing and merging resources. We've found people who want to spend time on testing and merging: Ivan Klimchuk, John Peca (MODX) and Garry Nutting (MODX). This will all be coordinated by Jason Coward, as usual. 

We've got one thing to mention for this week: huge refactoring of the MODX core to make it more modern. Vasily changed 2077 files and added PSR-4 autoloading, xPDO 3 models, refactored processors. This means no screenshots this week, but a lot of under-the-hood work!

May has started and we're nearing the endgame of the MODX3 Project. We see less drastic changes, but nevertheless important changes. MODX Community Slack discussions have given us some very valuable input for UX improvements this week. We're continuing work on this.

Where we need help right now: help us test the codebase and help fund the project (we're still not there yet)!

The MODX UI redesign is really shaping up! Rinze made new designs for the manager UI in week 9. Vasily did a great job at implementing those this week. It is not finished yet, but we're getting close! Check screenshots and videos of the UI work!

Development has started on the resource editing screen and the first prototype is ready. The template preview also is in the prototype stage, which is amazing news for content managers. Please check the screencasts we recorded to show the changes.

Refactoring, testing, testing, finishing up designs, bug fixing, 2.6.3, 2.7, a lot is going on. Vasily did a full refactor of the current browser processors and he implemented Markdown support for extras! Besides we built a failsafe feature for overwriting elements.

The design front has been busy researching how to optimize resources, the tree and the uberbar. We're sharing Rinze's prototypes in this post.

One of the primary goals of MODX3 is optimizing the UX. Vasily did an amazing job at increasing the UX, specifically the time required to upload images. Every upload action now takes 4 fewer clicks than you are used to! We did a lot of testing and polishing on existing MODX3 features, but we need more testers! Therefore we made a screencast for this, to make it easier to understand.

Week 7 was an exciting week for MODX3. Vasily finished the new Dashboard architecture. It needs testers now, lots of them! The MODX3 team got a new member and we're working on finishing up the MODX Template Preview feature. MODX 2.6.2 will be released soon and last but not least: the modx.org project is progressing!

Work started on implementing the new dashboard in MODX. While doing so, we also took a shot at upgrading ExtJs for some extra abilities and new features, but the effort would have too much an impact on our June release date. The login screen was finished with the last pull request on Github.

Week 5 is the week after the official project-launch at the MODX Meetup in Leeuwarden. We've got several amazing sponsorships going and receive a good amount of donations. More is better though! As for project progress: we finished the login screen, updated plan-page on the website and we did more media source fixes. All of these changes require more testers and people who can translate new lexicon strings. Last but not least: dashboard development has begun!

This week finished the first month of the project. MODX3.org is live now and you can now support our cause! Work continued on the media sources with Flysystem integration. Adapters were implemented: local filesystem, FTP, SFTP, Amazon S3 and Swift. Jason Coward brought up the idea to use Github Projects for increased project transparency, which will happen in week 5. Design work also started on the create resource-page. The MODX Meetup in Leeuwarden also was organized with over 40 attendees!

The third week of the project! Rinze made a lot of progress on the new MODX dashboard. It's such an improvement, you will love it! More work has been done by Vasily on adapters: AWS S3, Swift, local file system, FTP, and SFTP are being worked on. Besides that, we did a lot of work on refactoring the media browser and improving the tree.

The second week of our MODX3 project featured continuous work on the login window, improved HTML emails from the manager and a new forgot-password flow, compliant with the new EU regulations. A long-time request has been implemented: manager customization for both create and update actions! Last but not least: MODX is now installable through composer and an install script.

Week 7 of 2018 was the first week of the MODX3 project. GP, Vasily and Rinze continued started off with the login window, while Mark and Jason some serious cleaning up on the 3.x branch on Github. Vasily also did some amazing work on using composer to load third-party components.