Updated introduction
authorThierry Florac <tflorac@ulthar.net>
Sun, 11 Mar 2018 11:40:48 +0100
changeset 23 c4d22fabf017
parent 22 2dfb4161b66c
child 24 be7ec27f09bb
child 26 7d77990df225
child 28 a7332a53e6dc
Updated introduction
src/source/index.rst
--- a/src/source/index.rst	Tue Mar 06 11:24:09 2018 +0100
+++ b/src/source/index.rst	Sun Mar 11 11:40:48 2018 +0100
@@ -30,6 +30,9 @@
 * command line scripts
 * custom utilities.
 
+*PyAMS_content* is an important package providing content management features, which can be easily extended to manage
+your own content types. But PyAMS can also be used to manage any kind of application.
+
 If you just want to know how easy it is to create a PyAMS application instance, just read the :ref:`quickstart`!
 
 To know how PyAMS management interface looks like, look at :ref:`screenshots`!
@@ -49,16 +52,16 @@
 PyAMS applications architecture
 -------------------------------
 
-PyAMS applications are built on a small set of prerequisites and components which *can* or, for some of them, *must*
-be included. Some of them are:
+PyAMS applications are built on a small set of prerequisites and external components which *can* or, for some of them,
+*must* be included. Some of them are:
 
 * a mandatory shared ZODB;
 
+* a Redis or Memcached server, to handle cache and sessions;
+
 * a websockets server, used to handle desktop notifications; you can find information about this component in the
   :ref:`pyams_notify` chapter;
 
-* a Redis or Memcached server, to handle cache and sessions;
-
 * an Elasticsearch index, used to handle quick and optimized searching.
 
 See :ref:`architecture` to get all architecture details.