Issue 2196 - [cms] Drop depencency on Flask for test server

README.md

 # CMS #
 
 We use this CMS for [adblockplus.org](https://github.com/adblockplus/web.adblockplus.org/)
 and related websites. It converts a directory with content data into static
 files. You are free to use it for other projects but please keep in mind that we
 make no stability guarantees whatsoever and might change functionality any time.
 
 ## How to use ##
 
 ### Running the test server ###
 
 The test server will convert your content directory on the fly, your changes
 will become visible immediately. To run it you need:
 
 * Python 2.7
-* [Flask](http://flask.pocoo.org/), [Jinja2](http://jinja.pocoo.org/) and
+* [Jinja2](http://jinja.pocoo.org/) and
   [Markdown](https://pypi.python.org/pypi/Markdown) modules (can be installed by
-  running `easy_install Flask Jinja2 Markdown` from the command line)
+  running `easy_install Jinja2 Markdown` from the command line)
 * A current copy of the
   [cms repository](https://github.com/adblockplus/cms/) (can be
   [downloaded as ZIP file](https://github.com/adblockplus/cms/archive/master.zip)
   or cloned via `git clone https://github.com/adblockplus/cms.git`)
 
+Optionally, the [Werkzeug](http://werkzeug.pocoo.org/) module can be installed
+as well, this will provide some developer features.
+
 Run the `runserver.py` script from your content directory, e.g.:
 
     python ../cms/runserver.py
 
 Alternatively, the content directory could also be specified as command line
 parameter of `runserver.py`. This will start a local web server on port 5000,
 e.g. the page the page `pages/example.md` will be accessible under
 `http://localhost:5000/en/example`.
 
 Note that the test server is inefficient and shouldn't be run in production.
@@ skipping 209 matching lines @@
 filter is invoked. For more information on Jinja2 filters see
 [official documentation](http://jinja.pocoo.org/docs/dev/api/#writing-filters).
 
 ### Custom functions and variables ###
 
 The `globals` directory can define custom Jinja2 globals which will be available
 in all Jinja2 templates. Typically, this is used for custom functions. The file
 name should match the name of the function or variable to be defined, and export
 a variable with that name. E.g. `globals/myfunction.py` can define a function
 called `myfunction` that will become available to all Jinja2 templates.