[IxDA Discuss] Designing for CMS

[Jay Barbarich]

I think that the problem of designing for a CMS depends upon the CMS
itself.

I've been fooling with Drupal for a while and find that I can muddle
through the creation of basic app with almost no additional
constraints on account of the CMS. Its all open source, so you're
working with predominantly PHP and JavaScript for functionality, and
then CSS for aesthetics. Everything is more or less familiar and
pretty object-oriented in approach, and it pretty much good-to-go
right out of the box on a LAMP setup.

Of course I was granted the luxury of getting to choose the system
appropriate for my needs. I think that if a client arbitrarily
chooses the CMS that they think is the best (because of branding or
otherwise, *cough* M$ CMS *cough*), then, echoing Bryan's
sentiments, you might end up spending more time/money trying to bend
the system to your needs than you would've by simply rolling your
own.

It seems like if you have the ability to do so, picking a (or rolling
your own) CMS that aligns with your needs and abilities would make for
a rather pleasant experience in the realm of design/development.


. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://gamma.ixda.org/discuss?post=23301