diff --git a/source/conf.py b/source/conf.py
index 520cfb4f..ac718c1f 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -1,436 +1,438 @@
 # -*- coding: utf-8 -*-
 #
 # Kolab Groupware documentation build configuration file, created by
 # sphinx-quickstart on Tue Jul 16 12:32:13 2013.
 #
 # This file is execfile()d with the current directory set to its containing dir.
 #
 # Note that not all possible configuration values are present in this
 # autogenerated file.
 #
 # All configuration values have a default; values that are commented out
 # serve to show the default.
 
 import sys, os, glob, imp
 
 # If extensions (or modules to document with autodoc) are in another directory,
 # add these directories to sys.path here. If the directory is relative to the
 # documentation root, use os.path.abspath to make it absolute, like shown here.
 thisdir = os.path.dirname(os.path.abspath(__file__))
 extdir = os.path.abspath(os.path.join(thisdir, '..', 'ext'))
 
 sys.path = [
         extdir
     ] + sys.path
 
 # -- General configuration -----------------------------------------------------
 
 # If your documentation needs a minimal Sphinx version, state it here.
 #needs_sphinx = '1.0'
 
 # Add any Sphinx extension module names here, as strings. They can be extensions
 # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
 extensions = [
         'sphinx.ext.autodoc',
         'sphinx.ext.extlinks',
         #'sphinx.ext.mathjax',
         'sphinx.ext.todo',
         'sphinx.ext.graphviz',
         'sphinx.ext.ifconfig',
         'kolab.fancyfigure',
         #'kolab.phabricator',
     ]
 
 # fancybox extension config
 fancybox_config = {
     'helpers': {
         'title': { 'type': 'inside' }
     }
 }
 
 # Add any paths that contain templates here, relative to this directory.
 templates_path = ['_templates']
 
 # The suffix of source filenames.
 source_suffix = '.rst'
 
 # The encoding of source files.
 #source_encoding = 'utf-8-sig'
 
 # The master toctree document.
 master_doc = 'index'
 
 # General information about the project.
 project = u'Kolab'
 
 import datetime
 copyright = u'2010-%s, Kolab Systems AG' % (datetime.datetime.strftime(datetime.datetime.utcnow(), '%Y'))
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
 version = '16'
 # The full version, including alpha/beta/rc tags.
 
 #import subprocess
 #p1 = subprocess.Popen(['git', 'log', '--oneline'], stdout=subprocess.PIPE)
 #p2 = subprocess.Popen(['wc', '-l'], stdin=p1.stdout, stdout=subprocess.PIPE)
 #p1.stdout.close()
 #(count, errors) = p2.communicate(p1.stdout)
 #release = '%s (%s)' % (version, count)
 release = ''
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
 language = None
 
 # If true, a document’s text domain is its docname if it is a top-level project file
 # and its very base directory otherwise.
 # By default, the document markup/code.rst ends up in the markup text domain.
 # With this option set to False, it is markup/code.
 gettext_compact=False
 
 locale_dirs = ['../locale/']
 
 # There are two options for replacing |today|: either, you set today to some
 # non-false value, then it is used:
 #today = ''
 # Else, today_fmt is used as the format for a strftime call.
 #today_fmt = '%B %d, %Y'
 
 # List of patterns, relative to source directory, that match files and
 # directories to ignore when looking for source files.
 exclude_patterns = [
         'about/.template/*',
         'webmail-user-guide/roundcubemail-plugins-kolab/*'
     ]
 
 # The reST default role (used for this markup: `text`) to use for all documents.
 #default_role = None
 
 # If true, '()' will be appended to :func: etc. cross-reference text.
 #add_function_parentheses = True
 
 # If true, the current module name will be prepended to all description
 # unit titles (such as .. function::).
 #add_module_names = True
 
 # If true, sectionauthor and moduleauthor directives will be shown in the
 # output. They are ignored by default.
 show_authors = True
 
 # The name of the Pygments (syntax highlighting) style to use.
 pygments_style = 'sphinx'
 
 # A list of ignored prefixes for module index sorting.
 #modindex_common_prefix = []
 
 
 # -- Options for HTML output ---------------------------------------------------
 #import sphinx_rtd_theme
 #html_theme = "sphinx_rtd_theme"
 #html_theme_path = [sphinx_rtd_theme.get_html_theme_path()]
 
 html_theme = 'sphinxdoc'
 html_theme_path = ['themes']
 
 # The name for this set of Sphinx documents.  If None, it defaults to
 # "<project> v<release> documentation".
 html_title = 'Kolab Groupware documentation'
 
 # A shorter title for the navigation bar.  Default is the same as html_title.
 html_short_title = 'Kolab documentation'
 
 # The name of an image file (relative to this directory) to place at the top
 # of the sidebar.
 #html_logo = None
 
 # The name of an image file (within the static path) to use as favicon of the
 # docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
 # pixels large.
 #html_favicon = None
 
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
 html_static_path = ['_static']
 
 # If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
 # using the given strftime format.
 html_last_updated_fmt = '%b %d, %Y'
 
 # If true, SmartyPants will be used to convert quotes and dashes to
 # typographically correct entities.
 #html_use_smartypants = True
 
 # Custom sidebar templates, maps document names to template names.
 #html_sidebars = {}
 
 # Additional templates that should be rendered to pages, maps page names to
 # template names.
 #html_additional_pages = {}
 
 # If false, no module index is generated.
 #html_domain_indices = True
 
 # If false, no index is generated.
 #html_use_index = True
 
 # If true, the index is split into individual pages for each letter.
 #html_split_index = False
 
 # If true, links to the reST sources are added to the pages.
 #html_show_sourcelink = True
 
 # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
 #html_show_sphinx = True
 
 # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
 #html_show_copyright = True
 
 # If true, an OpenSearch description file will be output, and all pages will
 # contain a <link> tag referring to it.  The value of this option must be the
 # base URL from which the finished HTML is served.
 #html_use_opensearch = ''
 
 # This is the file name suffix for HTML files (e.g. ".xhtml").
 #html_file_suffix = None
 
 # Output file base name for HTML help builder.
 htmlhelp_basename = 'KolabGroupwaredoc'
 
 
 # -- Options for LaTeX output --------------------------------------------------
 
 latex_elements = {
 # The paper size ('letterpaper' or 'a4paper').
 #'papersize': 'letterpaper',
 
 # The font size ('10pt', '11pt' or '12pt').
 #'pointsize': '10pt',
 
 # Additional stuff for the LaTeX preamble.
 #'preamble': '',
 }
 
 # Grouping the document tree into LaTeX files. List of tuples
 # (source start file, target name, title, author, documentclass [howto/manual]).
 latex_documents = [
   ('index', 'KolabGroupware.tex', u'Kolab Groupware Documentation',
    u'Jeroen van Meeuwen', 'manual'),
 ]
 
 # The name of an image file (relative to this directory) to place at the top of
 # the title page.
 #latex_logo = None
 
 # For "manual" documents, if this is true, then toplevel headings are parts,
 # not chapters.
 #latex_use_parts = False
 
 # If true, show page references after internal links.
 #latex_show_pagerefs = False
 
 # If true, show URL addresses after external links.
 #latex_show_urls = False
 
 # Documents to append as an appendix to all manuals.
 #latex_appendices = []
 
 # If false, no module index is generated.
 #latex_domain_indices = True
 
 
 # -- Options for manual page output --------------------------------------------
 
 # One entry per manual page. List of tuples
 # (source start file, name, description, authors, manual section).
 man_pages = [
     ('index', 'kolabgroupware', u'Kolab Groupware Documentation',
      [u'Jeroen van Meeuwen'], 1)
 ]
 
 # If true, show URL addresses after external links.
 #man_show_urls = False
 
 
 # -- Options for Texinfo output ------------------------------------------------
 
 # Grouping the document tree into Texinfo files. List of tuples
 # (source start file, target name, title, author,
 #  dir menu entry, description, category)
 texinfo_documents = [
   ('index', 'KolabGroupware', u'Kolab Groupware Documentation',
    u'Jeroen van Meeuwen', 'KolabGroupware', 'One line description of project.',
    'Miscellaneous'),
 ]
 
 # Documents to append as an appendix to all manuals.
 #texinfo_appendices = []
 
 # If false, no module index is generated.
 #texinfo_domain_indices = True
 
 # How to display URL addresses: 'footnote', 'no', or 'inline'.
 #texinfo_show_urls = 'footnote'
 
 
 # -- Options for Epub output ---------------------------------------------------
 
 # Bibliographic Dublin Core info.
 epub_title = u'Kolab Groupware'
 epub_author = u'Jeroen van Meeuwen'
 epub_publisher = u'Jeroen van Meeuwen'
