We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 26826
    • 7 Posts
    I decided to dip my toe into the CMS waters after years of hard coding sites by hand, FrontPage, Dreamweaver, etc. The concept of CMS and CMF was a new and foreign concept.

    I wanted to create an intranet for my firm and developed one by hand by purchasing modules from different vendors for the menus, articles, galleries, file management, etc. I had one fully working only to trash it in the end because of usability issues (each vendor’s plugin created confusion amongst the content authors) and upkeep.

    I tried DotnetNuke, WordPress, Joomla, Mambo and Drupal and didn’t feel like I was in total control of both the front end and back end. Plus, my users would be frustrated in their content authoring and would either abandon their content authoring or ask me to do it.

    And me being a fellow techie, I needed some eye candy in terms of...

    - managing the entire framework
    - setting user roles (down to which user can edit a particular page)
    - extensive and flexible WYSIWYG editor
    - content authoring platform the user could be in both total control and limited control
    - optional content such as galleries, file repository, etc

    So I was looking for not a blogging platform but a website content platform that was both user friendly and powerful on the backend. I ran into www.opensourcecms.com and was amazed as to how many platforms were reviewed.

    I was reading the reviews of another CMS platform and one of the posters mentioned MODx and that little blurb in another CMS’ review is how I discovered MODx.

    MODx is very easy to install and then logging into the Manager gave me some serious eye candy! After a few days of getting used to its interface and resulting output to the browser, I decided that MODx was the platform I would go with.

    So me being a newbie to the CMS/CMF world, I’d like to grade MODx from worst to first...

    F - Frames. Lose the frames in the manager. Full screening the WYSIWYG doesn’t work that great with the frames. But I believe the roadmap says this will be gone soon (I hope).

    D - Templating. There is no ability to import templates as the other CMS’ have. However, I do realize that with the other CMS platforms, the template developers pre-package their templates with the necessary CMS tags and the CMS backend would simply import them. It was then up to the site manager to tweak it from there. Whereas with MODx, you have to start from scratch which is good and bad. Bad if you want to get your current look into MODx quickly. But go from the standpoint that you can take almost any template on the web and with a little patience and understanding of how the MODx template tags, chunks and snippets all work together, you can in fact be in TOTAL control of the resulting output to the browser. You can develop quite a powerful template if you take the time, slow down and learn it. With that said, the current templating process will stop or slow most MODx integrators but the message is not to be discouraged and take your time to learn the templating. This explains why there are not a lot of sites out there offering MODx templates.

    D - Messaging. It’s okay as-is but the sender should have a copy of the message they sent.

    C - User Roles. I’m in the middle of the road on this one. Setting up the user roles is a little confusing (a lot confusing at first) on how to setup access and editing ability. I didn’t realize at first that there was both a manager and web role and that a user can be setup in both. But the beauty of MODx is how granular you can actually setup a user’s editing ability. I think I read MODx’s roadmap that they will simplify this process but to the MODx folks - please don’t lose the granular concept. It is very useful to have pinpoint control on content editing/authoring.

    B - File structure. Simple file structure starting with two root folders: Manager and Assets. Nicely organized which leads to easy tweaking.

    B - TinyMCE File/Image Manager. Wish there was a way to integrate TinyMCE’s commercial plugins for file and image management. A post elsewhere in these forums was correct in that any integrated file/image manager must follow the open source concept. That I agree with. However, it would still be nice to somehow easily integrate Moxiecode’s commercial plugins.

    A - TinyMCE Editor. Wow! Talk about customizing! You can be as pinpoint as you want in specifying which buttons appear in the editor and which row - all within the manager (and not hacking the code). On top of that, you can specify which buttons a particular user can see. User A can have the bold button and User A cannot. Now that’s granular control!

    A - Customized Menuing. Not bad control on the menu aspect. You can specify if a page appears on the drop down menus or not. This is great to highlight an important page within the menus and not have it buried. Add to that is the ability to place a page exactly where you want it within the menu structure. Pretty nice.

    A - Caching. Confusing at first between page and snippet caching to improve performance (to do or not to do) but again, granular control. Nice feature.

    A - Security. Obviously MODx is security conscious and I like the manager and web permissions. This would get an A+ but only if the next version makes it a little less confusing. But to have a strong emphasis on security is a big plus in my book. Very nice.

    A - Tools-Configuration. Wow! Granular control at its best! Too many good things to mention here so lets just say that this entire area in the manager is awesome!

    A+ - Usability. It’s obvious MODx has spent considerable time in seeking a balance in satisfying the power hungry techies as well as empowering the content authors with the tools they need. This goes a long way in my book.

    I’m sure I missed out on other features worth grading but I’ve only been using MODx for a few days. So IMHO, MODx is a great CMS/CMF out of the box. It does lack some features as other posts in this forum point out but so far, MODx is pretty good as-is.

    All in all, I’m glad I came across MODx and look foward to its future. They deserve their Most Promising CMS of 2007 award. Now lets work on CMS of the Year award!
      • 7231
      • 4,205 Posts
      Very interesting analysis, I appreciate that you took the time and effort to let us know your impressions. I can see that you are on your way to being a modx geek (in the good way). I agree with your impressions overall, and in general the next releases will address the issues that got low grades.

      One thing that you did not grade and yet plays a major role in any successful open source project...The Community (which I grade at A+) grin This is the only place I have ever been where you can get direct help from a very enthusiastic (and humble) team of developers including the founding members. As a minor team member myself I am in awe of the atmosphere of actually wanting to help no matter how trivial or obscure the requests may be.

      Welcome aboard grin
        [font=Verdana]Shane Sponagle | [wiki] Snippet Call Anatomy | MODx Developer Blog | [nettuts] Working With a Content Management Framework: MODx

        Something is happening here, but you don't know what it is.
        Do you, Mr. Jones? - [bob dylan]
        • 25663 MODX Staff
        • 12,272 Posts
        F - Frames. Lose the frames in the manager. Full screening the WYSIWYG doesn’t work that great with the frames. But I believe the roadmap says this will be gone soon (I hope).
        Gone in 097. Public preview soon!

        D - Templating. There is no ability to import templates as the other CMS’ have. However, I do realize that with the other CMS platforms, the template developers pre-package their templates with the necessary CMS tags and the CMS backend would simply import them. It was then up to the site manager to tweak it from there...
        097 introduces transport packages which are a way to bundle anything you need and adds the ability to automatically put it all into place. If your server supports it, you can even install templates remotely.

        D - Messaging. It’s okay as-is but the sender should have a copy of the message they sent.
        This needs massive attention and probably shouldn’t even be part of the core install. I’ve never used this once in fact!

        C - User Roles. I’m in the middle of the road on this one. Setting up the user roles is a little confusing (a lot confusing at first) on how to setup access and editing ability. I didn’t realize at first that there was both a manager and web role and that a user can be setup in both. But the beauty of MODx is how granular you can actually setup a user’s editing ability. I think I read MODx’s roadmap that they will simplify this process but to the MODx folks - please don’t lose the granular concept. It is very useful to have pinpoint control on content editing/authoring.
        Again, 097 massively improves the permissions system and streamlines the users into a single user system. You can control what they access by creating "contexts", the manager being one and anonymous web surfers being another.

        B - File structure. Simple file structure starting with two root folders: Manager and Assets. Nicely organized which leads to easy tweaking.
        In 097 you get the core and that’s the only thing that’s required. You make everything else as simple or complex as you like. You can even install the Core outside of webroot and run multiple sites off a single "install".

        B - TinyMCE File/Image Manager. Wish there was a way to integrate TinyMCE’s commercial plugins for file and image management. A post elsewhere in these forums was correct in that any integrated file/image manager must follow the open source concept. That I agree with. However, it would still be nice to somehow easily integrate Moxiecode’s commercial plugins.
        Now this one I’m not so sure about, but I bet it’s straightforward.

          Ryan Thrash, MODX Co-Founder
          Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
          • 28215
          • 4,149 Posts
          Great perspective and review. Thanks.

          A few follow-up comments:

          Quote from: SFGolfer at Mar 20, 2008, 11:56 AM

          F - Frames. Lose the frames in the manager. Full screening the WYSIWYG doesn’t work that great with the frames. But I believe the roadmap says this will be gone soon (I hope).
          097 moves to an iframe, contrary to what rthrash says. There are plans in the works for future versions that will get rid of frames entirely.


          D - Messaging. It’s okay as-is but the sender should have a copy of the message they sent.
          I agree. I think the messaging system is awful.


          C - User Roles. I’m in the middle of the road on this one. Setting up the user roles is a little confusing (a lot confusing at first) on how to setup access and editing ability. I didn’t realize at first that there was both a manager and web role and that a user can be setup in both. But the beauty of MODx is how granular you can actually setup a user’s editing ability. I think I read MODx’s roadmap that they will simplify this process but to the MODx folks - please don’t lose the granular concept. It is very useful to have pinpoint control on content editing/authoring.
          097 will be using ABAC-style ACLs, which allow incredible depth and granularity into whatever you want to prevent or allow.


          B - File structure. Simple file structure starting with two root folders: Manager and Assets. Nicely organized which leads to easy tweaking.
          097 implements packaging, so basically you wont have to worry about ever touching the filesystem again.


          B - TinyMCE File/Image Manager. Wish there was a way to integrate TinyMCE’s commercial plugins for file and image management. A post elsewhere in these forums was correct in that any integrated file/image manager must follow the open source concept. That I agree with. However, it would still be nice to somehow easily integrate Moxiecode’s commercial plugins.
          MODx is by principle against implementing anything non-GPL or non-open source into the core. Someone could develop a plugin, if they like, though.


          A - Customized Menuing. Not bad control on the menu aspect. You can specify if a page appears on the drop down menus or not. This is great to highlight an important page within the menus and not have it buried. Add to that is the ability to place a page exactly where you want it within the menu structure. Pretty nice.

          This is vastly improved in 097 - the document tree is now a drag/drop tree, so you can drag resources (formerly called documents) all around to re-order them or move them into different folders. No more ’changing the parent’. Now it’s all intuitive WYSIWYG.


          A - Caching. Confusing at first between page and snippet caching to improve performance (to do or not to do) but again, granular control. Nice feature.
          Caching is a ton better in 097 - resource-specific, context-driven, and sped way, way up.

          A+ - Usability. It’s obvious MODx has spent considerable time in seeking a balance in satisfying the power hungry techies as well as empowering the content authors with the tools they need. This goes a long way in my book.
          Just wait till 097. I don’t think I’ve seen a CMS with nearly as much usability as the current manager.


          All in all, I’m glad I came across MODx and look foward to its future. They deserve their Most Promising CMS of 2007 award. Now lets work on CMS of the Year award!

          Thanks for the comments, and we really are thankful for the award - and especially for this community. They make MODx what it is.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 26826
            • 7 Posts
            Thanks for the replies. Nice to know that the core will be upgraded soon.

            But 097? It sounds like there’s enough improvements to go to ... 1.0? Or do you have something special in mind for the threshold 1.0? wink
              • 25663 MODX Staff
              • 12,272 Posts
              Nothing to see here ... carry on!
                Ryan Thrash, MODX Co-Founder
                Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                • 6726
                • 7,075 Posts
                Quote from: rthrash at Mar 20, 2008, 04:07 PM
                Nothing to see here ... carry on!

                lol

                Quote from: SFGolfer at Mar 20, 2008, 04:03 PM
                But 097? It sounds like there’s enough improvements to go to ... 1.0? Or do you have something special in mind for the threshold 1.0? wink

                Well that last comment was right on target, rev numbering is always something which raises a hell lot of discussions among the team or the community. You’re not entirely wrong here, it’s not a small step from 0.9.6.x to 0.9.7, more like a revolution in progress tongue

                MODx is known for its conservative numbering, and the basis of this is probably tied to the Etomite legacy which is still present. I guess 1.0 will mark a stepstone severing all ties to the old codebase. To me, since 0.9.2 we have a very stable release and 0.9.6 was really a maturity release for the "soon to be history" branch.

                But back on subject : I’ll add my thoughts to the reactions here... I’ll join in and say that the input is very interresting and appreciated ! A fresh sharp look at MODx, just what we need now and then to keep perspective smiley

                This being said, the major disagreement I’ll have with what you wrote is a D for templating.

                I would rate it at least an A and A+ with PHx installed (conditionnal logic and extended parser capability is really key and if I am not mistaken, will make it in the new branch’s parser). Keep in mind I am only speaking of templating the frontend pages, not the backend (templating the backend will become way easier with the new manager -> Current backend templating would be an E for me).

                Templating is one of the key items why I love MODx over the 1-click install systems out there : it’s as flexible as it can be, there is nothing you can’t do with MODx in that area ! The fact that snippets use chunk as templates (what I call micro-templates) to format the output and placeholders to control what data goes where... goes way beyond most systems can do (Textpattern, EE and CMS Made Simple use a similar logic... but they don’t have TVs tongue ).

                Now, about importing templates : it’s not entirely true that it’s not possible to import template in a quick and easy way, provided they comply with a few guidelines to work with MODx Resources Wizard.

                Frankly I have NEVER imported a template, but then again my goal is building custom websites starting from scratch, as many webdesigners who produce website for clients.
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l'outil id