Posted by Rik on 03/08/07 18:03

tonnie <t.prasinge@chello.nl> wrote:

> Rik schreef:
>> tonnie <t.prasinge@chello.nl> wrote:
>>> Why a cms? Total overkill as it looks now. Use the time to teach her
>>> how to place content in HTML!
>> Hmmmz, a CMS is a real time-saver. Teaching a client HTML, billed by
>> the hour, quickly becomes very expensive. Also, it would mean a lot of
>> 'helpdesking' for them, you can just count on the fact that they will
>> call for every little problem they don't know how to solve.
>> Most of my clients have better things to do then to learn HTML, but
>> still want to be able to change content themselves.
>
> Nonsense, the time spent on teaching them how to handle the cms is
> wasted time, especially if one uses it for a small site like the one in
> the example.

For this example, maybe. I don't use the big CMS's, but a customizable one
of my own making. Exactly everything they need with a very intuitive
interface (allthough I have documentation there's no client that actually
asked for this, they see the interface and know what to do). Every
configruation/option they don't require is hidden or hardcoded to avoid
confusion. Should they require it in the future I'm happy to give them
access the options at no cost offcourse, it's all about having a
user-friendly back-end.

> I do teach my clients how to use a few elements, copy and paste, where
> they have to put what and how to upload it. Thats it, it aint no rocket
> science.
> Don't try to make your client believe it is, just because you want to
> make it yourself easy and earn quick bucks.

Highly dependable on the client. Having a CMS for the less savvy user is
cheaper for most. I'll bill by the hour if I have to explain HTML to them.

> Using a cms system for a small site like the one in the example is
> completely ridiculous, period.

Depends on how you use the CMS, and what is actuallyt customisable in it.
I rather like having a CMS for my own site, which saves me the headache of
creating new files/directories if I not only want to change pagecontent
but the hierarchy or change/add/remove pages. A few simple clicks and the
new files are ready, instead of me manually creating them, uploading them,
etc.

I do agree however that this is not a page which should be build on the
fly again and again. They're mainly static, so the CMS should just write
to files.
--
Rik Wasmus
Posted on Usenet, not any forum you might see this in.
Ask Smart Questions: http://tinyurl.com/anel

[Back to original message]