-epub_copyright = u'2013, Jeroen van Meeuwen'
+epub_copyright = u'2013-2016, Jeroen van Meeuwen'
 
 # The language of the text. It defaults to the language option
 # or en if the language is not set.
 #epub_language = ''
 
 # The scheme of the identifier. Typical schemes are ISBN or URL.
 #epub_scheme = ''
 
 # The unique identifier of the text. This can be a ISBN number
 # or the project homepage.
 #epub_identifier = ''
 
 # A unique identification for the text.
 #epub_uid = ''
 
 # A tuple containing the cover image and cover page html template filenames.
 #epub_cover = ()
 
 # HTML files that should be inserted before the pages created by sphinx.
 # The format is a list of tuples containing the path and title.
 #epub_pre_files = []
 
 # HTML files shat should be inserted after the pages created by sphinx.
 # The format is a list of tuples containing the path and title.
 #epub_post_files = []
 
 # A list of files that should not be packed into the epub file.
 #epub_exclude_files = []
 
 # The depth of the table of contents in toc.ncx.
 #epub_tocdepth = 3
 
 # Allow duplicate toc entries.
 #epub_tocdup = True
 
 todo_include_todos = True
 
 # -- Load variables for client configuration docs -----------------------------
 
 variables = {}
 default_tags = []
 custom_tags = False
 
 config_files = glob.glob('./*/conf.py')
 
 if os.path.exists('./conf.local.py'):
     config_files.append(os.path.relpath('./conf.local.py'))
 
 # collect variables from submodule configs
 for pathname in config_files:
     try:
         conf = imp.load_source('conf', pathname)
         if hasattr(conf, 'variables'):
             variables.update(conf.variables)
         if hasattr(conf, 'tags'):
             custom_tags = True
             for tag in conf.tags:
                 tags.add(tag)
         if hasattr(conf, 'module_tags'):
             default_tags += conf.module_tags
         if hasattr(conf, 'extensions'):
             extensions += conf.extensions
         # TODO: merge other config options like rst_prolog, rst_epilog, etc.
     except Exception, e:
         print "Failed to open config file", pathname
         print e
 
 # add default tags if no custom ones defined
 if not custom_tags:
     for tag in default_tags:
         tags.add(tag)
 
 # add variables as substitutions to the head of each page
 rst_prolog = ""
 for var, repl in variables.items():
     rst_prolog += "    .. |%s| replace:: %s\n" % (var, repl)
     rst_prolog += "    .. |**%s**| replace:: **%s**\n" % (var, repl)
 
 
 # forward variables for substitutions in fancyfigures
 fancyfigure_variables = variables
 
 extlinks = {
         'rfc': ('http://tools.ietf.org/html/rfc%s', 'RFC '),
         'mock': ('https://git.kolab.org/T%s', 'Mock #'),
         'task': ('https://git.kolab.org/T%s', 'Task #'),
     }
 
 rst_prolog += """
 .. _Architecture & Design: https://git.kolab.org/tag/architecture_design/
 .. _bugzilla: https://issues.kolab.org/
 .. _current sprint: https://git.kolab.org/tag/sprint_current/
 .. _next sprint: https://git.kolab.org/tag/sprint_next/
 .. _DAVDroid: http://davdroid.bitfire.at/what-is-davdroid
 .. _DAVDroid from Google Play: https://play.google.com/store/apps/details?id=at.bitfire.davdroid
 .. _Differential: https://git.kolab.org/differential/
 .. _Diffusion: https://git.kolab.org/diffusion/
 .. _Drydock: https://git.kolab.org/drydock/
 .. _EPEL for Enterprise Linux 6: http://download.fedoraproject.org/pub/epel/6/x86_64/repoview/epel-release.html
 .. _EPEL for Enterprise Linux 7: http://download.fedoraproject.org/pub/epel/7/x86_64/repoview/epel-release.html
 .. _F-Droid app repository: https://f-droid.org/repository/browse/?fdid=at.bitfire.davdroid
 .. _Harbormaster: https://git.kolab.org/harbormaster/
 .. _Herald: https://git.kolab.org/herald/
 .. _Kolab Systems AG: https://kolabsystems.com
 .. _Maniphest: https://git.kolab.org/maniphest/
 .. _Phabricator: https://git.kolab.org/
 .. _Process Managers: https://git.kolab.org/tag/process_managers/
 .. _Product Owners: https://git.kolab.org/tag/product_owners/
 .. _Projects: https://git.kolab.org/projects/
 .. _Quality Assurance: https://git.kolab.org/tag/quality_assurance/
 .. _Report a bug: https://git.kolab.org/maniphest/task/edit/form/9/
 .. _Scrum: http://en.wikipedia.org/wiki/Scrum_%28software_development%29
 .. _Scrum Masters: https://git.kolab.org/tag/process_managers/
 .. _Sprints: https://git.kolab.org/project/sprint/
 .. _Why Your System Should Have a Proper FQDN: https://kanarip.wordpress.com/2016/02/04/why-your-system-requires-a-proper-fqdn/
 """
 
 rst_prolog += """
 .. role:: blue
 .. role:: gray
 .. role:: green
 .. role:: orange
 .. role:: red
 """
 
 #
 # Releases
 #
 rst_prolog += """
 .. |Winterfell| replace:: :orange:`Winterfell`
 .. |K16| replace:: :orange:`Kolab 16`
 .. |KE14| replace:: :orange:`Kolab Enterprise 14`
 .. |KE13| replace:: :orange:`Kolab Enterprise 13`
+.. |ReleaseProduction| replace:: :orange:`Kolab Enterprise 14`
+.. |ReleaseCurrent| replace:: :orange:`Kolab 16.0`
 """
 
 #
 # Target platforms
 #
 rst_prolog += """
 .. |maipo| replace:: :gray:`Maipo`
 .. |santiago| replace:: :gray:`Santiago`
 """
 
 #
 # Packages
 #
 rst_prolog += """
 .. |roundcubemail| replace:: :blue:`roundcubemail`
 .. |roundcubemail-plugins-kolab| replace:: :blue:`roundcubemail-plugins-kolab`
 """
