We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 40447
    • 165 Posts
    Funny that no one mentions the page fields in the admin of processwire. Developers keep themselves busy with the php tags in the template files in processwire. Clients never go there. Clients update their webpages by simply editing fields in the admin. It's been made part of the api. Processwire has been made scalable from the beginning so you can use it for big projects. And aestethicly appealing interfaces has very little to do with the cms you are using, but with html, css, photoshop, etc. typical designers work. [ed. note: sitecms last edited this post 13 years, 6 months ago.]
      • 42967
      • 143 Posts
      Processwire appeals to me purely for the speed, front end and backend speed looks really good. But the manager interface really does not work for me, I can't imagine our clients getting on with it.
        Eighth day design
        Design agency with offices in Edinburgh and Brighton
        • 25511
        • 13 Posts
        Quote from: Bruno17 at Mar 13, 2013, 12:33 AM
        when you, as a 'backend'-developer, work together with 'frontend' - developers and designers, its a must to have separated logical- and the layout-stuff.
        This is one of the great advantages of MODX with its templates/chunks/placeholders and its parsing-system.
        processwire seems to have only plain php - templates, which for sure is simple and may make things fast, but can make it very frustrating, when your frontend - developers have to bother with php-tags in between their html tags and may ruin your development-work.
        It would never came to my mind to change Revo (or Evo) with something like processwire for bigger projects, and when working together with more than one people on it at the same time, so far I can tell about it. (had just the time for a quick lookup into it, some time ago)

        You can put all your logical php code in a seperate file(s) and just call functions in templates. This way you can keep your templates clean for frontend developers - if that's what you want.

        We never actually moved to Revo with our customer projects for mainly because of three reasons: 1) It's too complicated. 2) It's too slow. 3) It needs too much from server. Evo doesn't have these issues and that's why it's been our wheapon for most of the projects.

        When speaking about large projects I woul'd definetly choose PW over MODX any time. Admin area is VERY easy to customise between different users and PW has no problems with handling thousands and thousands of pages. MODX document tree is terrible when you have large amount of documents under one folder. PW has built in pagination inside document tree that helps alot. Plus it's also very easy to build your own admin pages like this one: http://modules.processwire.com/modules/data-table/

        I was hoping that MODX 3 would be the next step for us but it looks like 3 isn't gonna be here for some time. I surely hope that it would be released soon and will rock our world like Evo did back in 2008. Now PW did the same some time ago and it's no looking back.
          • 28042 ☆ A M B ☆
          • 24,524 Posts
          I've heard much the same thing from a few people that I worked with over the years as they came to prefer Concrete 5 and various other CMS applications. As they say, whatever floats your boat wink

          I don't have the time or energy any more to learn something radically different. Yes, Revo core is a lot different than Evo core, but it's really still doing essentially the same thing, so it's more a matter of how it's doing it rather than having to start all over with learning what it's doing.

          Besides the actual technology, I've been comfortable with the community for too many years to be dissuaded from going along with it for very long. Get right down to it, the technology doesn't matter all that much. They all get the job done and need to be learned (by both developers and editor users), from phpNuke to WordPress, so to me my "comfort" is the deciding factor.
            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
            • 37099
            • 338 Posts
            Just been looking at process wire and it does look very appealing, for a few of reasons.


            • Speed.
            • The client interface looks really user friendly. For example, in the intro video (http://processwire.com/videos/ ) at around 5:00 it looks really easy for a client to make a link to another page from the text editor. And then just after that he adds an image and resizes it in the editor and says it's being re-sampled from the original image. I think clients would love that! I don't know if that is a feature of process wire or some plugin for a rich text editor that I don't know about.

            • The "jQuery like" API looks intuitive.


            I'm going to give it further investigation .....
              • 40447
              • 165 Posts
              Get right down to it, the technology doesn't matter all that much. They all get the job done
              Yes, but, they all get the job done very different in performance and interfacing with clients, designers, developers, and coders.
              I've been comfortable with the community for too many years
              Yes, I learned a lot from the modx community because of many experienced modx'ers who always want to help you to upgrade your skills, like you Susan.
              I think modx 3 is going to change the cms game again. By the way, does anyone know any news lately about modx 3 development ? [ed. note: sitecms last edited this post 13 years, 6 months ago.]