[thelist] The quagmire of CMS

Thomas Moore thdomo at gmail.com
Tue Apr 24 16:08:39 CDT 2007

Well I said Contriibute not captivate. Not a flash program, doesnt
build flash sites, so your objections dont make sense in that context.

Anyway db content is not the main driver in my mind for using a CMS
though it may be the main technology behind many CMS's.

The main driver for me is having someone other than the web developer,
web master, etc having responsibility for the content.

A db is needed when the content changes regularly, often, and also if
it needs to be archived..

On 4/24/07, Christie Mason <cmason at managersforum.com> wrote:
> Sorry,  but I think of Captivate like this -  Captivate=Flash= ICK.
> Isn't dynamic content the main driver for using a CMS?  Put your content
> into a db and then call and present as needed.  Navigation is dynamic,
> content is dynamic, content is separate from the presentation.  Graphics are
> reusable, only need to be edited in one place then reuploaded and you're
> done.  Versioning and permissions are two other areas where Flash dependent
> sites struggle.
> Try changing a logo image in a Flash dependent site, I have and it was a
> horror.  Or, think about a scenario where the organization changes it's
> corporate colors.   Or new product images are produced. Plus, even though
> navigation can be dynamically generated for Flash dependent sites, most of
> the time it's not.  Also SEO and bookmarking issues.
> Christie Mason
> --
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !

More information about the thelist mailing list