The distinction from us and business is that on our campus agreeing to
submit yourself to accountability of this sort is a pre-requisite for
admission. With contributors being more students than staff, and
rollover being therefore frequent this enforcing through the technology
is the alternative to an enormous workload for one full-time content
approver for all of campus. The only way we feel safe distributing
content management to the students, while still maintaining a very
specific guideline for our public image, is to require either content
approval or this kind of technological enforcement. Our current
browser-based web editor does control the users to specific layouts, and
styles, prohibiting embedded html (anybody know how to restrict certain
subject matter with a web part? j/k). We've had this same debate prior
to selecting sharepoint, because of the nature of SharePoint is to
empower. For web authoring though, we just need sharepoint for search
capabilities and re-usable libraries. It just happens to have a rich
text editor that is more capable than would be favorable for our needs.
We're actually considering for public web authoring supplying only page
layouts that contain content and image placeholders.
The rich editor toolbar for content placeholders would be what I want to
restrict in that case.
With sharepoint we're buying the Ferrari for our document management and
collaboration needs. For the web authoring portions of our deployment
all we need is the hood ornament, but not so shiny.