From 45e07ccc25b1216189685154a5420d327e0c086c Mon Sep 17 00:00:00 2001
From: Carsten Heidmann <carsten@heidmann.info>
Date: Mon, 3 Aug 2020 11:47:05 +0200
Subject: [PATCH] add some bulletpoints about the functionality of the
 technical platform/cloud access layer

---
 cloud-platform.md | 21 ++++++++++++---------
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/cloud-platform.md b/cloud-platform.md
index edcb77282..b3d9097d3 100644
--- a/cloud-platform.md
+++ b/cloud-platform.md
@@ -16,20 +16,23 @@ The upcoming Helmholtz Cloud will initially consist of approximately 20 of 25 se
 It is the purpose of HIFIS to allow a common, harmonized access to Helmholtz Cloud services via 
 a single portal -- the Cloud Access Layer: 
 and Single-Sign-On (SSO). 
-The initial set of services as well as the first version of the access layer is scheduled to be available by end of 2020. 
+The initial set of services as well as the first version of the access layer is scheduled to be available by the end of 2020.
 
 [**See also our roadmap**](roadmap).
 
 #### What are the plans for the Cloud Access Layer?
-The initial version of the Cloud Access Layer is planned to be kept simple but already allow for one of the most important features, the single-sign on funcionality.
-* one
-* two
-* three
+The initial version of the Cloud Access Layer is planned to be kept simple while at the same time incorporating one of the most important features, the single-sign on functionality. Further functionality of the first version includes
+* list of services
+* detail view for services
+* possibility to access a service via a link
+* indication of service status
 
-Later versions may contain...
-* four
-* five
-* six
+Later versions will contain more enhanced features like
+* personal workspace with overview about the personal set of services
+* possibility to request more specific setup of services
+* creation of meta services, e.g. combination of JupyterLab with HPC resources and a storage service
+
+If you have suggestions about additional use cases and functionality, please feel free to contact us. We appreciate all input from the user community!
 
 ## Contact us:
 `contact-at-hifis.net`
-- 
GitLab