Blogreen Development Wiki

Abstract

Writing policies: this wiki is hosted on an English IP address, the XHTML pages have the attribute xml:lang="en" and the wiki content may be reused in future articles that will be mostly written in English. So, please, write as much as possible in English.

There is no licence for the wiki contents yet. You are therefore invited to consider everything you write subject to publication without prior confirmation nor notification.

Philosophy

An architect is a person who translates the user's needs into the builder's requirements.

(Source: Wikipedia)

Blogreen is the builder. The user is the architect. The architect can be a developer.

... or we may explain it like RockLinux does.

Goals

  1. Be concise: the core shall be as small as possible (max. 1000 LOSC?);

  2. Be hookable;

  3. Be layered;

  4. Be object.

  5. No [direct] dependencies (ie. self-suficient code).

So, what is Blogreen?

Somewhat that is between a Data Management System and a Stream Processing Schema. It is not a Content Management System since those systems are caracterized by a unique, centralized database wich (while beeing easy to install and use for the admin staff) is not flexible, can be limitted in functionalities and can be blocking for evolution of the services provided.

Work in Progress

Want to join the fun? Have a look to our IRC channel #blogreen on freenode.

Documentation

Unsorted pages

Edit [Edit this page] [Move to parent directory] Up