16 |
16 |
|
17 |
17 |
At the current state the application provides the following features:
|
18 |
18 |
|
19 |
|
* basic cms funcionality (adding/removing/editing hierarchical pages)
|
20 |
|
* blog application
|
|
19 |
* Basic cms funcionality (adding/removing/editing hierarchical pages)
|
|
20 |
* Blog application
|
21 |
21 |
* FAQ application
|
22 |
22 |
* Resources application (for presentations, technical papers etc.)
|
|
23 |
* User guide application
|
23 |
24 |
|
24 |
25 |
.. _django: http://www.djangoproject.com
|
25 |
26 |
.. _feincms: http://feinheit.ch/media/labs/feincms/
|
... | ... | |
40 |
41 |
|
41 |
42 |
.. _snf-webproject: http://docs.dev.grnet.gr/snf-webproject
|
42 |
43 |
|
|
44 |
.. note::
|
|
45 |
|
|
46 |
Synnefo components and additional required packages can be obtained from
|
|
47 |
``apt.dev.grnet.gr`` debian repository. To enable the repository add the
|
|
48 |
following lines in ``/etc/apt/sources.list.d/apt.dev.grnet.list``::
|
|
49 |
|
|
50 |
deb http://apt.dev.grnet.gr squeeze main
|
|
51 |
deb-src http://apt.dev.grnet.gr squeeze main
|
|
52 |
|
43 |
53 |
Install required packages::
|
44 |
54 |
|
45 |
55 |
apt-get install snf-common snf-webproject
|
46 |
56 |
apt-get install python-django-feincms python-django-pagination python-django
|
47 |
57 |
|
48 |
|
.. note::
|
49 |
58 |
|
50 |
|
``python-django-feincms`` and ``python-django-pagination`` are not provided
|
51 |
|
currently on debian stable but can be backported from sid.
|
52 |
|
|
53 |
59 |
then, install ``snf-cloudcms`` package::
|
54 |
60 |
|
55 |
61 |
apt-get install snf-cloudcms
|
... | ... | |
159 |
165 |
Admin guide
|
160 |
166 |
===========
|
161 |
167 |
|
162 |
|
Bind blog to a cms page
|
163 |
|
-----------------------
|
|
168 |
Bind blog application to a cms page
|
|
169 |
-----------------------------------
|
164 |
170 |
|
165 |
|
1. Create a page on the cms tree.
|
|
171 |
1. Create a page on the cms tree using the ``Blog template`` template.
|
166 |
172 |
2. On the region you want the blog content to appear (list of posts, and post
|
167 |
173 |
details), add an ``Application content`` content type and choose ``Cloud
|
168 |
174 |
blog`` from the drop down list.
|
169 |
175 |
3. On navigation extension settings of the page, choose ``blog categories``.
|
170 |
176 |
|
171 |
|
Bind FAQs to a cms page
|
172 |
|
------------------------
|
173 |
177 |
|
174 |
|
1. Create a page on the cms tree.
|
175 |
|
2. On the region you want the blog content to appear (list of posts, and post
|
176 |
|
details), add an ``Application content`` content type and choose ``Cloud
|
177 |
|
FAQ`` from the drop down list.
|
|
178 |
Bind FAQs application to a cms page
|
|
179 |
-----------------------------------
|
|
180 |
|
|
181 |
1. Create a page on the cms tree using the ``FAQ's template`` template.
|
|
182 |
2. On the top region add an ``Application content`` content type and choose
|
|
183 |
``Cloud FAQ`` from the drop down list.
|
178 |
184 |
3. *Optional:* On navigation extension settings of the page, choose
|
179 |
185 |
``faq categories``.
|
180 |
186 |
|
181 |
|
Bind resources to a cms page
|
182 |
|
----------------------------
|
|
187 |
|
|
188 |
Bind resources application to a cms page
|
|
189 |
----------------------------------------
|
183 |
190 |
|
184 |
191 |
1. Create a page on the cms tree.
|
185 |
192 |
2. On the region you want the resources to appear append a ``Resources list``
|
186 |
193 |
content type.
|
187 |
194 |
|
188 |
195 |
|
189 |
|
FAQ's guide
|
190 |
|
-----------
|
191 |
|
|
192 |
|
Adding a question
|
193 |
|
^^^^^^^^^^^^^^^^^
|
194 |
|
|
195 |
|
1. Open the faq's list in admin panel (``/cmsmanage/cloudcmsfaq/question/``)
|
196 |
|
and press the ``Add faq`` button.
|
197 |
|
2. Fill in the required fields:
|
198 |
|
* Title, the question.
|
199 |
|
* Author, the question author.
|
200 |
|
* Slug, the url to be used for the current question
|
201 |
|
(should get autocompleted after filling the title field)
|
202 |
|
* Category, the category of the question.
|
203 |
|
|
204 |
|
3. On the main content area tab add the content you want to be displayed as the
|
205 |
|
answer of the question.
|
206 |
|
* ``Rich text`` (can be added by pressing the icon with the pencil) and
|
207 |
|
``Raw content`` may contain html text.
|
208 |
|
|
209 |
|
4. Click save.
|
210 |
|
|
|
196 |
Bind Userguide application to a cms page
|
|
197 |
-----------------------------------------
|
|
198 |
|
|
199 |
1. Create a page on the cms tree using the ``Userguide template`` template.
|
|
200 |
2. On the top region add an ``Application content`` content type and choose
|
|
201 |
``Cloud user guide`` from the drop down list.
|
|
202 |
|
|
203 |
|
|
204 |
Importing FAQ's and Userguide entries from rst files
|
|
205 |
----------------------------------------------------
|
|
206 |
|
|
207 |
Cloudcms provides a way to import content for faq and userguide applications
|
|
208 |
from rst files. This allows you to keep the guide and faq content tracked in
|
|
209 |
rst markup format seperately from the cms database (e.g. in a git repository
|
|
210 |
maintained by your documentation team), and update the cms content on demand.
|
|
211 |
|
|
212 |
.. warning::
|
|
213 |
Notice that you can still edit the FAQ's and Userguide entries using the
|
|
214 |
corresponding section in the cms admin interface, but beware that mixing both
|
|
215 |
methods is not recommended since it's ineffective and prone to data loss.
|
|
216 |
|
|
217 |
To access the import form, login to the admin site and open the following url::
|
|
218 |
|
|
219 |
https://cms.com/cmsmange/rstimport/
|
|
220 |
|
|
221 |
The required file should be a zip archive containing files of the following
|
|
222 |
structure (similar to common sphinx project structure)::
|
|
223 |
|
|
224 |
|
|
225 |
|
|
226 |
├── README.rst
|
|
227 |
└── source
|
|
228 |
├── conf.py
|
|
229 |
├── faq
|
|
230 |
│ ├── cyclades.rst
|
|
231 |
│ ├── index.rst
|
|
232 |
│ ├── okeanos.rst
|
|
233 |
│ └── pithos.rst
|
|
234 |
├── images
|
|
235 |
│ ├── cyclades
|
|
236 |
│ │ ├── image10.png
|
|
237 |
│ │ └── image9.png
|
|
238 |
│ ├── faq
|
|
239 |
│ │ └── faq_image1.png
|
|
240 |
│ ├── intro_img_cyclades.png
|
|
241 |
│ └── pithos_guide
|
|
242 |
│ └── image2.png
|
|
243 |
├── index.rst
|
|
244 |
└── userguide
|
|
245 |
├── cyclades.rst
|
|
246 |
├── index.rst
|
|
247 |
├── pithos.rst
|
|
248 |
└── quick-intro.rst
|
|
249 |
|
|
250 |
.. warning::
|
|
251 |
Notice that directory names ``faq``, ``userguide`` are mandatory.
|
|
252 |
|
|
253 |
|
|
254 |
By submiting the form the application will act as follows
|
|
255 |
|
|
256 |
- Clean existing data if ``clean data`` was checked. This includes **all**
|
|
257 |
FAQ/Userguide entries, FAQ categories and media files linked to them.
|
|
258 |
- Will search for files named after the ``CMS_RST_IMPORT_SERVICE_FILE_MAP``
|
|
259 |
setting both in ``faq`` and ``userguide`` directories, to identify which
|
|
260 |
service the contents of the file are referred to. The default setting value
|
|
261 |
is (maps files to service slugs)::
|
|
262 |
|
|
263 |
DEFAULT_SERVICE_MAP = {
|
|
264 |
'cyclades': 'cyclades',
|
|
265 |
'okeanos': 'okeanos',
|
|
266 |
'pithos': 'pithos'
|
|
267 |
}
|
|
268 |
|
|
269 |
- For the FAQ entries which are structured by service/category, the importer will
|
|
270 |
parse secondary headings as FAQ categories and tertiary headings as FAQ
|
|
271 |
entries.
|
|
272 |
- For the Userguide entries which only require the service to be linked to, the
|
|
273 |
secondary headings and their content are parsed as Userguide entries
|
|
274 |
- For both FAQ and Userguide entries the linked images will be uploaded
|
|
275 |
in the media files application and the html anchors will get updated
|
|
276 |
containing a valid cms link.
|
|
277 |
|
|
278 |
.. warning::
|
|
279 |
Import helper uses python ``docutils`` to parse .rst files contents. This
|
|
280 |
means that additional sphinx directives like ``:ref:`` or ``.. code-block``
|
|
281 |
won't be parsed as excpected. This behaviour might get improved in future
|
|
282 |
versions. Until then try to compromise your content to `basic rst format`_.
|
|
283 |
|
|
284 |
.. _basic rst format: http://docutils.sourceforge.net/docs/user/rst/quickstart.html
|
211 |
285 |
|
212 |
286 |
.. include:: ../../Changelog
|
213 |
287 |
|