We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31906
    • 26 Posts
    Hello, I’m using MODx for developing webapages and I really like it. Thanks for it!

    But I need to use some PHP application framework now. I don’t need CMS functionality. Do you think is possible to use MODx as application framework? If yes could you point me in right direction?

    For example I’m looking on Kohana (kohanaphp.com) now but I don’t have so much time to learn something new now.

    Thanks!
      • 22303 MODX Staff
      • 10,725 Posts
      MODx is primarily a framework for developing content-managed sites. You would really be better off using a stand-alone framework for building a non-CMS site, IMO.
        • 31906
        • 26 Posts
        OK. Thanks for answer. That’s what I was thinking... embarrassed
          • 28215
          • 4,149 Posts
          With that said...you can use Revolution to build massive components quite robustly via Custom Manager Pages, xPDO, and the Security system.

          It’s not CodeIgniter, however; it’s main purpose is as a Content Management Framework.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 28042 ☆ A M B ☆
            • 24,524 Posts
            I’m not sure why MODx wouldn’t be useful in any case; even if it’s a web application, it still needs web pages for the forms and various displays. And if you’ve got pages, you can use a management system. And then you don’t have to worry about managing your users, or the organization of your site; you can concentrate on your application. Between plugins, modules for back-end management, and using MODx documents for AJAX processing, I would think using MODx as your core could really speed up your application development.
              Studying MODX in the desert - http://sottwell.com
              Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
              Join the Slack Community - http://modx.org
              • 22303 MODX Staff
              • 10,725 Posts
              I certainly didn’t mean to say it wouldn’t be useful, but just wanted to indicate that using it for such may be overkill, especially for those that don’t want to be constrained by the database connection and other overhead the CMS adds on all requests. Certainly it makes it more convenient and efficient to develop and change things as you go along, though many frameworks that do not add the overhead that MODx does for content-management features include user management, intelligent routing and other things that might make more sense if you don’t need a full-fledged CMS. Just depends on the project TBH; you always have to weigh the benefits of convenience and maintainability against the requirements for functionality and performance as it is always a compromise at some point.