My good friend Mike has been at it for years now, providing a custom solution for his clients that is built just the way it needs to be... Proprietary and Simple - Page editing at it's simplest, along with apps he's built himself.

However, I don't have nearly the patience, or brainpower - I'm definately more a graphic/css designer - still learning the ropes, and don't currently have the strength or experience to build my own. So I wanted to get the voice of the community here and see what your solutions are.

To note some CMS/Blogging Engines I've used and *customized for clients are: Wordpress, Text Pattern, Joomla, and soon to try ModXCMS - http://modxcms.com

Personally I've started building custom CMS's, it's the best option if you've got the knowledge to do it. (It's surprisingly easy to do the basic stuff, the advanced not quite so easy!). It means you have greater control and understanding of what you're playing with.

Using a popular blog/CMS is a good alternative, but only if it fits the project. In the past I've used CuteNews, that's good if you just want to build a site then shove chunks of editable content in.

There are so many out-of-the-box CMS and blogging solutions out there, I really don't see a need to custom build one. From open source to high-end enterprise solutions, someone has already built a CMS that will fit your client's needs. If your skills are primarily in design and front end development, I would suggest focusing on learning how to get the most of a few different CMS solutions that your clients may need; in other words hack the Hell out of them.

Consider the amount of time/money it would take you to build a CMS vs. how much you might charge a client for the licensing fee of a Movable Type or Expression Engine.

Adjustfresh - Sometimes, those engines aren't perfect for the content. Photo galleries, flash, flash video, etc. When you design a blog like site, yeah, a blog engine will work. I've built custom cms before, multiple times. And sometimes, it comes down to xml files, php includes, mysql, etc.

It comes down to content. The question itself is subjective. And the cost of a custom cms dependant upon rather dynamic and varying content outweighs the cost of a license. Maybe I'm unfamiliar with those systems but a rather unique design calls for something less cookie cutter.



CSS != blog.

Right now, I'm using open source CMS-solutions, primarily Drupal, while I work on my own full-featured systems to offer later, when I plan to move into more freelancing/running my own small business.

The benefit to having your own solution is that it is your baby--you know it from the ground up. Sure, like one of my co-workers, you can make things like Drupal your baby, but I'd personally feel more accomplished, and feel like I'm offering a better service, were it my own solution.

Building custom CMS solutions from scratch is more to me about - Creating a fully bespoke solution, Working in technologies and techniques that I personally understand, Knowing the product inside out so you can solve any problems.

There are some good out-of-the-box CMS's out there... there are also some shoddy ones! Just because the car's already been invented, doesn't mean no-one ever produces a new one :)

Well written Ben.

Adjustafresh - Egos? I have no clue what you are talking about. None of the people that talked about building their own cms sounded remotely. Hacking the hell out of a pre-built CMS is fine if you have the time, but if you have already built a cms that mainly operates on 'widgets' that you have wrote, well it's bluntly not about ego, it is about the client, it's about knowing the system and being INDEPENDENT of others. If you want to talk about client's best needs, then say something like ego... You don't know my clients, and you don't know me well enough to use words like egos. I'm sorry if our words in support of custom CMS might have touched a soar spot.

I've built a CMS for my own site that OneCreative can attest and say it's brilliant for it's application. I can run any kind of site off of it, expand when needed. Even suggesting I package it up and release it. Rather bogus to suggest the people who can build good CMS systems do it out of ego... Some of us don't want to wait on others, or a widget, a bit more progressive than that. When we have the time, we build what we need for the client. In essence a developer creates a swiss army knife for their client, adding photo galleries, writing their own faq, uploading flvs, but keeping it all simple, not overwhelming to the client.

But where do you think the CMS applications that people use come from? Making what they need, then broadening it out as people see that it's usable past the developer's application.

I'm sorry, but suggesting spending time to hack something to all hell can be THE BIGGEST WASTE OF TIME if you know how to build a cms in certain circumstances. Don't be telling people about egos when you are goin off assumptions, it's not in good taste.

I'd put it to bed, but that last remark about client's footing the bill and designing something just for a portfolio... If client's come because of the work in the portfolio, it's not them flipping any bill just as much as it is having them pay for a license or the time to modify a CMS, it is about the same to the client. Credibility in the design community isn't associated with ego, it's associated with wanting to steer as many people in the right direction as possible.

Honestly, I tried negating all this talk with making a point that it's subjective and comes down to the client and their needs. I was thrown when the word ego was used, as I've never seen ego used in a good way, and to use it on such a question, with little input on the ones you are using it on. I by no means am trying to demean your best practices Adjustafresh, but please dood, don't ask to put something to bed when you finish the way you did.


My only point is that is is subjective and that a good CMS comes from a developer or group of designers working that develop a system out of work flow. Once it hits the right spot, it's released for public use. Is it for their ego? To make their portfolio look better? YES, because a custom well built specialized system that takes care of their clients is something to sell and increases productivity and therefore it is for the client. Not for dispute on a forum that has seemingly strong headed views from those who haven't seen a custom CMS from a person on the opposite side.

I'm not trying to flame you, but the things you've said lead me to believe you are strong in your position and haven't been forced outside of it to see the other side of the grass. Nothing wrong with that, but just don't assume it's ego, then defend ego, then quote someone saying 'proves the point' using it in a negative way. Not trying to teach you internet behavior, but pointing out that your defense of a pre-built CMS is based on negative assumptions from people you do not know, not solid examples of how a pre-built CMS doesn't turn out generally cookie cutter sites. I know they don't have to be, but part of their appeal, is just that. Quick, standard systems to make compliant sites that just look like a blog with box model designs. It's rare to see a pre-built CMS whipped into shape.

I'm also playing devils advocate.

cmsmadesimple (cmsmadesimple.org) is pretty easy to get up and running for basic websites.