Simple is the name of the CMS that runs my personal website (this website). This PHP/MySQL system allows me to directly edit pages on the site from any computer with internet access and a reasonably competent browser. It automatically arranges the pages into a hierarchy on the fly, complete with user and group permissions properly inherited throughout the tree.
When logged in, the user gets a bar placed at the top of the page with the controls appropriate for his or her permissions on that page. If the user has permission to edit, there will be controls for editing. If the user has permissions to delete, there will be controls for deletion.

From there, the users can click edit, make changes in a WYSIWYG editor, and then publish those changes onto the live page. Pages are rendered into static pages in order to allow the server to cache the results.

If the user just wanted to undo a mistake made when editing a page, he or she can restore a previous revision of the page with just a few mouse clicks.

In order to change access levels for a page, a use can use either the Page User Permissions panel or the Page Group Permissions panel. Both panels will show who's inheriting permissions, what permissions they're inheriting, who's got special permissions set, and what those special permissions are.

Page permissions for groups and users are automatically inherited. So, in order to give editing access for a section (i.e. Admissions) to a group (i.e. the Office of Admissions), a user with "manage" rights must grant "edit" right for the group "Office of Admissions" on the Admissions home page. Then, the "edit" rights will be applied to the Admissions home page, as well as every other page within the Admissions section.
One intentional caveat, however, is that should a user revoke any rights for an Administrator (such as the Webmaster), the Administrator attribute in that user's settings will override the permissions settings. So, in a nutshell, nobody can prevent the site administrators from accessing their pages.
While this limited overview can give you a rough impression of the administrative side of the Simple CMS, I would encourage you to view the Simple section of this site for a more end-user-oriented overview of the system including a project timeline and user documentation.