I have a potential client who wants a website of his music and a calendar of his upcoming shows. He wants the ability to be able to post new audio sample .mp3s, flyers of shows, show dates/times, etc.

Is this something that is suited for using a blog like WordPress or should I go with a CMS?

I want to just limit his ability to changing text/images, nothing where he can screw up design of the site or where he can dink around and destroy something.

Just something where he logins, makes an update, logs out.

How would I do this and what technology is recommended for this?

Thanks!

I think wordpress would work well this this. It would not be as bloated with other non-essential items on the backend that somethign like joomla would have. On the flip side you might see where he plans to go with the site, becuase joomla offer alot of extensions that could be plugged in at a later date is he wants more functionality.

In either you can set him up as a user so he can login make his post and log out.

I would go with WordPress.

I want to just limit his ability to changing text/images, nothing where he can screw up design of the site or where he can dink around and destroy something.

Just something where he logins, makes an update, logs out.

To satisfy these specific demands I would definitely, by no doubt, recommend you Word Press. Very even-IT-illiterate-friendly. :agree:

I dunno....Wordpress is blogware meaning that it's designed to be updated chronologically. Every time he logs in and posts something, older posts will get bumped down the page. Maybe that's what you want and maybe not.

If you're intending to have a fairly static site and just change images and some text now and again, I'm not so sure blogware is going to work out for you.

Most CMSs allow different user levels. Depending on the CMS, you should be able to create a relatively unpriviledged user for your client to use which will only allow him at the things you specify.

If you are looking for a more simple but powerfull CMS look at Etomite or Websitebaker. They should do the job.

Actually, Wordpress has the ability to be used as a CMS. It is simple and easy to use that way.

Well..yes...the templating system is quite flexible and you can make it look like just about anything. I've done it once or twice before, but I've never been 100% happy with it. I figure that a CMS is good for CMS stuff and blogware is good for blogs. Trying to make one into the other generally ends up kind of Frankensteiney.

yeah it makes no sense to use wordpress for a CMS. it's like buying a honda and putting nissan stuff all over it.

If you want a cms (which is what you describe) use one. if you want a blog, use one. I also think wordpress, while simple, is nowhere near the best blog software.

I think either Wordpress or a CMS would work for this, but I'd probably lean toward a CMS like Joomla for a music site like this, just because it's a lot more flexible if his site grows and he wants more interactive features (tell a friend, reviews, etc.).

I think either Wordpress or a CMS would work for this, but I'd probably lean toward a CMS like Joomla for a music site like this, just because it's a lot more flexible if his site grows and he wants more interactive features (tell a friend, reviews, etc.).
That is a noteworthy comment. If the site specifics *music* is to be taken into consideration, then definitely a CMS (Joomla, Mambo) is a better bet. :)

Again, it is a matter of *weighing* - whether the accent will be on blogging and even more blogging (in other words - content) or interaction (just as Virgvv mentioned). If interaction is the main key feature, then choose CMS.

Speaking from experience, however, it is usually easier for some newbies in, let's say, *content management*, to get into the basics of Wordpress rather than to start easilywith Joomla/Mambo.