Mainpage for doxygen

doc/img/graphviz/Makefile

@@ -1,14 +0,0 @@
-dotfiles := $(wildcard *.dot)
-images := $(patsubst %.dot,%.png,$(wildcard *.dot))
-
-all: $(images)
-	
-%.png: %.dot
-	dot -Tpng $< > $@
-
-.PHONY: clean distclean
-
-clean:
-	-rm $(images)
-
-distclean: clean

lodel/leapi/lefactory.py

@@ -1,5 +1,5 @@
 #-*- coding: utf-8 -*-
-
+## @package lodel.leapi.lefactory
 import os
 import os.path
 import functools

lodel/leapi/leobject.py

@@ -1,5 +1,4 @@
 #-*- coding: utf-8 -*-
-
 ## @package lodel.leapi.leobject
 # This module is centered around the basic LeObject class, which is the main class for all the objects managed by lodel.
 

lodel/leapi/query.py

@@ -1,5 +1,5 @@
 #-*- coding: utf-8 -*-
-
+## @package lodel.leapi.lequery
 import re
 import copy
 import inspect

lodel/plugin/plugins.py

@@ -1,4 +1,5 @@
 #-*- coding: utf-8 -*-
+# @package lodel.plugin.plugins
 
 import sys
 import os.path

mainpage.dox

@@ -0,0 +1,54 @@
+ /**
+\mainpage Lodel 2 documentation
+
+Lodel2 has two modes of operations : a standalone one, in that case Lodel2 is a customized CMS or and one, multisite case, in which it can be seen as a manager of CMS.
+
+Lodel2 has to perform 2 distinct tasks : to produce sites (cms), and to be a site.
+Plus, in the case of multisite install, it has to manage the produced sites.
+2 parts :
+- Editorial Model, whom the goal is to describe the structure of the content managed by the instance. This Editorial Model has to be built, and has to produce the python code which will represent the content.
+- LeAPI, which is a python API to manipulate the objetcs created by the first part.
+
+In case of multisite install the manager of the sites is a lodel site itself, like the others, with a adapted Editorial Model.
+
+Editorial Model part
+====================
+
+To represent the content we have :
+
+- Classes, the [EmClass](@ref lodel.editorial_model.components) module, it is a fields container which is named.
+- Fields, the [emField](@ref lodel.editorial_model.components) module
+
+These two modules are the components (see [EmComponent](@ref lodel.editorial_model.components)) of the content.
+
+In order to organize the different Editorial Models (for the different sites) from a single one, we have set up a system of groups, 
+the [EmGroup](@ref lodel.editorial_model.components). This system allows each site to activate or not certain groups. 
+A EmGroup can be seen as a EmClass end EmField named container.
+ Some groups can depend of other groups. 
+ This means that if EmGroup A is selected and it depends of EmGroup B, it must also be activated.
+
+CMS part
+========
+
+The Editorial Model, in fact, is the configuration of a lodel site, the cms.
+
+The produced CMS are instances of Lodel2.
+
+To manipulate the content (which is EmClass ) we have the [LeObject](@ref lodel.leapi.leobject) API. This class allows CRUD operations on content objects. To perform these operations it uses [LeQuery](@ref lodel.leapi.lequery) API, the bridge with the datasource.
+
+Datasources are [plugins](@ref lodel.plugin.plugins), like interfaces (IHM, cli, ...), extensions, scripts, session handlers.
+
+Plugins part
+============
+
+A lodel2 instance is an API. To produce a running application, we need plugins.
+
+Several types of plugins are mandatory : datasource, interface for now.
+
+LeFactory - Migration Handler
+=============================
+
+
+
+
+*/