16 Responses

  1. Jason Pelker
    Jason Pelker August 8, 2013 at 19:57 | | Reply

    This is an accurate review. I found my experiences to be very similar.

    It took a few hours to become comfortable with the system, but once I did, I had no doubt I could create almost any marketing page I could imagine. In fact, I’d love to see DMS functionality one day built into WordPress. It would significantly improve the content creation system offered today.

    Besides that, I’d like to see the tool’s usability improved slightly, but that’s to be expected with a 0.9.6 release.

    I recommend trying DMS.

    1. Joe
      Joe October 5, 2013 at 15:35 | | Reply

      Yes, I’d also definitely recommend trying DMS if you are at all interested in using a tool to build WP pages, themes or layouts.

  2. James Giroux
    James Giroux September 17, 2013 at 05:28 | | Reply

    Joe! I just found this page. Great article. I’ve been using PageLines for a while now and have built a number of sites on it. It’s been great and the community of developers and enthusiasts around the product is awesome too.

    1. Joe
      Joe October 5, 2013 at 15:33 | | Reply

      James, glad you’ve enjoyed using PageLines. Would you say the product has improved since its launch?

  3. Oliver Nielsen
    Oliver Nielsen October 22, 2013 at 15:13 | | Reply

    When DMS was released I was skeptical. And I still think it has some way to go, before I feel 100% using it, but I think PageLines DMS is an interesting product, that gets better and better very quickly.

    The idea to standardize a lot of the layout mechanisms, and integrate Bootstrap, parallax effects, viewport animation, and more; is quite empowering.

    Good review Joe!


    1. Joe Fylan
      Joe Fylan October 22, 2013 at 16:18 | | Reply

      Thanks Oliver, I keep meaning to find the time to go back and see how it is developing.

  4. Nick Haskins
    Nick Haskins October 30, 2013 at 14:00 | | Reply

    For the consumer, DMS is amazing.

    As a developer, I would stay FAR away from PageLines DMS. I’ve been building on this platform for nearly two years, and am slowly moving away.

    1. Jean Galea
      Jean Galea October 30, 2013 at 14:54 | | Reply

      I would say something like Genesis is more developer-oriented.

      1. Nick Haskins
        Nick Haskins October 30, 2013 at 14:59 | | Reply

        To be honest I’m quite apprehensive about using frameworks, period (wordpess frameworks that is). I’m to the point where writing out from scratch, and on-boarding BS3 takes less time and is far easier than fighting with a framework, or overriding css, or unnecessary code running, unused scripts, et cetera, et cetera.

    2. Oliver Nielsen
      Oliver Nielsen October 30, 2013 at 18:07 | | Reply


      I (and many others I believe) tend to think of Nick Haskins as mr. PageLines;)

      I agree with your other comment that frameworks can sometimes be more of a hassle than helpful. Compatibility issues, new updates breaking stuff, etc, can all be very bothersome.

      And the page load speed gets slower the fancier the framework is. PageLines DMS f.e. comes with quite a handful JavaScripts. It would be super nice if all these could have been combined into one file, loading in the proper order. I have trouble getting DMS to work when using CloudFlare’s rocket loader (an asynchronous JS loader).

      I still have some clients running WordPress themes I wrote from scratch, 100% tailor-made to them. I’m amazed that I haven’t had to update a single line of code, for 3+ years, to ensure compatibility with WordPress or plugin updates.

      And the speed of those custom-coded themes? No framework, even the fastest ones, like Genesis, can compare. Reason? There’s zero superfluous code, no theme options, etc.

      But please let me know more about what you find most cumbersome about PageLines DMS, Nick. I’m curious, as I think they have a nice product. Just isn’t perfect. I struggle choosing DMS for client sites. Difficult to put my finger on why.


      1. Nick Haskins
        Nick Haskins October 30, 2013 at 18:11 | | Reply

        “I still have some clients running WordPress themes I wrote from scratch, 100% tailor-made to them. I’m amazed that I haven’t had to update a single line of code, for 3+ years, to ensure compatibility with WordPress or plugin updates.”

        you hit the nail on the head, and summed up why in 3 lines. They are not developer friendly. Consumer friendly? Absolutely. For the average user it’s awesome.

        What’s cumbersome?

        Old Site – First View – 5.214s
        Old Site – Repeat View – 2.010s

        New Site – First view – 1.625s
        New Site – Repeat view – 0.740s


        Again, DMS is a great tool for the average user and developers who prefer not to write code. I personally enjoy it, and I enjoy even more when 100% of my code is being used.

        1. Nick Haskins
          Nick Haskins October 30, 2013 at 18:12 | | Reply

          personally enjoy writing code from scratch, that is. just to clarify.

        2. olivernielsen
          olivernielsen October 31, 2013 at 23:32 | | Reply


          “14K less lines of CSS, 50% less markup, and 14 less js files” … That says it all really;)

          1. Nick Haskins
            Nick Haskins November 1, 2013 at 13:51 | | Reply

            ya i understand its a framework, but that’s excessive, especially when 90% of it isnt even being used. I’ve been on those guys for years to NOT load the sections LESS files when not in use. Still, they load. That’s 30+ LESS files getting compiled using server resources when it doesnt have to be like that. It’s the same thing with all the js files. Parallax, fitvids, easing, waypoints, animations, etc, should ONLY Be loaded on demand. ONLY if the user checks the option. But it’s not the cause unfortunately, the framework loads 14 js files just to be a framework.

            I personally want 100% of my code being utilized. Anything else is just kruft and slows things down, as those stats show.

            1. Oliver Nielsen
              Oliver Nielsen November 1, 2013 at 14:44 | | Reply

              I agree! Been thinking similarly. On a side note, the situation is the same with WooCommerce. The moment one activates WooCommerce on a site, it gets *significantly* slower. Each and every page. Even pages not related to the shop, with no WooCommerce related widgets or anything. All the JS loads, on all pages. Insanely needless.

              Btw, I like your goal of utilizing 100% of the code. Never thought of it that way, but absolutely a great ideal to strive for.

            2. Oliver Nielsen
              Oliver Nielsen November 1, 2013 at 14:55 | | Reply

              Oh, by the way, what’s needed, in my opinion, is a radically different kind of framework to be made. One more akin to Ruby on Rails – but focused on templating and 100% designer-friendly.

              Thesis 2.1 sports some of that thinking, but it’s way to technical and convoluted (UI and UX-wise).

              There’s also a need for a common, standardized codec for specifying f.e. colors. By that I mean: how cool it would be, if there was a standard color palette-format, like .ASE is to Adobe apps, akin to .less, but more semantic. That way, anyone could create a color palette on Kuler, ColourLovers etc, save it in this special, standardized file format, and have the intended colors applied as expected.

              So, instead of @color1, @color2, etc, it would be: @accentcolor, @light-backgroundcolor, @dark-backgroundcolor, etc.

              Then themes and frameworks could support it. Import color-file, boom! your website’s is colored.

              The above is just draft thoughts, not fully throught through, but I do think, overall, that web design in general, as well as WordPress theming, is scattered and in some ways archaic. Research and innovation is very welcome. Feels like everyone thinks inside the box, only diverging minimally from the competition.

              (but maybe my ADD head is just too far into the future:-)

Leave a Reply