1) Since it really focuses on using iRite to control content, non-styled content that doesn't include html like link labels don't really fit that well. I imagine it would work, and it could be added to the framework in power cms, but currently it wouldn't lend itself to doing this well since it would allow such varied content when you only want a short label.
2) It is subject to the limitations of iRite including it's lack of ability to delete uploaded images. Images would have to be cleared through ftp if and when it was necessary, or an additional module could be created with digital file pro to delete.
3) No. This solution offers CMS without context. Which means that you can add it in context, but it doesn't have a concept of when and where it is displayed. This is more of the job for DataAssist to create a full fledged Data Management application.
4) The current version is a single level administration. It doesn't support user privilages and is designed for a single administrator or administrative group.
5) CMS would allow you to define content areas anywhere on the page, that then would be editable with the cms back end. In this case you would probably break it into 4 CMS entries and all three cols and header would be edited individually in the cms application.
6) You could break it out into as many content areas as you want, but quickly changing order would not be easy if it were broken into many areas, and it would be heavy if it were all manged in one.
7) The naming scheme is arbitrary and up to the developer. It can be whatever you want, but if you cannot come up with an intuative name as the developer, then some level of user training will be necessary.
8) Yes, as many as you want for as small or as large of an area as you want.
9) You have a source veiw in the editor just like DW if you have difficulty determining what you have selected you can look there.
