diff --git a/source/img/TrayWithPanel.png b/source/img/TrayWithPanel.png
new file mode 100644
index 0000000..b92e8c7
Binary files /dev/null and b/source/img/TrayWithPanel.png differ
diff --git a/source/index.rst b/source/index.rst
index 54862ac..df5e0a6 100644
--- a/source/index.rst
+++ b/source/index.rst
@@ -1,87 +1,88 @@
 .. KDE HIG documentation master file, created by
    sphinx-quickstart on Tue Feb  6 13:29:47 2018.
    You can adapt this file completely to your liking, but it should at least
    contain the root `toctree` directive.
 
 KDE Human Interface Guidelines
 ==============================
 
 .. toctree::
    :titlesonly:
    :hidden:
 
    introduction/index
    layout/index
    style/index
    components/index
    patterns/command/index
    patterns/content/index
    patterns/navigation/index
+   plattform/index
    resources/about
    resources/contribute
    resources/glossary
 
 
 .. Indices and tables
    ==================
 
    * :ref:`genindex`
    * :ref:`modindex`
    * :ref:`search`
 
 The KDE Human Interface Guidelines (HIG) offer designers and developers a set of recommendations for producing beautiful, usable, and consistent user interfaces
 for convergent desktop and mobile applications and workspace widgets. Their aim
 is to improve the experience for users by making application and widget
 interfaces more consistent and hence more intuitive and learnable.
 
 .. figure:: /img/HIGDesignVisionFullBleed.png
    :scale: 50 %
    :alt: Different DPIs on desktop and mobile
 
    ''Simple by default, powerful when needed.''
 
 
 Design Vision
 -------------
 KDE's design vision focuses on two attributes of KDE software that connect its
 future to its history:
 
 -  **Simple by default** - Simple and inviting. KDE software is pleasant 
    to experience and easy to use.
 -  **Powerful when needed** - Power and flexibility. KDE software allows 
    users to be effortlessly creative and efficiently productive.
 
 Design Principles
 -----------------
 The following design principles are used in support of the Design Vision.
 
 -  **Simple by default**
 
    -  *Make it easy to focus on what matters.* - Remove or minimize elements
       not crucial to the primary or main task. Use spacing to keep things
       organized. Use color to draw attention. Reveal additional information or
       optional functions only when needed.
    -  *I know how to do that!* - Make things easier to learn by reusing design
       patterns from other applications. Other applications that use good design
       are a precedent to follow.
    -  *Do the heavy lifting for me.* - Make complex tasks simple. Make novices
       feel like experts. Create ways in which your users can naturally feel
       empowered by your software.
 
 -  **Powerful when needed**
 
    -  *Solve a problem.* - Identify and make very clear to the user what need is
       addressed and how.
    -  *Always in control.* - It should always be clear what can be done, what is
       currently happening, and what has just happened. The user should never
       feel at the mercy of the tool. Give the user the final say.
    -  *Be flexible.* - Provide sensible defaults but consider optional
       functionality and customization options that do not interfere with the
       primary task.
 
 .. note::
     Note: KDE encourages developing and designing for customization, while
     providing good default settings. Integrating into other desktop environments
     is also a virtue, but ultimately we aim for perfection within our own Plasma
     desktop environment with the default themes and settings. This aim should
     not be compromised.
diff --git a/source/plattform/index.rst b/source/plattform/index.rst
new file mode 100644
index 0000000..7bbca50
--- /dev/null
+++ b/source/plattform/index.rst
@@ -0,0 +1,13 @@
+Plattform
+=========
+
+.. toctree::
+   :titlesonly:
+   :hidden:
+
+   tray
+
+This is an overview of how to integrate your application into the 
+:doc:`plasma workspaces </introduction/architecture>`.
+
+* :doc:`tray`
diff --git a/source/plattform/tray.rst b/source/plattform/tray.rst
new file mode 100644
index 0000000..6cc36ba
--- /dev/null
+++ b/source/plattform/tray.rst
@@ -0,0 +1,43 @@
+System Tray Icon
+================
+
+The system tray provides quick access to functionality integrated into the 
+workspace that’s both highly visible to the user and frequently changed, like 
+enabling/disabling WiFi and Bluetooth, or whether or not to show notifications.
+See :doc:`architecture </introduction/architecture>` for an overview of plasma 
+workspace components.
+
+Examples
+--------
+
+.. figure:: /img/TrayWithPanel.png
+   :alt: 
+   
+   Tray icons with an open volume control panel.
+
+Guidelines
+----------
+
+Is this the right control
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+An application should only add an icon to the System Tray if the 
+user needs to frequently access the application, or if the user is intrested in 
+status changes within the application.
+
+Behavior
+~~~~~~~~
+
+-  On left click, open the application itself, or a panel that allows quick 
+   access to common features.
+-  On right click, open a 
+   :doc:`context menu </components/navigation/contextmenu>`.
+-  For application like media players, enable the user to change the volume 
+   while scrolling over the icon.
+
+
+Appearance
+~~~~~~~~~~
+
+Use a :doc:`monochrome, Shade Black, icon </style/icon>` and use color only to 
+communicate state.