For database websites, why use Dreamweaver when you canjust use a CMS?

Hello,

Can anyone tell me what the purpose is of using Dreamweaver to build a
database driven website if using a CMS is so much easier? I mean, if a CMS is
the way to go, what's the purpose of owning Dreamweaver?

Thanks,
Jenn

Jennifer90 wrote:

Hello,

Can anyone tell me what the purpose is of using Dreamweaver to build a
database driven website if using a CMS is so much easier? I mean, if a CMS is
the way to go, what's the purpose of owning Dreamweaver?

Not all database driven websites are CMS

Sometimes a CMS is too much for a simple site.

Some people enjoy the learning process of creating there own database
driven website.

If your building a site that can be built with a CMS, sure, use it, but
you end up relying on the developers to make sure its secure. If you
made it, you know how it works, so you know how to make changes or
protect it.

Dooza

I mean, if a CMS is the way to go, what's the purpose of owning
Dreamweaver?

If a CMS is the way to go for a given project then you may well not need
Dreamweaver.

However, the trick is establishing that a given CMS solution is the way to
go for a given project.

http://en.wikipedia.org/wiki/List_of...gement_systems

By choosing a specific CMS solution, you are adopting a pre-made framework
and a specific way of doing things. If you've made the right choice for a
project, this may well be a breeze. If not, you may regularly be frustrated
and find yourself going under the hood to make suitable mods far more often
than you might wish. Or frequently requesting new features and waiting for
them to be added or improved.

CMSes are not created equal. They all have their own unique framework,
idiosyncracies, support forums, strengths and weaknesses and means of
tweaking and modifying them to suit your purposes. Some are easier to
understand and manipulate than others. Some allow simple mods, others are
very powerful (perhaps overwhelming to some) allowing very granular mods and
make it hard or easy to do so depending on your skillset.

--
Regards

John Waller

CMS is good for small websites, but it also opens your website to security
hacks. Since the cms applications are closely followed, their vulnerabilities
are easily exploited unless you keep upgrading to regular patches and upgrades.

Good point.

--
Regards

John Waller

On Fri, 19 Sep 2008 12:58:34 +0000 (UTC), "merlinvicki"
<merlinvicki (AT) yahoo (DOT) com> wrote:

CMS is good for small websites, but it also opens your website to security
hacks. Since the cms applications are closely followed, their vulnerabilities
are easily exploited unless you keep upgrading to regular patches and upgrades.

Nonsense. Depends entirely on the CMS - AND the capability of folks
who develop it, install it, and maintain it.

All CMS means is content management system. There are quite literally
hundreds of packaged solutions available, some free, some commercial,
and some custom-built. Labeling them all security risks is
irresponsible.

Win
--
Win Day
Wild Rose Websites www.wildrosewebsites.com
winday (AT) wildrosewebsites (DOT) com

Win Day wrote:

All CMS means is content management system. There are quite literally
hundreds of packaged solutions available, some free, some commercial,
and some custom-built. Labeling them all security risks is
irresponsible.

I think the popular free ones are a security risk if the person who
installs it knows nothing about the risks.

I have been testing Joomla for sometime, but got sidetracked and left
the test site up. This site isn't publicly linked, I only showed it to a
few people, but when I went back to look at it the other day it had been
hacked. My version was 1.5.1, the current release, less than 4 months
later, is 1.5.7. All the dot releases had been security related.

I ended up deleted the database and files, and won't be testing on a
live server again until I totally happy with what I am doing. And even
then I will sign up to news lists to make sure when an update comes
along I install it immediately. I will also take every measure I can to
reduce any chance of harm that can be done.

Dooza

On Fri, 19 Sep 2008 16:20:29 +0100, Dooza <doozadooza (AT) gmail (DOT) com>
wrote:

Win Day wrote:
All CMS means is content management system. There are quite literally
hundreds of packaged solutions available, some free, some commercial,
and some custom-built. Labeling them all security risks is
irresponsible.

I think the popular free ones are a security risk if the person who
installs it knows nothing about the risks.

I have been testing Joomla for sometime, but got sidetracked and left
the test site up. This site isn't publicly linked, I only showed it to a
few people, but when I went back to look at it the other day it had been
hacked. My version was 1.5.1, the current release, less than 4 months
later, is 1.5.7. All the dot releases had been security related.

I ended up deleted the database and files, and won't be testing on a
live server again until I totally happy with what I am doing. And even
then I will sign up to news lists to make sure when an update comes
along I install it immediately. I will also take every measure I can to
reduce any chance of harm that can be done.

Dooza

Then have a look at Expression Engine. The core version is free.

I still hold that labeling every CMS as a security risk is
irresponsible.

Win
--
Win Day
Wild Rose Websites www.wildrosewebsites.com
winday (AT) wildrosewebsites (DOT) com

*anything* is a security risk when the person using it doesn't know about
the risks, no?

--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Dooza" <doozadooza (AT) gmail (DOT) com> wrote

Win Day wrote:
All CMS means is content management system. There are quite literally
hundreds of packaged solutions available, some free, some commercial,
and some custom-built. Labeling them all security risks is
irresponsible.

I think the popular free ones are a security risk if the person who
installs it knows nothing about the risks.

I have been testing Joomla for sometime, but got sidetracked and left the
test site up. This site isn't publicly linked, I only showed it to a few
people, but when I went back to look at it the other day it had been
hacked. My version was 1.5.1, the current release, less than 4 months
later, is 1.5.7. All the dot releases had been security related.

I ended up deleted the database and files, and won't be testing on a live
server again until I totally happy with what I am doing. And even then I
will sign up to news lists to make sure when an update comes along I
install it immediately. I will also take every measure I can to reduce any
chance of harm that can be done.

Dooza

Win Day wrote:

Then have a look at Expression Engine. The core version is free.

I had a look after your previous recommendation, but wasn't sure how it
worked, as you needed other stuff to get it going. I will revisit it again.

I still hold that labeling every CMS as a security risk is
irresponsible.

Yes, I agree, you can't call every CMS a security risk.

Dooza