diff --git a/source/installation-guide/index.rst b/source/installation-guide/index.rst
index 149c3f6d..2128a29a 100644
--- a/source/installation-guide/index.rst
+++ b/source/installation-guide/index.rst
@@ -1,63 +1,84 @@
 .. _installation-guide:
 
 ==================
 Installation Guide
 ==================
 
 Before you install Kolab Groupware
 ==================================
 
 .. toctree::
     :maxdepth: 2
 
     preparing-the-system
     overview
 
+Current Release
+===============
+
+The most recent version of Kolab is |ReleaseCurrent|.
+
+This is a preview release appropriate for pilot projects, testing, and development. 
+It is not recommended for production deployments at this time. You can help |K16| reach
+production readiness by using |ReleaseCurrent|, keeping it up to date, and
+`reporting issues <../contributor-guide/bug-reporting-casual.html>`_ you may encounter.
+
+The current recommended version for production deployment is |ReleaseProduction|.
+
+The release of Kolab 16.1 will occur in Q2 of 2016, at which point Kolab 16 will be
+upgraded to "gold" status and become the recomended release for production installations.
+Subscription-based support from `Kolab Systems AG`_ will also be available for Kolab 16.1.
+
+For subscription-based support of Kolab installations, please visit
+`Kolab Enterprise <https://kolabenterprise.com/>`_,
+which offers services for all sizes of business, government, NGO, and educational
+organizations. You can read about the advantages of Kolab subscription here: :ref:`advantages-of-subscription`
+
 Installing the Kolab Groupware Solution
 =======================================
 
