Toby,
The priority for ease of use in Siteframe always defaults to the user. That is not to say that it is hard to administer - it's not. I have tried many, many different systems and choose Siteframe because it is simple and easy to use. I will say that it is a bit more difficult to template than some because you need to know a little Smarty, but there are good reasons for using Smarty as a standard (because..well..it's a standard). The biggest problem we have here is documentation. This is a very small community in terms of active contributors and your success with Siteframe will require an investment of time on your part if you want to run anything other than a default install. If I ever get the time to I am going to put together a more thorough How To on template and template functions, that I hope will help some out there.

As far as keeping it easy for your users - You need to identify what functions/features they REALLY need and start there. I would not include a thing more than you need on your first release. Keep it simple and then scale as you need.

And you may want to check out Chatter, which is kind of like a Siteframe Lite. It is already set up for the minimum feature set required to run a community blog.

Coby

I've also noticed how search engine friendly it is. I've got something running in 'stealth' mode and it's becoming a problem.

I thought about cutting out some of the features, like folders and groups, etc, but I've found people seem to like them. They complain about not knowing what to do at first, but then have a good time using features I never payed much attention to. it depends how democratic you want it to be, I think.

This is the simplest and most easily expandable cms I've found so far.