Re: Roles in CMS --> was -->Re: Netdoc

> Yep, but IA is not rocket science. Consultants and tools should enable
> those who want to be architects (even if they don't know what IA means)
> to do what they need/want to do. But what does this have to do with PHP
> developers?

Actually I'm writing a thesis on CMSs, and will be using Netdoc as an
example there. Questions like "But what does this [IA stuff] have to do with
PHP
developers?" are good to ponder in it.

Of course one could argue that an IA could use pen & paper / his (her) head
/ some other tool to think about the site structure and let the coding be
done by some other person - but I know that this is a bit of running away
from the problem and maybe it a bit clumsy way (and not always possible).

Achieving a good compromise here may be difficult... of course if we think
of PHP as an user interface, it's quite powerful and versatile, and it
wouldn't hinder the IAs performance at least in what he could do with the
site. I can imagine that an IA is frustrated in front of some CMSs that just
don't let him do what he wants, or it's somehow too hard (yes PHP may also
be hard).

Maybe one could use some kind of plugins and modules to help the IA, and in
reality that would probably be the case. But if this goes too far, we may
have an UI in the CMS itself, which allows the IA to arrange the page blocks
etc., and I'm not sure if that's good. Is it...?

Ilkka