I used to make sure when i do a site for a client that i tell them if the site is built on wordpress or if just a static site.....does it really matter? often i find i am quoting on a site and will probably build it with static pages.....and then later decide it might be easier for me to maintain and update if built on worpress. So my dilema is do i tell the client when i change the basic framework as i dont think i have to....as the final product is still the same (to them)....but i am not sure.....was curious what others do in this situation?
i think it depends on the client, given that some barely know what a browser is, i think it complicates things for them if you tell them more than they need to know. eg they want a website. they don't want to know about linux or windows or wordpress or drupal or anything else for that matter.
i agree with you topr8....was just always in the habit of "full disclosure" but lately it has become more of a problem and is limiting me should i decide something else....even if it is in the clients best interest it is often hard to explain why the change. So i guess its a less is more approach and not go into too much detail as to what and how it is built but make sure the final product speaks for itself...thanks for your input i was just curious if others had similar experiences.
If you are not hosting the site, I say definitely yes. It may require additional work to coordinate with the hosting company to make sure everything is configured properly.
If you are hosting the site yourself (so you will be dealing with all the configuration/updates yourself), I'd still say yes. If the client thinks you're building a site from scratch, then later find out that you used a CMS and (in their eyes) just pushed a few buttons and added some content, most likely they're going to feel ripped off.
State it in the contract. They may not have any interest, but then again, they might.
If you are hit by a truck, how hard will it be for the client to replace you?
The client may not think of this-- though they should-- but as a professional you should definitely take it into account. Same as with any contract: What happens if for reasons beyond your control you are unable to do the work?
From "I use a terrific programming language that I developed myself and nobody else in the world knows how to use"
to "I use an out-of-the-box CMS that has its shortcomings but any idiot off the street* can pick up where I left off"
... and then you work out where on the continuum you fit.
* Possibly including the client himself, though you won't put it in those words ;)