-Install the latest stable version of the Kolab Groupware solution for either
+Install the latest version of the Kolab Groupware solution for one
 of the following platforms:
 
 .. toctree::
     :maxdepth: 1
 
     centos-7
     rhel-7
 
 If your personal favorite is not listed, please read the
 "`Support Your Distribution, or else ... <https://kanarip.wordpress.com/2016/02/03/support-your-distribution-or-else/>`_"
 blog article, and follow the instructions.
 
 .. rubric:: Bleeding Edge
 
 .. toctree::
     :maxdepth: 1
 
     winterfell/index
 
 .. rubric:: Older versions of Kolab Groupware
 
 .. toctree::
     :maxdepth: 1
 
     kolab-14/index
     kolab-13/index
 
 Installing the Kolab Desktop Client
 ===================================
 
 The Kolab Desktop Client is maintained by community volunteers
 in their spare time.
 
 It has a fast release cycle and is in steady movement. If things do not
 work as expected, please consider contributing.
 
 .. toctree::
     :maxdepth: 1
 
     kontact-fedora
     kontact-centos
     kontact-windows
     kontact-ubuntu
 
diff --git a/source/introduction/advantages-of-subscription.rst b/source/introduction/advantages-of-subscription.rst
new file mode 100644
index 00000000..7d88a9d3
--- /dev/null
+++ b/source/introduction/advantages-of-subscription.rst
@@ -0,0 +1,75 @@
+.. _advantages-of-subscription:
+
+=============================================
+The Advantages of Having A Kolab Subscription
+=============================================
+
+Subscription-based support is available for Kolab from `Kolab Systems AG`_.
+Kolab Systems is the primary developer and maintainer of Kolab, and provides enterprise-level
+design, deployment, development, and support for Kolab installations to public and private organizations
+of all sizes. Subscriptions are offered on a per-seat basis, and provide subscribers with distinct advantages.
+
+The Benefits of Having a Kolab Subscription
+===========================================
+
+Subscriptions are an excellent way to support the ongoing development of Kolab, as proceeds go directly
+into infrastructure Kolab development relies on as well as the employment of the core
+Kolab technical team.
+
+But the most compelling aspect of subscriptions are the exclusive benefits that come with them. These
+advantages reliably lower the cost of ownership and increase overall reliability for the customer, including:
+
+1. Access to rolling security and bugfix updates
+
+    Non-subscribers will need to update their Kolab installations annually to get the last year's worth
+    of fixes and improvements. Subscribers, on the other hand, benefit immediately from fixes as they become
+    available between releases. Along with releases, all updates are cryptographically signed with Kolab
+    System's private GPG key allowing verification of the binaries.
+
+2. Five years of extended support for each release
+
+    This is vitally important for production deployments, as significant changes may occur from one annual
+    release to the next. Performing “update the world” upgrades to production systems every year can be a 
+    significant task and induce risk, both of which incur costs. Subscribers, on the other hand, can upgrade
+    when it fits their interests best, secure in the knowledge that the version of Kolab they are currently
+    running will be supported for years to come in that configuration.
+
+    And of course, all released packages are kept in perpetuity, which grants additional management flexibility,
+    such as being able to downgrade specific components via the package manager if needed.
+
+3. Professional support from Kolab Systems
+
+    If problems are encountered during setup, deployment, 
+    migration or production usage, you can access the expertise of Kolab Systems' technical support team 
+    through your subscription privileges, such as access to our internal ticketing system. Subscribers also 
+    receive greater priority in the community support forums and other communication channels Kolab 
+    Systems maintains.
+
+4. Professional services
+
+    Kolab Systems' “Tiger Team” of specialists may be retained by those with active Kolab subscriptions.
+    Services which are available on a per-project basis include deployment planning and management, infrastructure
+    integration (e.g. with existing directory services, including Active Directory), custom development, and
+    white-labeling. For deployments with special requirements or that need to scale reliably, this expertise in
+    high-availability, load-balancing, cluster/cloud deployment, and integration is invaluable.
+
+    Subscribers also have greater influence over where Kolab Systems focuses development resources for
+    upcoming releases in general.
+
+5. Access to optimized system packages
+
+    By default, Kolab uses the stock packages for PHP, Apache HTTPD, MariaDB, openSSL and others that come
+    with the base operating system. Kolab Systems engineers have made many improvements to the configuration and
+    builds of these packages that are available exclusively to subscribers.
+ 
+    These optimizations ensure, for instance, that Roundcube scales well and that encryption is set up in the most 
+    secure way possible for Kolab's needs. Every production environment benefits from this tuning and fitness work,
+    and is only available to Kolab subscribers.
+
+Have Questions or Comments?
+===========================
+
+We welcome feedback from our users, customers and partners. If you have any questions, concerns or 
+comments about the information in this briefing, please do not hesitate to contact us by email at 
+info@kolabsystems.com.
+
diff --git a/source/introduction/index.rst b/source/introduction/index.rst
index c6c19835..a1380d4a 100644
--- a/source/introduction/index.rst
+++ b/source/introduction/index.rst
@@ -1,21 +1,22 @@
 .. _introduction:
 
 ===============================
 Introduction to Kolab Groupware
 ===============================
 
 Welcome to Kolab Groupware!
 
 The community appreciates your interest in Kolab, since the Kolab
 community in turn has an interest in you -- but not in a stalker-like
 way of course.
 
 I expect you are reading this article to learn about Kolab Groupware,
 so please dive right in.
 
 .. toctree::
     :maxdepth: 1
 
     what-is-kolab-groupware
     do-it-yourself-or-kolab
     what-is-the-recommended-distribution
+    advantages-of-subscription