summaryrefslogtreecommitdiff
path: root/docs/configuration.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/configuration.rst')
-rw-r--r--docs/configuration.rst59
1 files changed, 40 insertions, 19 deletions
diff --git a/docs/configuration.rst b/docs/configuration.rst
index f8bed2b..0565509 100644
--- a/docs/configuration.rst
+++ b/docs/configuration.rst
@@ -33,6 +33,16 @@ To access theses pages you have to identify you with an account with *staff* and
A *superuser* account is created at the initialization of the database.
+Configuring the sites framework
+-------------------------------
+
+*Sites* framework allow you to serve the same content on different domains.
+Most of you will probably use only one domain but this unique domain has to
+be configured. This is done in the web administration interface in *Sites > Sites*
+You only need to change *example.com* by your domain name. If you forgot to
+do that functionality such as RSS feeds will not work properly.
+
+.. _managing-areas:
Managing areas
--------------
@@ -40,29 +50,36 @@ Managing areas
An *Area* is the base of your map. It defines:
* a name: a human readable label for this area.
+* an associated URN (*not mandatory*): the name of the area as a web ressource.
+ In practice, if the area is not the default area the URN is used at the end of
+ the default URL to access to this area. This is not mandatory but necessary
+ for each area that is not the default one.
* a welcome message (*not mandatory*): this message is displayed once a day per
user arriving on the map.
-* a map bounding box: this is the default area to display when arriving on the
- map.
-* restriction on the bounding box: if set to restricted, the end user can't pan
- outside the defined bounding box.
-* available layers (*not mandatory* OSM Mapnik is used by default): OSM Mapnik
- render, OSM MapQuest render, OSM Transport Map render, OSM CycleMap are
- available by default. You can add new custom layer cf. :ref:`managing-layers`.
-* categories restriction (*not mandatory*): if no restriction is set all
- categories are available.
+* an order (to sort areas).
+* an availability.
+* a default state. The /default/ area is viewed by default. Only one area can
+ be the default: activating this state disable it on the possible other area
+ with a default state.
* default checked categories (*not mandatory*).
-* an external CSS file (*not mandatory*): an URL to an external CSS file.
* if categories are displayed dynamically (if dynamically is set, the end user
only view categories witch have items on the map section the user currently
see).
-* an associated URN (*not mandatory*): the name of the area as a web ressource.
- In practice, if the area is not the default area the URN is used at the end of
- the default URL to access to this area. This is not mandatory but necessary
- for each area that is not the default one.
+* categories restriction (*not mandatory*): if no restriction is set all
+ categories are available.
+* an external CSS file (*not mandatory*): an URL to an external CSS file.
+* restriction on the bounding box: if set to restricted, the end user can't pan
+ outside the defined bounding box. Due to technical reasons, there is at this
+ time no restriction on the zoom.
+* a map bounding box: this is the area to display when arriving on the map. If
+ the area is restricted it will be the bounding box that restrict the end user.
+ Hold the control key, click and drag to draw the bounding box.
+* available layers (*not mandatory* OSM Mapnik is used by default): OSM Mapnik
+ render, OSM MapQuest render, OSM Transport Map render, OSM CycleMap are
+ available by default. You can add new custom layer cf. :ref:`managing-layers`.
*Areas* are customizable directly on the web administration interface in
-*Chimere/Areas*.
+*Chimere > Areas*.
As there is little chance that the default area is appropriate for you, you'll
have to set at least one default area.
@@ -92,8 +109,8 @@ and a default password (the user can change it on in own later).
Then complete the other pieces of information.
-Check the case: *Staff status* (or this user will not be able to log to
-the administration website).
+Check the case: *Staff status* (or this user will not be able to log to the
+administration website).
If this account is a new technical administrator, check *Superuser status* (this
user must be trustworthy!). Otherwise you'll have to give permissions to this
@@ -151,15 +168,19 @@ model*).
The administration page ask you for:
* a name,
-* an order (to order between other properties),
+* an order (to sort properties),
* an availability to the end user (this can be used to set hidden properties),
* a mandatory status,
* the categories the property applied to (if no categories selected it applied
to all),
* the type: text, long text, password or date.
-To make this property available it is necessary to reload your webserver (the
+To make this property available it is necessary to reload your web server (the
property is cached).
All forms are then automatically updated with this new field.
+If you don't want to allow add and modification of properties you can disable
+this form by setting CHIMERE_HIDE_PROPERTYMODEL to *True* in your
+*local_settings.py* file.
+