Yes, if we all knew php we could do the same, but most of us do not. So we have to rely on CMS to help foster content management.

do you mean you have to rely on a 'code package' to provide a CMS rather than make your own?

its not the concept of CMS thats the problem to you all is it? - its the package providing it - if all the other aspects of the code package (eg skinning, easy use etc) were easy for you, the CMS part itself (allowing a user to edit parts of a page) would not be such a problem - correct?

Yes i'm arguing technicalities here - thats because i think the idea of a CMS is a very good one - its just the implementation of the idea by the likes of joomla etc that make it difficult....

I work in close collaboration with my brother/sister-in-law who are both programmers and build databases and the cms you describe, usually based on asp. They often build large databases with many variations on a theme (eg.educational administration, medical studios, petroleum distribution chains etc) which take a long time to develop, test and launch. Unfortunately, their way is more expensive than my way, which is why I end up using cms packages - in particular DotNetNuke these days. My usual server limits how much I can actually do in there, but that is fine with me as they also take the brunt for any security issues which arise which is a big weight off my mind.

My limited experience with installing Joomla, for instance, has put me off to some extent, as I was responsible for the updates and checking for security problems and took up too much time, taking me away from areas of the business which I enjoy more.

As I have said on other occasions, there is no real reason to re-invent the wheel, and working as a one-woman-show, I also accept my limitations and realise that I cannot expect to be good/expert in all areas of the web application business so try to stick to those areas where I do know that I am fairly comptetent. There are loads of people out there who are excellent with cms building ground up, so rather than end up falling flat on my nose, I prefer to pass those commissions on to others when possible.

The farce still remains that even after messing around and getting in a real tangle to skin a cms site that my client has insisted on wanting, she then turns around and asks me to add all the content... here is the latest just sitting there waiting to get completed which just goes to show that it really is important in the early stages of communication with your client, that you check how much they really need to update by themselves! In this case the client is lucky that I have some standardized "stuff" to fill out her pages, but that would not always be the case of course.
veniceacquarello.com/

This may sound strange, but the only CMS that I have experience with is Expression Engine. Some time ago, I used it and learned a bit on how to manipulate it. I'm comfortable with it.

Typically how I've used it is as a sort of addendum to the main site. For example, I'm setting one up now to go with an existing martial arts site. The client really wants to have a set up for the instructors to be able to more or less blog; log on, post updates for various classes and seminars, and student highlights, plus also to have a place where students can interact. The person who made their "master site" does not have experience in doing this, so it was an opportunity for me to step in, offer a solution, and do it for a pay check.

Daniel

I have done that too Dan so I know what you mean. So long as the client doesn't come back and shout when they mess something up of course! Providing they are happy with limited administration rights, then you can overcome the problem. It's when they want all the keys to the house that you have to hold your breath.

I would love to learn how to build a CMS, but I also realize I cant do everything. This is why I have stopped, for now, at html/css/javascript, etc. But Fe you are correct.