Code yourself or CMS?

Thank you very much Andrew. I definitely don't have the knowledge to code a CMS and I believe that would be more than a "1-man's-job". However, my question was more towards the 'simple website', that doesn't have content being added to it all the time. I should've made that a little clearer, my apologies!

The way I see, Wordpress would really be advantageous because it makes blogging easy, and for those who aren't very proficient at php/MySQL, databases and etc, that would be a tremendous advantage considering they'd have to only create content, maybe work the layout a bit on CSS and the functionality of Wordpress would take care of the rest.

But for a simple static page (not a blog), if it'd there be any advantage or disadvantage on using Wordpress for a simple website or code it yourself. A website that uses HTML, CSS and maybe JavaScript for some interaction, but that doesn't go/need databases or more dynamic content creation.

Thanks again for your input.

I hear you. And I still think it revolves around what is the right tool. What will do what you need to. And, with both options being equal, what's the most efficient. I did a one pager a few months ago in Wordpress. I needed user access, and for my client to easily update and manage the content, and we needed it to be done quick. I threw up Wordpress, added some style for my one page, coupled in several plugins, and in a matter of an hour the client had everything they needed with an easy to use interface to update it.
Now, if had been doing this for myself, I would have just typed out the code.

Aha! Nice. So it made the job faster on that case, when you needed it.

Great. Thanks once more for your time!

Andy,

"they really don't care about the tool we use to do it."

I bet most clients would have no idea which platform was used to build the site from the other.

As long as the project meets or exceeds the clients needs, they won't care about the tools used to build it. (as you already stated)

When communicating with clients before builds I have come across a somewhat of a stigma in regards to Wordpress as a blogging only system, but after showing them the possibilities and ease of use what these CMSs can achieve, they're much easier to get on board.

Additionally, from a developers standpoint, why try to re-invent the wheel when there are already so many tried and tested themes, plugins, etc to use at will. This not only speeds up the building process, but it usually also guarantees a happy client, in the short and long term.

exactly. I use to hit that border with Wordpress when I knew I was going to choose to use it. Sometimes I realized they just weren't a client I wanted to work because they were going to micro-manage me and tell me what tools I could use (I don't like clients who think they know more about my job than me). Other times I did like you mentioned and should them sites that they never thought would have been a Wordpress site. Now a days, I don't even usually tell them. They describe the problem, I create the solution. Once they see the frontend and how it meets their needs, they are usually happy that the backend is Wordpress because a lot of them are somewhat familiar with it already.

Good point Christian, thanks for that!

We can always use CMS, it's a matter of "why use?" and "why not use it?" that I was looking for.

Thanks for your response.

Thanks for your input Vlatko, appreciated.

Guess everybody sort of likes working with something a little more practical!