Using database

Hello,

what are actually the advantages of programming a dynamic website with
database to making a static website with a CMS? My client says:
I will not need a database, once I could be able to edit the content of my
website with a CMS?
I couldn't still find enough argues to persuade him.

Thanks,
Steve

Steve wrote:

Hello,

what are actually the advantages of programming a dynamic website with
database to making a static website with a CMS? My client says:
I will not need a database, once I could be able to edit the content of my
website with a CMS?
I couldn't still find enough argues to persuade him.

Hi

These are the same thing. A dynamic web site would have a CMS to
interface with the database, you cannot have a static web site that is
run by a CMS. A static web site by nature has the content hard coded
into the page.

You could use xml to negate the use of a database if you wanted to but I
wouldn't have a client editing xml files if I could help it.


--
Cheers jojo
Team Macromedia Member Volunteer for Dreamweaver MX
http://www.webade.co.uk
http://www.cmsforbusiness.co.uk
----------------------------------------------------
Extending Knowledge, Daily.
http://www.communityMX.com/
Free 10 day trial
http://www.communitymx.com/joincmx.cfm
----------------------------------------------------

"jojo" <jojo (AT) zoot3 (DOT) com> wrote

Steve wrote:
Hello,

what are actually the advantages of programming a dynamic website with
database to making a static website with a CMS? My client says:
I will not need a database, once I could be able to edit the content of
my
website with a CMS?
I couldn't still find enough argues to persuade him.

Hi

These are the same thing. A dynamic web site would have a CMS to
interface with the database, you cannot have a static web site that is
run by a CMS. A static web site by nature has the content hard coded
into the page.

You certainly can have a CMS with "static" pages. I have one site that works
this way. The CMS is an online editor that alters the html directly on the
page - no database is involved.

I prefer to use a database driven CMS for pages that may have several
"articles", and that allows easy article updates/deletions and even time
based content. It might also make content archiving a bit easier. Of course,
if your client has a product catalog and event calendar, you would need a
database for those. But there's certainly nothing wrong with a CMS that
manages static pages..