diff --git a/_config.yml b/_config.yml
index f3c49e12dcb786ac094ff116f18893906e813fb5..62b964e4411d89dad8d1ef7f414cb2178c9643b1 100644
--- a/_config.yml
+++ b/_config.yml
@@ -1,9 +1,9 @@
# Global website configuration
baseurl: ""
-url: https://software.hifis.net
+url: https://www.hifis.net
-title: "HIFIS Software"
+title: "HIFIS"
# Encoding needs to be UTF-8.
encoding: utf-8
@@ -32,16 +32,16 @@ defaults:
path: ""
type: "events"
values:
- author: "HIFIS Software"
+ author: "HIFIS"
-
scope:
path: ""
type: "posts"
values:
- author: "HIFIS Software"
+ author: "HIFIS"
gitlab:
- project_url: https://gitlab.hzdr.de/hifis/software.hifis.net
+ project_url: https://gitlab.hzdr.de/hifis/hifis.net
contact_mail: hifis-help@hzdr.de
helpdesk: hifis-help.hzdr.de
@@ -63,7 +63,7 @@ plugins:
- 'jekyll-sitemap'
paginate: 5
-paginate_path: '/blog/page:num/'
+paginate_path: '/news/page:num/'
markdown: kramdown
kramdown:
@@ -93,7 +93,7 @@ collections:
feed:
collections:
posts:
- path: "/feed/blog.xml"
+ path: "/feed/news.xml"
events:
path: "/feed/events.xml"
excerpt_only: true
diff --git a/_data/hifis_team.yml b/_data/hifis_team.yml
index f523fc4109b3945bdade4c65a0f6835a68a10d28..2561955d59f524b7b2017561601284c5964482a7 100644
--- a/_data/hifis_team.yml
+++ b/_data/hifis_team.yml
@@ -31,11 +31,8 @@
# link_as: https://www.facebook.com/my-profile-url
# show_as: "My Profile"
-- id: example
- name: "Example, Edgar"
+- id: jandt
+ name: "Jandt, Uwe"
location:
- campus: hzdr
- office: "Buildeing A, Room 1"
- position: "Chief of Example Dpt."
- rank: 0
+ campus: desy
associate: false
diff --git a/_data/navigation.yml b/_data/navigation.yml
index 378d68de20701041315b2159104fa8c9bd8ea04b..68832bcd1369f647ec2c4184586f1d15fc6c9e02 100644
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -12,10 +12,10 @@
header:
- title: News
- url: blog/
+ url: news/
- title: Services
- url: "/"
+ url: "services/"
- title: Mission
url: "/"
diff --git a/_includes/cards/post_card_image.html b/_includes/cards/post_card_image.html
new file mode 100644
index 0000000000000000000000000000000000000000..25a0c4e1c0ce498f73a15d53d6893c987f73d2db
--- /dev/null
+++ b/_includes/cards/post_card_image.html
@@ -0,0 +1,29 @@
+{%- comment -%}
+
+ This is a card displaying post metadata as well as the title image.
+ Parameters:
+ post: The post which sould be displayed on the card
+
+{%- endcomment -%}
+{%- if post.title_image == "default" %}
+{%- assign image = 'hifis_page_title_background.jpg'-%}
+{%- else -%}
+{%- assign image = post.title_image -%}
+{%- endif -%}
+{%- assign img_url = site.directory.large_images
+ | append: "phone/"
+ | append: image
+ | strip
+ | relative_url -%}
+<div class="card">
+ <a href="{{ include.post.url | relative_url }}">
+ <img class="card-img-top card-img-equal" src="{{ img_url }}" alt="Title image">
+ <div class="card-body">
+ <span class="badge badge-pill badge-secondary">
+ <i class="fas fa-calendar-day" aria-hidden="true"></i>
+ {{ include.post.data | date: "%d. %b. %y" }}
+ </span>
+ <h3 class="card-title">{{ include.post.title }}</h3>
+ </div>
+ </a>
+</div>
diff --git a/_includes/team_card_mini.html b/_includes/team_card_mini.html
index 29566243823c25dd8371be9c03579bfbea66795d..d99259aad42326a8738d904ddfcc860726bddf56 100644
--- a/_includes/team_card_mini.html
+++ b/_includes/team_card_mini.html
@@ -6,7 +6,7 @@
{% assign person = include.person %}
{% if person %}
<span class="team-card-mini">
- <a href="{{ person.id | prepend: 'members/' | relative_url }}">
+ <!-- a href="{{ person.id | prepend: 'members/' | relative_url }}" -->
{% if person.image %}
{% assign image-url = site.directory.images
| append: "members/"
@@ -17,7 +17,7 @@
{% endif %}
{% include team_card/name.html person=person %}
{% include team_card/team_member_associate.html person=person %}
- </a>
+ <!-- /a -->
</span>
{% else %}
<!--
diff --git a/_layouts/frontpage.html b/_layouts/frontpage.html
index 7e2980ebf7a9fb41c026bb0ee7c99e38022a2733..4c6b24541376ecd7ba37a6ef7e0cdf75941f0f23 100644
--- a/_layouts/frontpage.html
+++ b/_layouts/frontpage.html
@@ -25,7 +25,7 @@
{% include frontpage/post-card.html post = post %}
{% endfor %}
</div>
- <a href="{{ 'blog/' | relative_url }}" class="btn btn-outline-secondary">More</a>
+ <a href="{{ 'news/' | relative_url }}" class="btn btn-outline-secondary">More</a>
</section>
</div>
<div class="frontpage-mission-jumbotron">
diff --git a/_layouts/pagination.html b/_layouts/pagination.html
index 157333e068da9a4ef2d7f4a73c4ea5f887e6e7f8..39efaab9148e8b02d354498f4eea0c98c50f7711 100644
--- a/_layouts/pagination.html
+++ b/_layouts/pagination.html
@@ -29,7 +29,7 @@ title: HIFIS
<span> {{ page }} </span>
{% elsif page == 1 %}
<span>
- <a href="{{ 'blog/' | relative_url }}"> {{ page }} </a>
+ <a href="{{ 'news/' | relative_url }}"> {{ page }} </a>
</span>
{% else %}
<span>
@@ -51,7 +51,7 @@ title: HIFIS
{% endif %}
</div>
<div class="rss-posts-container grid-item">
- <a class="rss-posts-button" href="{{ '/feed/blog.xml' | relative_url }}"
+ <a class="rss-posts-button" href="{{ '/feed/news.xml' | relative_url }}"
title="subscribe to feed"
type="application/atom+xml"
download>
diff --git a/_posts/2020/03/2020-03-13-jsc-hpc-support-for-covid-19-research.md b/_posts/2020/03/2020-03-13-jsc-hpc-support-for-covid-19-research.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5e13230358d1ad55fe42ae61f073ac7e4867cfe
--- /dev/null
+++ b/_posts/2020/03/2020-03-13-jsc-hpc-support-for-covid-19-research.md
@@ -0,0 +1,19 @@
+---
+title: "JSC: HPC support for COVID-19 research"
+title_image: default
+data: 2020-03-13
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt:
+ The Jülich Supercomputing Center (JSC) offers computing time and support
+ on its HPC facilities for research on the COVID-19 virus.
+---
+
+{{ page.excerpt }}
+
+<a type="button" class="btn btn-outline-primary btn-lg" href="https://www.fz-juelich.de/SharedDocs/Meldungen/IAS/JSC/EN/2020/offer-covid-19.html">
+ <i class="fas fa-external-link-alt"></i> Read more
+</a>
diff --git a/_posts/2020/04/2020-04-06-hifis-support-folding-at-home.md b/_posts/2020/04/2020-04-06-hifis-support-folding-at-home.md
new file mode 100644
index 0000000000000000000000000000000000000000..a46f88a429682402c835ca57430434416c462321
--- /dev/null
+++ b/_posts/2020/04/2020-04-06-hifis-support-folding-at-home.md
@@ -0,0 +1,25 @@
+---
+title: "Folding@Home and research on SARS-CoV-2"
+title_image: default
+data: 2020-04-09
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt_separator: <!--more-->
+---
+
+The Helmholtz platform HIFIS, the HZDR and the Center for Advanced Systems
+Understanding (CASUS) support the world-wide project Folding@Home in
+developing an antibody based therapy to prevent a respiratory infection by
+the virus.
+<!--more-->
+For this, a significant portion of the high performance computing capacity is
+provided to assist in computing protein structures of the Corona virus. The
+detailed knowledge of such structures is decisive to develop a successful
+therapy.
+In a coordinated effort with the computing center of the
+Helmholtz-Zentrum Dresden - Rossendorf, free resources of the CASUS high
+performance computer and the HZDR high performance computer "Hemera" are being
+combined.
diff --git a/_posts/2020/04/2020-04-08-kit-supports-distributed-protein-computing-projects.md b/_posts/2020/04/2020-04-08-kit-supports-distributed-protein-computing-projects.md
new file mode 100644
index 0000000000000000000000000000000000000000..03f9f2447b72aefa9e528b9b02fbc54f41346411
--- /dev/null
+++ b/_posts/2020/04/2020-04-08-kit-supports-distributed-protein-computing-projects.md
@@ -0,0 +1,25 @@
+---
+title: "KIT supports distributed protein computing projects"
+title_image: default
+data: 2020-04-08
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt:
+ Since end of March, the Grid Computing Centre Karlsruhe and the HPC systems
+ of KIT support the distributed computing projects Folding@Home and Rosetta@home,
+ helping to improve the understanding of proteins, including those of SARS-CoV-2.
+---
+
+Since end of March, the
+[Grid Computing Centre Karlsruhe](https://www.gridka.de/cgi-bin/frame.pl?seite=/welcome.html)
+and the
+[HPC systems of KIT](https://www.scc.kit.edu/en/services/12055.php)
+support the distributed computing projects Folding@Home and Rosetta@home,
+helping to improve the understanding of proteins, including those of SARS-CoV-2.
+
+<a type="button" class="btn btn-outline-primary btn-lg" href="https://www.scc.kit.edu/en/aboutus/13531.php">
+ <i class="fas fa-external-link-alt"></i> Read more
+</a>
diff --git a/_posts/2020/04/2020-04-15-hifis-software-workshops-in-2020.md b/_posts/2020/04/2020-04-15-hifis-software-workshops-in-2020.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a17138ffe6db09e53c4cd9c8b8e4a375b87ebf6
--- /dev/null
+++ b/_posts/2020/04/2020-04-15-hifis-software-workshops-in-2020.md
@@ -0,0 +1,39 @@
+---
+title: "HIFIS Software Workshops in 2020"
+title_image: default
+data: 2020-04-15
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt:
+ "HIFIS workshop cluster in spring and autumn 2020: Basic Software Carpentry,
+ Introduction to GitLab and Bring Your Own Script. Specialized workshops
+ are being planned: Catch them all by keeping an eye on our events page!"
+---
+
+Several different software development trainings will be offered to researchers.
+
+- _Software Carpentry_ workshops introduce scientists to use- and powerful
+ tools: Shell, Python and R for effective and reproducible scientific
+ programming, and Git for version controlling your projects.
+- _Bring Your Own Script_ workshops
+ ([like on May 12th and 13th](https://software.hifis.net/events/2020/05/12/ready-script-for-publication))
+ will help you to make your code publication-ready:
+ Regardless of your preferred programming language, we will advise you on all
+ aspects of making your research software (re)usable for others,
+ e.g. how to add a license.
+- _GitLab for Software Development in Teams_ introduces advanced GitLab features:
+ GitLab’s project management, collaboration and automation features will help
+ software development teams to improve software quality and speed up their
+ release cycles.
+ Join us on
+ [June 9th and 10th](https://software.hifis.net/events/2020/06/09/GitLab-Software-Development-Teams)!
+
+The [HIFIS Software events](https://software.hifis.net/events) page provides
+your with more details and keeps you updated about future events.
+More specialized events outside this core curriculum —
+like an
+[Introduction to Snakemake](https://software.hifis.net/events/2019/12/11/snakemake-introduction-workshop) —
+are being planned, so best keep an eye on that page!
diff --git a/_posts/2020/05/2020-05-15-guidelines-for-chatting.md b/_posts/2020/05/2020-05-15-guidelines-for-chatting.md
new file mode 100644
index 0000000000000000000000000000000000000000..3725eb4a469830e543fe7794fea56466ae25ecaa
--- /dev/null
+++ b/_posts/2020/05/2020-05-15-guidelines-for-chatting.md
@@ -0,0 +1,167 @@
+---
+title: "Guidelines for Chatting"
+title_image: volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
+data: 2020-05-15
+authors:
+ - Martin Hammitzsch (GFZ)
+layout: blogpost
+categories:
+ - guidelines
+excerpt:
+redirect_from:
+ - services/chatting/index_ger.html
+ - services/chatting/index.html
+excerpt:
+ Whenever you choose and set up a chat system you should as well implement a
+ netiquette and best practices for you and your team members from the start.
+---
+
+## Scope
+We’re talking about _Slack_, _Mattermost_, _Matrix_, _Rocket Chat_, _Jabber_,
+_XMPP_, _ICQ_, and other services supporting direct communication with remote
+team members either at the same time or asynchronously.
+
+## Task
+You're responsible for leading a group of people who work distributed in a team.
+Besides email, chat can be a useful tool to coordinate your collaboration.
+
+## Situation
+You and your team cannot communicate directly with each other due to space or
+time constraints.
+Therefore you want to give your team a possibility to exchange information
+easily and without problems.
+In order for this exchange to be goal-oriented and fruitful,
+a suitable tool and a set of rules must be discussed and set up.
+
+## Challenge
+Everyone is invited to participate actively while following rules that have
+been negotiated and agreed upon by all team members thus enabling a smooth
+communication and avoiding misunderstandings.
+
+## Approach
+Whenever you choose and set up a chat system you should as well implement a
+netiquette and best practices for you and your team members from the start.
+
+## Options
+Below are a few suggestions that might make it into the set of rules for your
+team to make everyone feel comfortable and more productive when using the chat.
+
+- **Define the purpose**
+ Be clear what can be communicated via chat in your team.
+ Chat does not completely replace email, but helps sufficiently keeping your
+ email inbox organized and communication regarding specific issues or topics
+ better inline - with a chat tool.
+ For example, do not share bits and pieces by email, use the chat instead.
+
+- **Propose chat rooms**
+ Make sure to create different chat rooms for different topics in case your
+ team is involved in various activities and interests in different constellations.
+ However, avoid cluttered communication, e.g. originating from too many chat rooms.
+
+- **Offer space for socializing**
+ Besides topical chat rooms, offer a „town hall“ or “campfire†for off-topic
+ conversations.
+ Keep off-topic conversation appropriate for your professional setting and
+ limit the amount.
+ Also use it to chat with only three or five of the team, e.g. to find a time
+ to meet and to avoid the creation of additional chat rooms in any combination
+ possible.
+ Other team members will appreciate it to see that their peers are alive even
+ if the chat isn't something they are directly involved in.
+ You even may use it to send out a “ping†each morning to let others know
+ that they are not alone.
+
+- **Foster direct chat communication**
+ Beyond chat rooms with three or more team members you might foster direct
+ communication for asking and answering quick questions, sharing immediate
+ information, getting in touch to arrange voice or video calls at a later
+ time, or clarifying and discussing facts in a lively back and forth
+ communication without phoning each other.
+
+- **Define response times and urgency**
+ Clarify what the acceptable and expected response time is.
+ A direct chat might be urgent in some cases whereas a chat room most likely
+ is not.
+ So make clear statements and agreements on the response time to be expected -
+ if there are any to be expected.
+
+- **Set a status message**
+ Include details in your chat profile you want others to see thus giving them
+ more information about what you are up to, where you are and whether you
+ are available.
+ It helps others to identify if you cannot reply quickly, e.g. when attending
+ a meeting, or if you are not available in person, e.g. when being in
+ home office.
+ Also, be aware of the status messages of your peers.
+
+- **Respect the working methods of your peers**
+ end chats only to relevant people or to the relevant room.
+ Use chats only for short conversations so you do not take too much time away
+ from the people on the other end. Don’t be distracting -
+ if a status message indicates that your peer is away or busy you may
+ postpone the communication or send an email instead.
+ Also, take care to get not distracted by chats from your work you currently
+ focus at - find a routine to come around from time to time.
+
+- **Stay structured and organized**
+ Stay on topic and keep the conversation short.
+ Send consolidated messages, avoid sending several messages in quick succession.
+ Reply only to messages directed at you or reply if you are able to contribute
+ meaningfully.
+ Use threads to organize discussions by replying to a specific message,
+ if possible.
+
+- **Be friendly and inviting**
+ Start with a short greeting or seek permission.
+ Reply quickly or communicate that you cannot, e.g. by using a status message.
+ End conversations with a short closing and a thank you, when appropriate.
+
+- **Be sensitive**
+ Be particularly cautious about joking, humorous comments, and sharing
+ personal information - things may come across differently than expected
+ when not talking in person.
+ Also, never write anything you wouldn’t say aloud.
+
+- **Be aware of the limitations of written communication**
+ Never send bad news via chat or negative feedback.
+ Do not use chat for emotionally loaded topics.
+ A face-to-face communication or a talk in person includes nonverbal behaviors -
+ e.g. the gestures and eye contact you make, your posture, and your tone
+ and pitch of voice.
+ These wordless signals cannot be given and received in a chat and limit the
+ communication.
+ Emojis were introduced to help in this regard for private chats but should
+ be used wisely in professional chat communications.
+
+- **Be mindful of spelling, formatting, and other mechanics**
+ Check your wording and spelling and possible mistakes produced by autocorrection.
+ Be appropriate with emojis, all caps and exclamation marks.
+ Be careful with abbreviations and communicate clearly - use enough words to make
+ your message understandable to all chat participants and avoid slang.
+
+- **Use encryption for sensitive and personal information**
+ Keep an eye on data privacy and protection.
+ Never share sensitive or confidential information in unsecured chats or
+ infrastructure of which you are not sure it is operated within your legal
+ constraints, e.g. outside the EU.
+ If there is a possibility that you share sensitive or personal information
+ via chat - the probability is high if you do more than share cat videos -
+ make sure that you use end-to-end encryption for your chat,
+ or point-to-point, if it is a requirement that your infrastructure
+ provider can listen in.
+ Many clients have plugins for encryption with PGP, for direct communication
+ between two users with OTR, or for group chat with OMEMO.
+
+- **Stick with other communication channels**
+ If communication started through a different channel than chat, stick with it!
+ When changing communication channels in-between then a communication breaks
+ apart and others will be lost.
+ For example, don't change meeting times or venues in a chat, use the medium
+ originally used to set up the meeting.
+
+<div class="alert alert-success">
+ <h2 id="contact-us"><i class="fas fa-info-circle"></i> Comments or Suggestions?</h2>
+ <p>
+ Feel free to <a href="{% link contact.md %}">contact us</a>.
+ </p>
+</div>
diff --git a/_posts/2020/05/2020-05-15-guidelines-for-video-conferencing.md b/_posts/2020/05/2020-05-15-guidelines-for-video-conferencing.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4d40ac0253c543538e70df75c40f052421b8b31
--- /dev/null
+++ b/_posts/2020/05/2020-05-15-guidelines-for-video-conferencing.md
@@ -0,0 +1,281 @@
+---
+title: "Guidelines for Video Conferencing"
+title_image: chris-montgomery-smgTvepind4-unsplash.jpg
+data: 2020-05-15
+authors:
+ - Martin Hammitzsch (GFZ)
+layout: blogpost
+categories:
+ - guidelines
+excerpt:
+redirect_from:
+ - services/video_conferencing/index_ger.html
+ - services/video_conferencing/index.html
+excerpt:
+ You are the one in charge of making this call a success by means of that
+ everyone is happy with a smooth performance of the call itself and is
+ satisfied with the outcome, preferably actionable results having a practical
+ value.
+ Using a video conferencing tool shall not hamper an effective meeting and
+ should be used to make the virtual get-together as efficient as possible when
+ participants are not at the same place.
+---
+
+## Scope
+We’re talking about _DFNconf_, _Skype_, _Google Hangouts_, _Microsoft Teams_,
+_Cisco WebEx_, _Adobe Connect_, _Zoom_, _Jitsi Meet_, _BlueJeans_,
+_GoToMeeting_, _StarLeaf_, _Lifesize_, _Fuze_ and other services that you may
+have heard of supporting online meetings.
+
+## Task
+You're either responsible for a team, a project, or any other measure - or you
+support someone who is.
+Regular and extraordinary meetings with the persons involved are part of your
+managerial routine to lead a group of individuals distributed across space and
+time.
+
+## Situation
+You are going to run a conference call with remote team members to get or keep
+things going - either by phone, or more likely, with a digital tool for video
+conferencing.
+Some participants may be in a hurry, may have other burning issues to take
+care of, or may have experience with unsatisfying virtual meetings.
+However, everyone has to coordinate with each other.
+
+## Challenge
+You are the one in charge of making this call a success by means of that
+everyone is happy with a smooth performance of the call itself and is
+satisfied with the outcome, preferably actionable results having a practical
+value.
+Using a video conferencing tool shall not hamper an effective meeting and
+should be used to make the virtual get-together as efficient as possible when
+participants are not at the same place.
+
+## Approach
+When you set-up an agenda, refer to a netiquette and best practices that covers
+a set of rules to make you and your team/group/colleagues feel comfortable and
+enable a productive environment in the meeting.
+
+## Options
+Below are a few suggestions that might make it into the set of your rules to
+make you feel comfortable in a virtual meeting, and the others too.
+
+### Equipment
+- **Use a headset or at least headphones or external speakers made for conferencing**
+ Using speakers close to your ears or speakers that are made for conferencing
+ avoid feedback of spoken words.
+
+- **Use an external microphone or an external camera paired with a room microphone**
+ Internal microphones and internal cameras, especially of older computers,
+ might be no fun for the other participants due to a limited quality of
+ recorded sound and video signals.
+
+- **Use a modern computer or mobile device**
+ Conferences tools, especially those supporting video, require hardware support
+ that often is underestimated.
+ Computers and mobile devices with modern technology are capable of handling
+ modern video conferences.
+ Older devices may lead to problems sooner or later.
+
+### Connection
+- **Use a high-speed Internet connection**
+ Preferably use a wired connection, stay close to a wifi device, or find a
+ fixed place with a reliable mobile network.
+ Avoid low-bandwidth connections shared with others streaming Netflix,
+ downloading files or video chatting at the same time.
+
+- **Close your VPN connection**
+ VPN connections route your communication through an additional transmission
+ node becoming a potential bottleneck when everyone is doing the same.
+ Disconnecting from VPN and similar connections reduces the risk of a
+ slowed down internet connection.
+
+- **Shut down any other programs connected to the network**
+ Normally many other tools run in the background that might interfere with
+ the bandwidth necessary to participate in a high-quality video conference.
+ So whenever you experience problems with the connection consider this option
+ too.
+
+- **Stop other devices streaming music or movies**
+ Tools on other devices may hamper your bandwidth, too,
+ when in use at the same time.
+ So close apps and programs for the time of the video conference even if
+ your kids don’t like it.
+
+### Conferencing tool
+- **Use an up-to-date browser or application**
+ Make sure to use a browser supported by the provider of the conferencing
+ service and double-check that updates are not too far behind.
+ Installing the application offered by the service provider may help,
+ too, to stay up-to-date.
+ Third party tools are an option but need a closer look since some of them
+ miss the required maintenance.
+
+- **Make yourself comfortable with the conferencing software**
+ Whether used in a browser or as an application, the conference tool of choice
+ might have a huge range of functionality, a very own behaviour, and
+ many settings. This needs to be understood.
+ So make yourself comfortable in advance to understand the behaviour and
+ turn-on/off functionality on-demand.
+
+- **Master relevant settings of your operating system**
+ Conference tools offer lots of functionality and configurations.
+ However, some of the important ones are anchored in operating systems such
+ as Microsoft Windows, Mac OS X or a Linux distribution. Specifically,
+ enabling and calibrating your microphone and speakers with the tools of your
+ operating system should become routine shortly before a virtual meeting.
+ A quick double-check testing the input level and volume might help to spot
+ problems, too, e.g. caused by blocking bluetooth connections.
+
+### Location
+- **Find a great location and working place**
+ Use, and reserve if necessary, a quiet location instead of a busy café,
+ the public transit, or the canteen.
+ It helps you to stay focused, to keep unexpected disturbances out of the
+ conference call, and to comfortably make use of working devices so that
+ following media presented and working at documents either alone or
+ collaboratively is fun.
+
+- **Prepare your location**
+ Close the doors and preferably windows too keep traffic and construction
+ noise, squeaky public transport and police sirens out of the conversation.
+ Keep dogs and other pets out of your room to avoid unexpected disturbing
+ sounds.
+
+- **Set-up your camera**
+ Place the camera close to the screen or at least ensure that you look at the
+ camera, not the screen, when talking.
+ Provide space between your body and the background and reduce back-lightning
+ by turning your computer and the conference equipment so you’re side-lit
+ or front-lit.
+
+### Pre-arrangements
+- **Send out an agenda in advance**
+ Send a crisp agenda with topics, times and timeframes plus responsibilities
+ and expected results and if required refer to related documents and
+ other sources to allow preparation for the participants in advance and
+ to have everything at hand in the video conference.
+
+- **Send dial-in information**
+ Send dial-in details preferably together with the agenda.
+ Sometimes it is needed to add alternatives to switch immediately in case of
+ anticipated connection errors.
+ Have in mind that this information is used often by participants when
+ creating calendar entries.
+
+- **Send a reminder**
+ Send a reminder with dial-in details again in the morning or shortly before
+ the conference call so that participants don't waste time searching in
+ e-mails from days ago.
+
+### The first minutes
+- **Open early**
+ Open the conference room five to ten minutes before the virtual meeting
+ actually starts, if you are the host.
+
+- **Enter early**
+ Enter the conference room a few minutes before the virtual meeting actually
+ starts, if you are a participant, to test that your equipment works as
+ expected - it's okay then to leave the scene, grab a coffee and show up in
+ time again when the meeting finally starts.
+
+- **Say Hi**
+ Unmute your microphone, switch-on video and say hello, your name and
+ affiliation when entering the conference room to test audio and video quality
+ and let the host and others know that you are here.
+
+- **Mute your microphone**
+ Mute your microphone after the welcome procedure and whenever you do not speak.
+ It reduces disturbances either coming from a noise background environment or
+ coming from your keyboard while typing.
+
+- **Turn off your camera**
+ Keep your camera turned on as long as you and the others feel comfortable.
+ However, turning off the camera improves the audio quality considerably.
+ Removing the video signal saves bandwidth which then is available for the
+ audio signal.
+ Depending on the rules, turning on the camera might be understood also as
+ holding up your hand and, therefore, is a sign that you have a comment or
+ want to say something at next.
+
+- **Look out for an additional text channel**
+ Open the chat window of the conference room, have a look at it, and use it
+ yourself to share important information, e.g. when problems with the
+ communication occur or when locations to ressources have to be shared.
+
+- **Double-check information about you**
+ Check if your name is entered correctly in the respective field so that the
+ host and others know who you are, have a help to address you by name,
+ and identify your contributions either when talking or typing in attached.
+
+- **Stop playing with effects**
+ Conference tools offer options for visual and other effects that,
+ unfortunately, consume computational resources that might be missing
+ for the call itself.
+ Blurring the background in the video is a useful option but already has been
+ identified as the root of lags in video and audio signals.
+ So if not necessary do not use effects in a professional call.
+
+### Chairing
+- **Introduce the rules**
+ After saying Hi when starting the conference, the host shall iterate quickly
+ the selected conventions to follow, how to implement them in the conferencing
+ tool, and ask if there are any questions.
+ Participants take part in other video conferences, too, with slightly
+ different rules and different tools.
+ So a quick recap helps all to run a smooth virtual meeting.
+
+- **Check participation**
+ The host should quickly go through the participants list in the conference
+ tool by saying names and institutions so that everyone knows who is
+ participating.
+ Also name the persons and institutions missing to make everyone aware that
+ particular discussions and decisions may miss relevant stakeholders.
+ It also helps to keep these persons or groups up-to-date afterwards.
+ Hosts should also ask the group if they missed naming someone either
+ participating or being absent.
+
+- **Implement the rules**
+ Everyone is invited to participate actively but the host is asked to chair
+ the virtual meeting and thus provides orientation similar to a panel
+ discussion or an evening talk show.
+ The host should name the one person who is up to speak next.
+ Participants follow what is said and use the functionality of the conference
+ tool to signal that they have a comment or want to add something important,
+ e.g. either by turning on their camera or by dropping a line in the chat.
+ The host then picks up these “hand signsâ€, ensures a clear order who is
+ next, and thus steers an organized discussion in the context of the agenda.
+
+### Participating
+- **Focus on the conference**
+ Following topics and discussions in a video conference is not that easy,
+ especially when held in a different language than your mother tongue,
+ when disturbed by a bad audio quality, and run for a longer time.
+ Additionally, humans are fairly bad at multitasking.
+ So give your full and undivided attention.
+
+- **Speak with normal tone**
+ Speak as you normally do with someone sitting across.
+ Modern computers have decent microphones.
+ They’re usually pretty good at picking up your voice,
+ which means you don’t have to shout at your camera for other people to hear you.
+ Just speak normally, and as long as there isn’t too much background noise,
+ people will hear you.
+
+- **Toggle your microphone when needed**
+ Unmute your microphone when you want to say something and mute it again once
+ you are finished, you may do the same with the camera,
+ it’s okay to toggle both all the time.
+
+- **Turn off the camera**
+ When experiencing audio problems then removing the video signal saves
+ bandwidth that improves the overall audio quality.
+ So turning off your camera and additionally turning off the received video
+ signal of others improves the audio quality considerably.
+
+<div class="alert alert-success">
+ <h2 id="contact-us"><i class="fas fa-info-circle"></i> Comments or Suggestions?</h2>
+ <p>
+ Feel free to <a href="{% link contact.md %}">contact us</a>.
+ </p>
+</div>
diff --git a/_posts/2020/06/2020-06-01-hifis-software-helpdesk-launched.md b/_posts/2020/06/2020-06-01-hifis-software-helpdesk-launched.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e9054654504cb6d7bc093f242f9717f406773cb
--- /dev/null
+++ b/_posts/2020/06/2020-06-01-hifis-software-helpdesk-launched.md
@@ -0,0 +1,24 @@
+---
+title: "HIFIS Software Helpdesk Launched"
+title_image: default
+data: 2020-06-01
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt:
+ The HIFIS Software Helpdesk has been launched.
+ Using common HIFIS authorization and authentication infrastructure
+ (future Helmholtz AAI), users can simply sign in using personal access data
+ of their home institution or even their personal GitHub account.
+---
+
+The [HIFIS Software Helpdesk](https://hifis-help.hzdr.de) has been launched.
+Using common HIFIS authorization and authentication infrastructure
+(future Helmholtz AAI), users can simply sign in using personal access data
+of their home institution or even their personal GitHub account.
+
+<a type="button" class="btn btn-outline-primary btn-lg" href="https://software.hifis.net/announcement/2020/06/01/helpdesk-launch">
+ <i class="fas fa-external-link-alt"></i> Read more
+</a>
diff --git a/_posts/2020/06/2020-06-19-example_post.md b/_posts/2020/06/2020-06-19-example_post.md
deleted file mode 100644
index 8225afb870f3b09e533cbcaf90ada4736d4f15d5..0000000000000000000000000000000000000000
--- a/_posts/2020/06/2020-06-19-example_post.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: "Example Post"
-data: 2020-06-19
-authors:
- - example
-layout: blogpost
----
-
-This is an example blog post.
-Not very fancy but it'll do.
-
diff --git a/_posts/2020/06/2020-06-19-hifis-in-the-egi-newsletter.md b/_posts/2020/06/2020-06-19-hifis-in-the-egi-newsletter.md
new file mode 100644
index 0000000000000000000000000000000000000000..64ff75f2cc8dab93a68d523016127faf65986d7b
--- /dev/null
+++ b/_posts/2020/06/2020-06-19-hifis-in-the-egi-newsletter.md
@@ -0,0 +1,21 @@
+---
+title: "HIFIS in the EGI newsletter"
+title_image: default
+data: 2020-06-08
+authors:
+ - jandt
+layout: blogpost
+categories:
+ - news
+excerpt_separator: <!--more-->
+---
+
+_Helmholtz Federated IT Services - Promoting IT based science at all levels_,
+is the title of our article that appeared in the newsletter of our friends
+from the EGI Federation. In the EGI Newsletters, we give an overview of the
+new HIFIS platform.
+<!--more-->
+
+<a type="button" class="btn btn-outline-primary btn-lg" href="https://www.egi.eu/about/newsletters/helmholtz-federated-it-services-promoting-it-based-science-at-all-levels/">
+ <i class="fas fa-external-link-alt"></i> Read more
+</a>
diff --git a/_posts/2020/06/2020-06-26-guidelines-for-collaborative-notetaking.md b/_posts/2020/06/2020-06-26-guidelines-for-collaborative-notetaking.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d94af9ab73894c72a5707bd2f2d9d52142c7542
--- /dev/null
+++ b/_posts/2020/06/2020-06-26-guidelines-for-collaborative-notetaking.md
@@ -0,0 +1,211 @@
+---
+title: "Guidelines for Collaborative Notetaking"
+title_image: glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
+data: 2020-06-26
+authors:
+ - Martin Hammitzsch (GFZ)
+layout: blogpost
+categories:
+ - guidelines
+redirect_from:
+ - services/collaborative_notetaking/index_ger.html
+ - services/collaborative_notetaking/index.html
+excerpt:
+ You are the one in charge of taking the notes - quick and precise, with
+ additions from, and the consent of, all participants - and you are in charge of
+ making actionable notes available for everyone immediately after the meeting.
+ However, being in charge does not mean that you have to work out the notes alone.
+ Instead, all participants are invited - or better even, obliged - to not only
+ follow the note taking directly but also to contribute when misunderstandings,
+ misinterpretations, delays in record keeping and other obstacles hinder the
+ success of a joint meeting.
+---
+
+## Scope
+We’re talking about _CodiMD_, _HackMD_, _Google Docs_, _Office365_,
+_OnlyOffice_, _Dropbox Paper_, _Polynote_, _Quip_, _Notejoy_, _ShareLaTeX_,
+_Overleaf_ and other services supporting note-taking and working at documents
+in one place together with remote team members either at the same time or
+asynchronously.
+
+## Task
+You're responsible for leading a group of people who work distributed in a
+team - or you support someone who is. Before or after various occasions such
+as meetings and presentations, the event requires agendas, meeting minutes,
+notes, document drafts or even complete and final documents to enable
+transparency, simplify decision-making and increase the performance of your
+team.
+
+## Situation
+You are going to run an in-person meeting or more likely a conference call.
+You need to keep the get-together on track with an agenda and you need to keep
+a record of reported states, discussed issues, agreements and decisions,
+upcoming tasks and other results.
+
+## Challenge
+You are the one in charge of taking the notes - quick and precise, with
+additions from, and the consent of, all participants - and you are in charge of
+making actionable notes available for everyone immediately after the meeting.
+However, being in charge does not mean that you have to work out the notes alone.
+Instead, all participants are invited - or better even, obliged - to not only
+follow the note taking directly but also to contribute when misunderstandings,
+misinterpretations, delays in record keeping and other obstacles hinder the
+success of a joint meeting.
+
+## Approach
+Set up a document in advance which is accessible for all participants.
+It should contain the agenda with references to the relevant material.
+This includes information on collaborative note-taking, how to prepare and
+what is expected from the participants by providing a set of rules for the
+note-taking process.
+Additionally, reserve a time slot in the beginning of the conference to make
+sure to get everyone on board and communicate who is in charge of the final notes,
+or at least of curating the collaborative notes.
+
+## Options
+Below are a few suggestions that might make it into the set of rules for your
+team to make everyone feel comfortable and more productive during a meeting
+while collaboratively taking notes or while collaboratively writing a document
+together.
+
+- **Select a tool meeting your needs**
+When selecting a web-based tool for collaborative note-taking offered by a
+cloud service provider you should know the expectations of the meeting
+participants, collaborators and other stakeholders, especially in terms of the
+look and feel, the functionalities, and their suitability in the intended
+workflow.
+Furthermore, security - including authentication and authorization - as well
+as data protection are non-functional requirements one should have in mind
+when sensitive content or personal data will be stored in these documents.
+
+- **Set-up the document in advance**
+Before the meeting, prepare the document to be used for collaborative note-taking:
+include the intended agenda with topics, times and timeframes as well as
+responsibilities and expected results. If required, refer to related documents
+and other sources to allow preparation for the participants in advance and to
+have everything at hand.
+Leave space close to each agenda item thus indicating the place to facilitate
+inline note-taking in the agenda so that the document automatically becomes the
+meeting minutes with contributions from everyone attending the meeting.
+
+- **Set-up a reusable template**
+ If the prepared document has worked in the meeting, consider the creation of a
+ template to allow an efficient preparation for regular meetings.
+
+- **Allow access and share the document**
+ Depending on the options of the cloud service provider for giving others
+ access to the document, you may set different access levels, e.g., full
+ editing, tracked editing, commenting, or read-access only.
+ You might give access to the public, or to specific individuals who need to
+ have an account with the service provider. While giving access to specific
+ people protects the document from access by others, publicly accessible
+ documents can be factually protected by sharing the URL address of the
+ document with specific people only.
+ However, even if a long and cryptic string within the URL offers limited
+ protection, public documents can still be found by chance or on purpose
+ through URL guessing with automated requests.
+ So, in any case, remind participants not to share further the URL in case of
+ confidential or sensitive content, or do not allow access to the public and
+ give individual access permissions, if possible.
+
+- **Make yourself comfortable with the note-taking tool**
+ Once you have access to a document used for collaborative note-taking, open
+ it and explore the behaviour of and functions available in the tool with the
+ permissions given to you.
+
+- **Make yourself comfortable with the note-taking itself**
+ Effective note-taking requires effort and simultaneous interaction with the notes.
+ Stay focused during the meeting, pay close attention and actively participate.
+ This helps optimize the results from the meeting.
+ So make yourself comfortable with each of the note-taking phases - they all
+ require a different behaviour of individuals and the group of collaborators
+ in certain stages of a meeting and of the note-taking.
+
+- **Double-check information about you**
+ Check if your name and your affiliation are entered correctly in the
+ respective field so that the host and others know who you are, can address
+ you by name, and identify your contributions and comments in the document.
+
+- **Introduce the note-taking process**
+ Collaborative note-taking requires a certain amount of discipline.
+ Everyone should be aware of the intended process for taking notes together.
+ So a quick recap of rules in the beginning of a meeting helps everyone to
+ contribute to the note-taking process. This includes to name the responsible
+ person, ask everyone else to contribute, and outline how to contribute by
+ repeating the relevant rules from this list.
+
+- **Take notes, contribute and follow**
+ If you don't speak, either listen and take notes in your own words to
+ paraphrase what you understand, or, if you don't write, follow other people’s
+ notes, review them, and comment them according to how you have understood
+ the subject matter.
+
+- **Provide immediate feedback and clarify discrepancies**
+ When you identify different understandings while taking notes together with
+ others, then don’t feel shy and speak up to clarify them directly in the
+ meeting and keep track of the clarified understanding in the notes immediately.
+ Speaking up could mean adding a comment in the notes to be taken up by
+ the host or other participants to clarify. Also, take up comments of others
+ and clarify different views, either by correcting, e.g. typos or misspellings,
+ by commenting, or by chatting in the note-taking tool, or - if this doesn’t
+ solve a different understanding - by initiating a short discussion directly
+ in the meeting.
+
+- **Ask information and questions for further discussion**
+ If necessary, add further information not yet discussed or add questions to be
+ discussed so that these information can be taken up by the host in the further
+ discussion of the meeting.
+
+- **Stay structured and organized**
+ Take notes for important, relevant, and non-trivial information, for
+ decisions, for tasks, upcoming events and anything else that will be of any
+ help personally for you at a later point of time thus allowing you to retrace
+ and understand what was reported, discussed, and decided - and why.
+ Write in phrases, not complete sentences, use bullet points and lists where
+ possible, and develop a consistent system of abbreviations and symbols
+ together with the others to save time as you take notes.
+
+- **Earmark and highlight take-home messages**
+ The use of key words and colours are options to label and emphasize specific
+ items that are important for the group and easy to spot throughout the document.
+ Often this is group-specific and must be negotiated within a team beforehand,
+ so that everyone deals with it in the same way.
+ Take cues to apply labels, e.g. “taskâ€, “todo†or “decisionâ€, keep priorities,
+ e.g. “important†or “postponeâ€, define deadlines, e.g. by giving dates,
+ define responsibilities, e.g. by naming persons, and use highlighters and colours,
+ e.g. to indicate key ideas, changes in concepts or links between information.
+ Use these earmarks and highlights at the end of the meeting to go through and
+ wrap-up the important take-home messages. If necessary, allow for some time
+ to work on the notes or discuss them again in the meeting until all agree
+ with the notes which represent your results.
+
+- **Finalise the notes**
+ Reserve time to finish the notes immediately after the conference call or
+ in-person meeting when discussions, results and other things said can be
+ remembered more easily.
+ Finish bullet points that may have been left incomplete or misleading.
+ Order items if necessary. Double-check wording, spelling and grammar.
+
+- **Share the notes and ask for corrections**
+ Finally, share the polished version of the document with all participants
+ providing a fixed time frame for possible feedback, corrections, and comments.
+ Provide a clear procedure for adding changes and comments so that they can be
+ traced subsequently.
+
+- **Accept final contributions, freeze and share the document**
+ Integrate subsequently provided feedback, corrections, and comments, finalise
+ the document, and make the final version available for the target group after
+ freezing the document so that no changes can be applied further on.
+ Freezing a document can be realised by creating a separate PDF version of the
+ document and integrating an appropriate comment or reference to the final
+ version in the original note-taking document.
+ In any case and if possible, freezing a document should additionally be
+ realised by withdrawing permissions for editing the original document in the
+ web-based tool for collaborative note-taking offered by the cloud service provider.
+
+<div class="alert alert-success">
+ <h2 id="contact-us"><i class="fas fa-info-circle"></i> Comments or Suggestions?</h2>
+ <p>
+ Feel free to <a href="{% link contact.md %}">contact us</a>.
+ </p>
+</div>
diff --git a/_sass/boilerplate/_measurements.scss b/_sass/boilerplate/_measurements.scss
index 18fb5602efa0e88b9fccf319e83a2de6e5f18393..a22815c33b20d56ad64cbbd6cac936691c98a152 100644
--- a/_sass/boilerplate/_measurements.scss
+++ b/_sass/boilerplate/_measurements.scss
@@ -42,7 +42,7 @@ $header-min-height: $header-content-min-height
/* --- Title Image --- */
$title-image-text-padding: 10rem;
-$title-image-text-size: 4rem;
+$title-image-text-size: 3rem;
$title-image-height: 2 * $title-image-text-padding + $title-image-text-size;
diff --git a/_sass/common/_cards.scss b/_sass/common/_cards.scss
new file mode 100644
index 0000000000000000000000000000000000000000..a89be0d463a16bdb0a3063d31b926ccd593f98ec
--- /dev/null
+++ b/_sass/common/_cards.scss
@@ -0,0 +1,27 @@
+.flex-cards {
+ display: flex;
+ flex-flow: wrap;
+ justify-content: space-evenly;
+
+ margin-top: 1rem;
+ margin-bottom: 1rem;
+}
+
+.card {
+ width: 15rem;
+
+ margin: 0.5rem;
+ margin: 0.5rem;
+}
+
+.card-body {
+ h3 {
+ margin: 0 !important;
+ }
+}
+
+.card-img-equal {
+ width: 100%;
+ height: 10rem;
+ object-fit: cover;
+}
diff --git a/_sass/common/_title.scss b/_sass/common/_title.scss
index 624a91747eb797adcf120ee3684786f1a1bd760d..df6d9d547fae9961d01f8e28315d00203d4ec9a3 100644
--- a/_sass/common/_title.scss
+++ b/_sass/common/_title.scss
@@ -60,7 +60,7 @@ div#title {
the transitions above and below.
*/
padding-top: 3rem;
- padding-bottom: 3rem;
+ padding-bottom: 2rem;
padding-left: $document-side-margin;
padding-right: $document-side-margin;
diff --git a/assets/css/hifis.scss b/assets/css/hifis.scss
index 1804c0461d7425b7a8f12fa1d26af83485c80c1d..00315bf995152248a705f6fef711afa8913b49bd 100644
--- a/assets/css/hifis.scss
+++ b/assets/css/hifis.scss
@@ -40,6 +40,7 @@
/* === Actual styling === */
@import "common/article";
+@import "common/cards";
@import "common/digest";
@import "common/event";
@import "common/footer";
diff --git a/assets/img/jumbotrons/chris-montgomery-smgTvepind4-unsplash.jpg b/assets/img/jumbotrons/chris-montgomery-smgTvepind4-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5f8bae303b45fff52b0c1faa9b343b60fe9bb861
Binary files /dev/null and b/assets/img/jumbotrons/chris-montgomery-smgTvepind4-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/desktop/chris-montgomery-smgTvepind4-unsplash.jpg b/assets/img/jumbotrons/desktop/chris-montgomery-smgTvepind4-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..2af0771a2ad9cdbbc3cbc88598c0ac461ca3f983
Binary files /dev/null and b/assets/img/jumbotrons/desktop/chris-montgomery-smgTvepind4-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/desktop/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg b/assets/img/jumbotrons/desktop/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7b5ef9d14d8b6785fbd43c34749f8fa1dbc3eec7
Binary files /dev/null and b/assets/img/jumbotrons/desktop/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/desktop/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg b/assets/img/jumbotrons/desktop/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ada9f0b238cdb3148a5a396b13326880a7d7898a
Binary files /dev/null and b/assets/img/jumbotrons/desktop/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/display_2k/chris-montgomery-smgTvepind4-unsplash.jpg b/assets/img/jumbotrons/display_2k/chris-montgomery-smgTvepind4-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fb9e9a6cc4885d3855db6bcbb1100d4113fbfcb3
Binary files /dev/null and b/assets/img/jumbotrons/display_2k/chris-montgomery-smgTvepind4-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/display_2k/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg b/assets/img/jumbotrons/display_2k/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dc5852a96c9d7c6e09f9edc4f2373814e99fc359
Binary files /dev/null and b/assets/img/jumbotrons/display_2k/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/display_2k/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg b/assets/img/jumbotrons/display_2k/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6631df28c8c1f06ef13fbc2364a77efc63cacdfc
Binary files /dev/null and b/assets/img/jumbotrons/display_2k/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg b/assets/img/jumbotrons/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..da63bb77e6f3613ceea78ff41045f72da8d35770
Binary files /dev/null and b/assets/img/jumbotrons/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/phone/chris-montgomery-smgTvepind4-unsplash.jpg b/assets/img/jumbotrons/phone/chris-montgomery-smgTvepind4-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d32340c2dff0ef034c75afdd482eb57f79388d73
Binary files /dev/null and b/assets/img/jumbotrons/phone/chris-montgomery-smgTvepind4-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/phone/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg b/assets/img/jumbotrons/phone/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fbf379932b047302065b421dd3d8793377c4d225
Binary files /dev/null and b/assets/img/jumbotrons/phone/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/phone/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg b/assets/img/jumbotrons/phone/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..158f53a101806db634a8fb1bb1ee1c4603082b3b
Binary files /dev/null and b/assets/img/jumbotrons/phone/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/tablet/chris-montgomery-smgTvepind4-unsplash.jpg b/assets/img/jumbotrons/tablet/chris-montgomery-smgTvepind4-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3c43bd3ebd60cd8707b8933c1fe1c18de7f603a4
Binary files /dev/null and b/assets/img/jumbotrons/tablet/chris-montgomery-smgTvepind4-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/tablet/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg b/assets/img/jumbotrons/tablet/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..34d2d62529af2308cb86390a97c3cd866b556091
Binary files /dev/null and b/assets/img/jumbotrons/tablet/glenn-carstens-peters-RLw-UC03Gwc-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/tablet/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg b/assets/img/jumbotrons/tablet/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42d9eb2a347af30385d02eb214deb1847b078688
Binary files /dev/null and b/assets/img/jumbotrons/tablet/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg differ
diff --git a/assets/img/jumbotrons/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg b/assets/img/jumbotrons/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..42263faa39a83f42bf3e7f33dcab322db8e21c22
Binary files /dev/null and b/assets/img/jumbotrons/volodymyr-hryshchenko-V5vqWC9gyEU-unsplash.jpg differ
diff --git a/faq.md b/faq.md
index d5fa0f58a2a061223eeaddd518a9e4d621f584bf..935ab359ae61ce9e6e43d73c3eadab3513a824c2 100644
--- a/faq.md
+++ b/faq.md
@@ -2,87 +2,14 @@
title: <i class="fas fa-question-circle"></i> FAQ - Frequently Asked Questions
layout: default
excerpt:
- Collection of Frequently Asked Question (FAQ) about HIFIS Software.
+ Collection of Frequently Asked Question (FAQ) about HIFIS.
---
## General
{:.text-success}
-#### [What is the mission of HIFIS Software?][1]
-HIFIS Software Services mission is to empower scientists of any domain to
-implement and to perpetuate modern scientific software development principles
-in order to make research software engineering more sustainable.
+#### [What is the mission of HIFIS?][1]
+The Helmholtz Infrastructure for Federated ICT Services (HIFIS) ensures an
+excellent information environment for outstanding research in all
+Helmholtz research fields.
-#### [How can HIFIS Software help me as a researcher?][2]
-Developing software is an essential part of a modern research process.
-Reproducible high-quality research requires a sustainable software devlopment
-process. HIFIS Software helps you with four different components:
-- [Education & Training](https://software.hifis.net/services#training)
-- [Technology Services](https://software.hifis.net/services#technology)
-- [Consulting Services](https://software.hifis.net/services#consulting)
-- [Community Services](https://software.hifis.net/services#community)
-
-#### [Whom can I talk to about HIFIS Software in my Helmholtz center?][3]
-Visit the [team page](team) for getting contact information. If there is no
-HIFIS Software associate in your center yet, we are happy to help to find
-and nominate someone in your institute as [contact person][contact].
-
-#### [My Helmholtz center is not directly involved into HIFIS Software. Do you still help me?][4]
-Yes, of course. HIFIS in general is a Helmholtz-wide platform that aims to
-provide offers for **all** Helmholtz centers.
-
-#### [Is there more in HIFIS than the Software Cluster?][5]
-Yes, there exist two more clusters within HIFIS:
-
-- *Backbone Services* - provide a stable network infrastructure and jointly
- usable core services in order to meet the increasing demand for networking
- of research and the increasing volume of data in the Helmholtz Association
-- *Cloud Services* - offer a federated cloud platform
- to the entire scientific community and partners in the long tail of
- science
-
-Visit [www.hifis.net](https://www.hifis.net) for general information about
-HIFIS.
-
-#### [How should I acknowledge HIFIS assistance in a paper?][10]
-
-Please include something like this:
-
-> We gratefully acknowledge the HIFIS.net (Helmholtz Federated IT Services)
-> Software team for ... (e.g. support with the [components above][2])
-
----
-## Education & Training
-{:.text-success}
-#### [Which trainings are you able to offer?][6]
-Please have a look into our training catalogue. This is a collection of
-material that either is developed by external organizations, e.g.
-[The Carpentries](https://carpentries.org/), originates from various Helmholtz
-centers or is created by HIFIS Software itself.
-
-#### [Where do I find upcoming training events?][7]
-Our [events page](events) lists future events.
-
-#### [I need a software training for my research group. Can you provide one?][8]
-We are very happy to provide trainings for you. Please have a look into our
-[events page](events) first, to see future scheduled trainings. If there is no
-event that fits your needs, please [contact us][contact].
-
----
-## Technology Services
-{:.text-success}
-#### [When are first Technology Services available for use?][9]
-It is planned to have the first usable services available by mid 2020. You can
-visit the [Technology Services](https://software.hifis.net/services#technology) page for further
-information.
-
-[1]: #what-is-the-mission-of-hifis-software
-[2]: #how-can-hifis-software-help-me-as-a-researcher
-[3]: #whom-can-i-talk-to-about-hifis-software-in-my-helmholtz-center
-[4]: #my-helmholtz-center-is-not-directly-involved-into-hifis-software-do-you-still-help-me
-[5]: #is-there-more-in-hifis-than-the-software-cluster
-[6]: #which-trainings-are-you-able-to-offer
-[7]: #where-do-i-find-upcoming-training-events
-[8]: #i-need-a-software-training-for-my-research-group-can-you-provide-one
-[9]: #when-are-first-technology-services-available-for-use
-[10]: #how-should-i-acknowledge-hifis-assistance-in-a-paper
-[contact]: mailto:{{ site.contact_mail }}
+[1]: #what-is-the-mission-of-hifis
diff --git a/blog/index.html b/news/index.html
similarity index 62%
rename from blog/index.html
rename to news/index.html
index 3eb66d732935eaf0f7b7e91effc9cf5adeb12063..4832d6f4254fefd2d927fb11019578a5e2899331 100644
--- a/blog/index.html
+++ b/news/index.html
@@ -1,5 +1,5 @@
---
-title: HIFIS Blog - Overview
+title: HIFIS News - Overview
title_image: default
layout: pagination
---
diff --git a/services/index.md b/services/index.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b618d859bdc6a509c92e16a8d88ae9a441297e2
--- /dev/null
+++ b/services/index.md
@@ -0,0 +1,25 @@
+---
+title: Services
+title_image: default
+layout: default
+author: none
+redirect_from:
+ - services/index_ger.html
+---
+
+## HIFIS Suggestions and Guidelines
+The optimal use of online collaboration tools is prerequisite for successful
+research and especially in times of social distancing.
+We provide guidelines and helping information.
+
+<div class="flex-cards">
+{% for post in site.categories['guidelines'] -%}
+{% include cards/post_card_image.html post=post %}
+{% endfor -%}
+</div>
+<div class="alert alert-success">
+ <h2 id="contact-us"><i class="fas fa-info-circle"></i> Comments or Suggestions?</h2>
+ <p>
+ Feel free to <a href="{% link contact.md %}">contact us</a>.
+ </p>
+</div>
diff --git a/team.md b/team.md
deleted file mode 100644
index a39e14ef9924f11c1d02b99d639ef666a22c521c..0000000000000000000000000000000000000000
--- a/team.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: The Team
-title_image: default
-layout: team
-excerpt: A list of HIFIS team members and associates.
----
-{% comment %}
- This markdown file triggers the generation of the team page.
- Only the frontmatter is required by Jekyll.
- The contents section does not get rendered into HTML on purpose.
-{% endcomment %}