Diogenes Documentation

1. Introduction

1.1. Diogenes and what it can do for you

Diogenes is a web content management system that allows you to create and manage multiple web sites on a single server via a web interface. It provides a sturdy authentication system with adjustable permission levels for each site and even for each page that makes up the site. Diogenes manages all the files that make up sites using revision control (you can choose between RCS and full-blown CVS), so the web sites can be managed collaboratively.

Diogenes was developped by Jeremy Lainé for Polytechnique.org, the non-profit organisation that manages Ecole polytechnique's alumni servers. Providing services both to individuals and to groups within the alumni community, it was realised that various alumni or student organisations need an easy-to-use (i.e for non programming-litterate people) web content management and hosting solution which gives them:

.. and this of course without any code replication for each additional site, otherwise it would become unmanageable! The resulting system is Diogenes, and it is released under the terms of the GNU General Public License (GPL).

1.2 Levels of Access

The Diogenes user interface is split into several levels (which happen to correspond to the sections in this manual, more or less). This allows the manager of the server or individual barrels to delegate authority on some barrels or pages to others, without having to give the other user access to anything else.

The Ultimate Authority in a Diogenes installation is the Server Administrator. They have the ability to:

Since the server administrator can change the admins for each barrel, they in effect also have control over every barrel and page on the server, although it is common for the server administrator to manage very few barrels herself, and instead delegate that tasks to other people -- the barrel admins.

Each barrel has one or more Barrel Administrators. Anyone with administrative access to a barrel can:

Sometimes, you only want someone to be able to modify some pages in a barrel, but not be able to add pages or change barrel-level settings. Diogenes supports this, by giving a user page admin access. Remember, also, that barrel and server administrators also have this privilege.

Page Administrators can:

Finally, there are ordinary website users. If you do not want to give access to some of your pages to the Internet at large, you can create user accounts in Diogenes and give those users only read-only access to some parts of your barrel or server.

The details of performing the actions available to each level of administrator is detailed in the relevant section of the manual (which you can find in the menu to your left).

1.3. The toplevel site

The Diogenes toplevel site is the main entry point to all the barrels. It also provides server administrators with tools to handle server-wide operations like managing user accounts, creating and deleting barrels.

Toplevel site

1.4. Diogenes, barrels et al.

You might be wondering why a web content management system is called Diogenes. Diogenes of Sinope was a Cynic philosopher who was born in Sinope, an Ionian colony on the Black Sea. One of the most famous anecdotes about his lifestyle is that he took up residence in a barrel (more acurately a pithos, or large tub).

The web sites created using the Diogenes content management system are referred to as barrels, because they are self-contained, each barrel having its own own separate content and permissions. All operations related to content and permissions are done at the barrel level.

$Id: page.html,v 1.4 2004/06/19 01:12:45 matthew.palmer Exp $