Re: Standard list of WCMS features

Mitchell, Christine L (EM, PTL) wrote:
> ...Software is malleable. I don't think enough companies understand that.
> They
> tend to accept whatever vendors tell them when they start hitting
> limitations of the product...
> 
> Software is malleable if you have deep pockets when you start to hit that
> wall. Oh the pain of being at the mercy of a vendor whose product does not
> do what they said it would do without extensive (and expensive)
> customization. Then the additional pain that comes when they have an version
> upgrade but no clear upgrade path for your customizations. Then the
> additional, additional pain when it turns out that you now have a single
> point of failure, that one person who understands the customizations, and
> they leave.

What about working with products that understand the need for 
customisations?

It is possible to architect solutions that allow considerable 
flexibility in implementation without jeapordising companies' ability to 
easily participate in the core trunk of code.

For instance, most modern CMS's offer a templating engine that allow you 
to implement any look and feel without breaking the authoring 
environment -- why not look for the same sort of ability to extend and 
customise elsewhere in the framework?

-- geoff
http://farcry.daemon.com.au/