135 files changed, 7522 insertions, 414 deletions
diff --git a/template/about.html.j2 b/template/about.html.j2
index be9a7298..77c424ee 100644
--- a/template/about.html.j2
+++ b/template/about.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -108,31 +109,12 @@
          <li>
            <p>
            {% trans %}
-            We're receiving funding from NLnet's Next Generation Internet
+            This project is receiving funding from the European Union’s Horizon
-            funding line to document and implement
+            2020 research and innovation programme NGI Assure.
-            the GNU Name System protocol in a way suitable for the
-            IETF standardization process.
            {% endtrans %}
            <br>
-            <a href="https://nlnet.nl/">NLnet Foundation</a><br>
+            <a href="https://www.assure.ngi.eu/">NGI Assure homepage</a><br>
-            <img src="{{ url('static/images/nlnet_logo.gif') }}" alt="NLnet logo">
+            <img style="width: 35%" src="{{ url('images/ngi_assure.png') }}" alt="NGI Assure logo">
-            </p>
-          </li>
-          <li>
-            <p>
-            {% trans %}
-            This project has received funding from the European Union’s Horizon
-            2020 research and innovation programme under the NGI_TRUST grant
-            agreement no 825618.
-            The project aims to integrate re:claimID with the GNU Taler payment
-            system in a pilot in order to demonstrate the practical feasibility
-            and benefits of privacy enhancing technologies for users and
-            commercial service providers. The project is called "Decentralized
-            Identities for Self-Sovereign End-users" (DISSENS).
-            {% endtrans %}
-            <br>
-            <a href="https://wiki.geant.org/display/NGITrust/">GEANT NGI TRUST</a><br>
-            <img style="width: 35%" src="{{ url('static/images/ngi_trust.png') }}" alt="NGI TRUST logo">
            </p>
          </li>
@@ -155,26 +137,39 @@
        <ul>
          <li>
            <p>
+            <a href="https://nlnet.nl/discovery/">NGI DISCOVERY</a> [<a href="https://nlnet.nl/project/GNS/">Project summary</a>]<br>
+            <img style="width: 35%" src="{{ url('images/ngi_discovery.svg') }}" alt="NGI DISCOVERY logo">
+            </p>
+          </li>
+          <li>
+            <p>
+            <a href="https://wiki.geant.org/display/NGITrust/">GEANT NGI TRUST</a> [<a href="{{ url_localized('news/2021-05-DISSENS.html') }}">Project report</a>]<br>
+            <img style="width: 35%" src="{{ url('images/ngi_trust.png') }}" alt="NGI TRUST logo">
+            </p>
+          </li>
+          <li>
+            <p>
            <a href="https://renewablefreedom.org/">Renewable Freedom Foundation / Stiftung Erneuerbare Freiheit</a><br>
-            <img src="{{ url('static/images/rff_logo.png') }}" alt="RFF logo">
+            <img src="{{ url('images/rff_logo.png') }}" alt="RFF logo">
            </p>
          </li>
          <li>
            <p>
            <a href="https://cordis.europa.eu/fp7/">European Commission (FP7)</a><br>
-            <img src="{{ url('static/images/fp7_logo.jpg') }}" alt="FP7 logo">
+            <img src="{{ url('images/fp7_logo.jpg') }}" alt="FP7 logo">
            </p>
          </li>
          <li>
            <p>
            <a href="http://www.dfg.de/">Deutsche Forschungsgemeinschaft</a><br>
-            <img src="{{ url('static/images/dfg_logo.gif') }}" alt="DFG logo">
+            <img src="{{ url('images/dfg_logo.gif') }}" alt="DFG logo">
            </p>
          </li>
          <li>
            <p>
            <a href="https://nlnet.nl/">NLnet Foundation</a><br>
-            <img src="{{ url('static/images/nlnet_logo.gif') }}" alt="NLnet logo">
+            <img src="{{ url('images/nlnet_logo.gif') }}" alt="NLnet logo">
            </p>
          </li>
        </ul>
diff --git a/template/applications.html.j2 b/template/applications.html.j2
index 43b0dd2f..e1f3d48f 100644
--- a/template/applications.html.j2
+++ b/template/applications.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <div class="container-fluid">
  <div class="container">
    <div class="row">
@@ -19,7 +20,7 @@
          hierarchy, GNS uses a directed graph.  Naming conventions
          are similar to DNS, but queries and replies are private even
          with respect to peers providing the answers.  The integrity of
-          records and privacy of look-ups is cryptographically secured.
+          records and privacy of look-ups are cryptographically secured.
          <!-- Too technical: GNS integrates
               a robust, efficient and instant key revocation mechanism. -->
        {% endtrans %}
@@ -37,8 +38,8 @@
      <section>
      <h3>{{ _("Self-sovereign, decentralized identity provider") }}</h3>
      <p>
+        <a href="{{ url_localized('reclaim/index.html') }}">re:claimID</a>
        {% trans %}
-        <a href="https://reclaim.gnunet.org/">re:claimID</a>
        is a decentralized Identity Provider (IdP) service built in top of the
        GNU Name System. It allows users to securely share personal information
        with websites using standardized protocols (OpenID Connect).
@@ -93,106 +94,88 @@
    </div>
    <div class="row">
      <div class="col-lg-6">
-      <section>
-      <h3>{{ _("GNU Taler (Alpha)") }}</h3>
-      <p>
-        {% trans %}
-        <a href="https://taler.net/">GNU Taler</a>
-        is a new privacy-preserving electronic payment system.
-        Payments are cryptographically
-        secured and are confirmed within milliseconds with
-        extremely low transaction costs.
-        {% endtrans %}
-      </p>
-      </section>
-    </div>
-    <div class="col-lg-4">
-    <center><img style="width: 20em" src="{{ url_static('images/logo-2018-dold.svg') }}"  alt="Taler" /></center>
-    </div>
-    </div>
-    <hr/>
-    <div class="row">
-      <div class="col-lg-6">
        <section>
-        <h3>{{ _("secushare") }}</h3>
+          <h3>{{ _("GNU Taler (Alpha)") }}</h3>
-        <p>
+          <p>
-          {% trans %}
+            {% trans %}
-          <a href="https://secushare.org/">secushare</a>
+            <a href="https://taler.net/">GNU Taler</a>
-          is creating a decentralized social networking
+            is a new privacy-preserving electronic payment system.
-          application on top of GNUnet.  Using overlay
+            Payments are cryptographically
-          multicast and the extensible PSYC protocol, notifications are
+            secured and are confirmed within milliseconds with
-          distributed end-to-end encrypted to authorized recipients only.
+            extremely low transaction costs.
-          {% endtrans %}
+            {% endtrans %}
-        </p>
+          </p>
        </section>
      </div>
-    <div class="col-lg-4">
+      <div class="col-lg-4">
-    <center><img style="width: 14em" src="{{ url_static('images/secushare-0444.png') }}"  alt="secushare" /></center>
+        <center>
+          <img style="width: 20em" src="{{ url_static('images/logo-2018-dold.svg') }}"  alt="Taler" />
+        </center>
+      </div>
    </div>
+    <hr/>
-     </div>
+    <div class="row">
-     <hr/>
-     <div class="row">
      <div class="col-lg-6">
        <section>
-        <h3>{{ _("pretty Easy privacy") }}</h3>
+          <h3>{{ _("secushare") }}</h3>
-        <p>
+          <p>
-          {% trans %}
+            {% trans %}
-          <a href="https://pep.foundation/">pretty Easy privacy</a> (p&#8801;p)
+            <a href="https://secushare.org/">secushare</a>
-          is creating a usable end-to-end encrypted e-mail solution using
+            is creating a decentralized social networking
-          opportunistic key exchange.
+            application on top of GNUnet.  Using overlay
-          p&#8801;p will use GNUnet to protect metadata and exploit new
+            multicast and the extensible PSYC protocol, notifications are
-          cryptographic protocols to verify keys.
+            distributed end-to-end encrypted to authorized recipients only.
-          {% endtrans %}
+            {% endtrans %}
-        </p>
+          </p>
        </section>
      </div>
-    <div class="col-lg-4">
+      <div class="col-lg-4">
-    <center><img style="width: 14em" src="{{ url_static('images/peplogo.svg') }}"  alt="pEp" /></center>
+        <center>
-    </div>
+          <img style="width: 14em" src="{{ url_static('images/secushare-0444.png') }}"  alt="secushare" />
+        </center>
      </div>
-     <hr/>
+    </div>
-     <div class="row">
+    <hr/>
+    <div class="row">
      <div class="col-lg-6">
        <section>
-        <h3>{{ _("Cadet-GTK") }}</h3>
+          <h3>{{ _("Messenger-GTK") }}</h3>
-        <p>
+          <p>
-          {% trans %}
+            {% trans %}
-          <a href="https://gitlab.com/gnunet-messenger/cadet-gtk">Cadet-GTK</a>
+            <a href="https://git.gnunet.org/messenger-gtk.git/">Messenger-GTK</a>
-          is a convenient but feature-rich graphical application
+            is a convergent GTK messaging application using the GNUnet Messenger
-          providing messaging using especially the CADET subsystem. It is
+            service. The goal is to provide private and secure communication
-          developed using GTK and libhandy for a convergent design.
+            between any group of devices.
-          {% endtrans %}
+            {% endtrans %}
-        </p>
+          </p>
        </section>
      </div>
-    <div class="col-lg-4">
+      <div class="col-lg-4">
-    <center><img style="width: 8em" src="{{ url_static('images/cadet-gtk.svg') }}"  alt="cadet-gtk" /></center>
+        <center>
-    </div>
+          <img style="width: 8em" src="{{ url_static('images/messenger-gtk.svg') }}"  alt="messenger-gtk" />
+        </center>
      </div>
-      <hr/>
+    </div>
-      <div class="row">
+    <hr/>
+    <div class="row">
      <div class="col-lg-6">
        <section>
-        <h3>{{ _("groupchat") }}</h3>
+          <h3>{{ _("messenger-cli") }}</h3>
-        <p>
+          <p>
-          {% trans %}
+            {% trans %}
-          <a href="https://git.gnunet.org/groupchat.git/">groupchat</a>
+            <a href="https://git.gnunet.org/messenger-cli.git/">messenger-cli</a>
-          is a terminal user interface providing messaging using especially the CADET subsystem. It is
+            is a terminal user interface providing messaging using the GNUnet Messenger
-          developed using nim. Cadet-GTK and groupchat are planned to be compatible.
+            service. It is developed in C using ncurses. Messenger-GTK and messenger-cli 
-          {% endtrans %}
+            are fully compatible.
-        </p>
+            {% endtrans %}
+          </p>
        </section>
      </div>
-    <div class="col-lg-4">
+      <div class="col-lg-4">
-    <center><img style="width: 14em" src="{{ url_static('images/groupchat.png') }}"  alt="groupchat" /></center>
+        <center>
-    </div>
+          <img style="width: 10em" src="{{ url_static('images/messenger-cli.png') }}"  alt="messenger-cli" />
+        </center>
      </div>
    </div>
  </div>
 </div>
diff --git a/template/architecture.html.j2 b/template/architecture.html.j2
index ef6e8799..63fadfb2 100644
--- a/template/architecture.html.j2
+++ b/template/architecture.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -8,49 +9,9 @@
  <div class="container">
    <div class="row">
-     <!--<div class="col-10">
+      <div class="col-10">
-        <img class="img-fluid border rounded" src="../static/images/gnunet-arch-full.svg">
+       <img class="img-fluid" src="../static/images/arch.png">
      </div>
-      <div class="col-2 d-none d-sm-block">
-        <h4>{{ _("Legend") }}:</h4>
-        <dl>
-          <dt>house</dt>
-          <dd>application</dd>
-        </dl>
-        <dl>
-          <dt>circle</dt>
-          <dd>application</dd>
-        </dl>
-        <dl>
-          <dt>box</dt>
-          <dd>daemon</dd>
-        </dl>
-        <dl>
-          <dt>diamond</dt>
-          <dd>library</dd>
-        </dl>
-        <dl>
-          <dt>blackline</dt>
-          <dd>dependency</dd>
-        </dl>
-        <dl>
-          <dt>blue line</dt>
-          <dd>extension via plugin</dd>
-        </dl>
-        <dl>
-          <dt>red line</dt>
-          <dd>possibly useful</dd>
-        </dl>
-        <dl>
-          <dt>dashed</dt>
-          <dd>in planning</dd>
-        </dl>
-      </div>-->
-  <div class="col-10">
-     <img class="img-fluid" src="../static/images/arch.png">
-  </div>
    </div>
  </div>
@@ -65,7 +26,7 @@
          messaging layer (CADET), a public key infrastructure
          (GNS) and a pluggable transport system (TRANSPORT).<br>
          Using public keys for addresses
-          and self-organized decentralized routing algorithms,
+          and self-organizing decentralized routing algorithms,
          these subsystems replace the traditional TCP/IP stack.
          {% endtrans %}
        </p>
@@ -78,7 +39,7 @@
          {% trans %}
          GNUnet is implemented using a multi-process architecture.
          Each subsystem runs as a separate process, providing
-          fault-isolation and enabling tight permissions to be
+          fault isolation and enabling tight permissions to be
          granted to each subsystem.  Naturally, the
          implementation is a <a href="https://www.gnu.org/">GNU</a>
          package, and will always remain free software.
@@ -91,13 +52,13 @@
      <div class="col-md">
        <h2>{{ _("System architecture") }}</h2>
        <p>
-        Read more about the system architecure in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>.
+        Read more about the system architecture in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>.
        </p>
      </div>
      <div class="col-md">
        <h2>{{ _("Subsystems") }}</h2>
        <p>
-        Read more about the subsystems (or GNUnet services) in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>.
+        Read more about the subsystems (or GNUnet services) in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>.
        </p>
      </div>
    </div>
@@ -112,11 +73,53 @@
      <div class="col-md">
        <h2>{{ _("APIs") }}</h2>
        <p>
-        GNUnet offers variaty of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>.
+        GNUnet offers a variety of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>.
        </p>
      </div>
    </div>
  </div>
+  <div class="container">
+    <div class="row">
+     <div class="col-10">
+        <img class="img-fluid border rounded" src="../static/images/gnunet-arch-full.svg">
+      </div>
+      <div class="col-2 d-none d-sm-block">
+        <h4>{{ _("Legend") }}:</h4>
+        <dl>
+          <dt>house</dt>
+          <dd>application</dd>
+        </dl>
+        <dl>
+          <dt>circle</dt>
+          <dd>application</dd>
+        </dl>
+        <dl>
+          <dt>box</dt>
+          <dd>daemon</dd>
+        </dl>
+        <dl>
+          <dt>diamond</dt>
+          <dd>library</dd>
+        </dl>
+        <dl>
+          <dt>blackline</dt>
+          <dd>dependency</dd>
+        </dl>
+        <dl>
+          <dt>blue line</dt>
+          <dd>extension via plugin</dd>
+        </dl>
+        <dl>
+          <dt>red line</dt>
+          <dd>possibly useful</dd>
+        </dl>
+        <dl>
+          <dt>dashed</dt>
+          <dd>in planning</dd>
+        </dl>
+      </div>
+    </div>
+  </div>
 </article>
 {% endblock body_content %}
diff --git a/template/contact.html.j2 b/template/contact.html.j2
index 8f320503..6d894f13 100644
--- a/template/contact.html.j2
+++ b/template/contact.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -18,19 +19,6 @@
          {% endtrans %}
        </p>
    </div>
-    <div class="col-lg-6">
-      <h2>{{ _("The IRC channel") }}</h2>
-        <p>
-          {% trans %}
-            <tt>#gnunet</tt> is reachable via
-            <a href="https://freenode.net">irc.freenode.net</a>.
-            There is also an
-            <a href="https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/">archive</a>
-            available.
-          {% endtrans %}
-        </p>
-    </div>
  </div>
  <div class="row">
diff --git a/template/copyright.html.j2 b/template/copyright.html.j2
index ca779567..95db9c51 100644
--- a/template/copyright.html.j2
+++ b/template/copyright.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/dev_pages/t3sserakt.html.j2 b/template/dev_pages/t3sserakt.html.j2
new file mode 100644
index 00000000..5ef774ee
--- /dev/null
+++ b/template/dev_pages/t3sserakt.html.j2
@@ -0,0 +1,106 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<!-- Jumbotron -->
+<div>
+  <div class="container">
+    <div class="row">
+      <div class="container text-center">
+        <h1>{{ _("Developer page: t3sserakt") }}</h1>
+      </div>
+    </div>
+    <div class="container text-center">
+      <img src="{{ url_static('images/t3sserakt.jpg') }}"  alt="t3sserakt" />
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Current Work") }}</h2>
+        <p>
+        {% trans %}
+             Today consumer devices are behind a NAT quite often, restricting internet connectivity. There are several methods to reach peers being
+behind a NAT, but there are as many reasons those existing methods might fail. We will implement a new way of NAT traversal that we
+think of being independent from the existing network configuration, and does not require a third party which is not natted helping two
+peers to connect to each other. For details have a look on the <a href="../probnat/">project page</a>
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Past Project") }}</h2>
+        <h3>{{ _("Transport Next Generation") }}</h3>
+        <p>
+          {% trans %}
+          The current GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, UDP, HTTP(S) and other protocols) together with the ATS subsystem for bandwidth allocation and choosing plugins has several issues with its design. With the Layer-2-Overlay project we like to implement the design goals of the future GNUnet TRANSPORT Next Generation (TNG) subsystem. For details have a look on the <a href="../l2o/">project page</a>.
+      {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Voluntary Work") }}</h2>
+        <p>
+          {% trans %}
+            In the past I have tried to help making the vision of the <a href="http://secushare.org">secushare</a> project a reality. To achieve this the GNUnet framework was the perfect match for a solution to fullfill the privacy preserving part of that vision, and we could concentrate to build a tool for social communication that deserves its name. While trying to use GNUnet, we found and fixed bugs. For example there was one <a href="https://bugs.gnunet.org/view.php?id=5822">bug</a> in CADET which prevented the re-establishment of a connection after a communication partner suddenly stopped communicating. From our perspective there is no alternativ to GNUnet, which led us to first bring the parts of GNUnet needed by secushare to a state that they can be used prouctively.
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Contact Information") }}</h2>
+        <p>
+          <div class="container">
+            <div class="row">
+              <div class="col-lg-2">Mail:</div>
+              <div class="col-lg-6">t3sserakt@gnunet.org</div>
+            </div>
+            <div class="row">
+              <div class="col-lg-2">Fediverse:</div>
+              <div class="col-lg-6"><a rel="me" href="https://c3d2.social/@t3sserakt">@t3sserakt@c3d2.social</a></div>
+            </div>
+            <div class="row">
+              <div class="col-lg-2">Matrix:</div>
+              <div class="col-lg-6">@t3sserakt:tchncs.de</div>
+            </div>
+            <div class="row">
+              <div class="col-lg-2">PGP:</div>
+              <div class="col-lg-6"><a href="https://keyoxide.org/hkp/34156165BAC792A688C990CFC9A2D9D808FF308D">keyoxide</a></div>
+            </div>
+          </div>
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+{% endblock body_content %}
diff --git a/template/developers.html.j2 b/template/developers.html.j2
index c28418d2..e7e013fc 100644
--- a/template/developers.html.j2
+++ b/template/developers.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <div class="jumbotron">
  <div class="text-center">
    <h1>{{ _("GNUnet for developers") }}</h1>
diff --git a/template/download.html.j2 b/template/download.html.j2
index a7df9108..42a0aa48 100644
--- a/template/download.html.j2
+++ b/template/download.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
  <article class="d-flex flex-column p-2 bd-highlight">
    <div class="container">
      <div class="text-center">
diff --git a/template/engage.html.j2 b/template/engage.html.j2
index 000396ab..517c098d 100644
--- a/template/engage.html.j2
+++ b/template/engage.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -10,33 +11,26 @@
    <div class="col-md">
      <h2>Join the conversation!</h2>
      <p>
-        There are many ways to get engaged with GNUnet. A first step is to join the conversation on the mailing lists and on our IRC channel to keep up with development, find technical help, and discuss GNUnet:
+        There are many ways to get engaged with GNUnet. A first step is to join the conversation on the mailing lists to keep up with development, find technical help, and discuss GNUnet:
      </p>
      <h4>Mailing List</h4>
      <p>
        You can get help on our mailing list <a href="https://lists.gnu.org/mailman/listinfo/help-gnunet">help-gnunet</a>. <br>If you generally want to be informed about recent updates and happenings, get in touch over our <a href="https://lists.gnu.org/mailman/listinfo/info-gnunet">info mailing list</a>.<br/>
        If you want to hack on GNUnet or want to follow technical discussions, try our <a href="https://lists.gnu.org/mailman/listinfo/gnunet-developers">developer mailing list</a>
      </p>
-      <h4>IRC</h4>
-      <p>
-        Most of the GNUnet developers are on the
-        IRC channel #gnunet on freenode (connect via
-        <a href="ircs://chat.freenode.net:6697/#gnunet">ircs://chat.freenode.net:6697/#gnunet</a>).
-        Please be patient and stay around at least for some hours to get an answer for your request. <!-- There is also a Matrix bridge to the IRC where you can get a backlog without staying connected. -->
-      </p>
      <h4>Mumble</h4>
      <p>
-            We have a monthly get-together on mumble where we talk about recent developments, strategies, and politics.<br>
+            We have a monthly get-together on Mumble where we talk about recent developments, strategies, and politics.<br>
            We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br>
-            To connect just enter "gnunet.org" as server into your mumble client; leave everything else as default. 
+            To connect just enter "gnunet.org" as server into your Mumble client; leave everything else as default.
      </p>
      </p>
      <h4>PSYC</h4>
      <p>
-        You find some of us on PSYC using the following adresses: 
+        You find some of us on PSYC using the following adresses:
        <ul>
-          <li>psyc://loupsycedyglgamf.onion/@welcome</li>
+          <li>psyc://psycyificvaxuzut3t6hcies3stfdtlzqftcnmbb5su3xv4zugplsfad.onion/@welcome</li>
-          <li>irc://loupsycedyglgamf.onion:67/welcome</li>
+          <li>irc://psycyificvaxuzut3t6hcies3stfdtlzqftcnmbb5su3xv4zugplsfad.onion:67/welcome</li>
          <li>psyc://psyced.org/@welcome</li>
          <li>irc://psyced.org/welcome</li>
          <li>xmpp:*welcome@psyced.org</li>
@@ -46,7 +40,7 @@
    <div class="col-md">
      <h2>Install GNUnet!</h2>
      <p>
-        Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>.
+        Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (as of June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>.
     </p>
     <h2>Use GNUnet!</h2>
      <p>
@@ -62,14 +56,16 @@
        <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li>
        <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li>
        <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li>
-        <li>Please follow up with eventual questions about the bug. </li>
+        <li>Please follow up on any questions about the bug.</li>
-        <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credits :)</li>
+        <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credit :)</li>
      </ul>
    <h2>Contribute!</h2>
      <p>
        There are various ways to contribute. We especially need coders with C skills and knowledge of crypto. Development work on this this website, it&#39;s translations, the bibliography, our wide documentation, and other efforts are most welcome, too.<br>
        The core software of GNUnet used to be released with long breaks between releases. Since the 0.11.0 release we try to make releases more regularly. Therefore package maintainers who are interested in working together with an welcoming environment are invited to contribute packages of our software to any OS/PM and request help.<br>
-        Last but not least designers are welcome to contact us about projects which require help.
+        Last but not least designers are welcome to contact us about projects which require help.<br>
+        You may also take a look into our bug tracker
+        <a href="https://bugs.gnunet.org/search.php?tag_string=beginner">for beginner-friendly issues</a>.
    </p>
    </div>
  </div>
diff --git a/template/ev.html.j2 b/template/ev.html.j2
index d8589b11..812af3cc 100644
--- a/template/ev.html.j2
+++ b/template/ev.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -40,7 +41,7 @@
          to support GNUnet e.V. and in particularly contribute to the
          technical development within their means. For further
          details, we refer to the
-          <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung</a>
+          <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung (Charter)</a>
          (currently only available in German, translations welcome).
        {% endtrans %}
      </p>
@@ -52,18 +53,18 @@
      <h3>{{ _("Governance") }}</h3>
      <p>
        {% trans %}
-          You can find our "Satzung", and the list of members under
+          You can find our charter, and the list of members under
          <a href="https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex">https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex</a>.
          The current board consists of:
          <dl><dt>Vorsitz</dt>
            <dd><a href="https://schanzen.eu">Martin Schanzenbach</a></dd>
-            <dt>stellvertretender Vorsitz</dt>
+            <dt>Stellvertretender Vorsitz</dt>
-            <dd>t3sserakt</dd>
+            <dd>Florian Felgenhauer</dd>
            <dt>Kassenwart</dt>
            <dd>Florian Dold</dd>
            <dt>Beisitzer</dt>
            <dd>
-              <a href="https://grothoff.org/christian/">Christian Grothoff</a>, ch3
+              <a href="https://grothoff.org/christian/">Christian Grothoff</a>, Julius Bünger
            </dd>
          </dl>
        {% endtrans %}
@@ -83,7 +84,7 @@
  <div class="row">
    <div class="col-md">
-      <h3>{{ _("Support Us!") }}</h3>
+      <h3 id="support">{{ _("Support Us!") }}</h3>
      <p>
        {% trans %}
          Everybody is welcome to support us via donations. For
diff --git a/template/faq.html.j2 b/template/faq.html.j2
index f23a9d7a..66da7fc2 100644
--- a/template/faq.html.j2
+++ b/template/faq.html.j2
@@ -1,65 +1,1014 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <div class="container-fluid">
  <div class="container text-center">
    <h1>FAQs<h1>
-    <h2><i>This page is a work-in-progress</i></h2>
-  </div>
  </div>
+</div>
 <div class="container">
-  <article>
+  <div class="row">
-    <section>
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
-      <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
-      <p>
+        <a class="nav-link" href="#general">{{ _("General") }}</a>
-        {% trans %}
+        <a class="nav-link" href="#features">{{ _("Features") }}</a>
-        A: GNUnet is still undergoing major development. It is largely not yet ready
+        <a class="nav-link" href="#gns">GNU Name System</a>
-  for usage beyond developers. Your mileage will vary depending on the
+        <a class="nav-link" href="#errors">{{ _("Error messages") }}</a>
-  functionality you use, but you will always likely run into issues with
+        <a class="nav-link" href="#fs">{{ _("File-sharing") }}</a>
-  our current low-level transport system. We are currently in the process of
+        <a class="nav-link" href="#contrib">{{ _("Contributing") }}</a>
-  rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)
+      </nav>
-        {% endtrans %}
+    </div>
-      </p>
-    </section>
+    <div class="col">
-    <section>
+      <article>
-      <h3>{{ _("Is GNUnet build using distributed ledger technologies?") }}</h3>
+        <h2><a name="general" class="subnav-anchor"></a>{{ _("General") }}</h2>
-      <p>
+        General questions about the project.
-        {% trans %}
+        <section>
-        A: No. GNUnet is a new network protocol stack for building secure,
+          <h3>{{ _("What do I do if my question is not answered here?") }}</h3>
-  distributed, and privacy-preserving applications.
+          <p>
-  While a ledger could be built using GNUnet, we currently have no plans in
+          {% trans %}
-  doing so.
+          A: There are many other sources of information. You can read additional
-        {% endtrans %}
+          documentation or ask the question on the help-gnunet@gnu.org mailing list.
-      </p>
+          {% endtrans %}
-    </section>
+          </p>
-    <section>
+        </section>
-      <h3>{{ _("I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. Should I worry?") }}</h3>
+        <section>
-      <p>
+          <h3>{{ _("When are you going to release the next version?") }}</h3>
-        {% trans %}
+          <p>
-        A: Right now, this is expected and a known cause for high
+          {% trans %}
-        latency in GNUnet.  We have started a major rewrite to address
+          A: The general answer is, when it is ready. A better answer may be: earlier
-        this and other problems, but until the Transport Next
+          if you contribute (test, debug, code, document). Every release will be
-        Generation (TNG) is ready, these warnings are expected.
+          anounced on the info-gnunet@gnu.org mailing list and on
-        {% endtrans %}
+          <a href="https://planet.gnu.org">planet GNU</a>. You can subscribe to the
-      </p>
+          mailing list or the RSS feed of this site to automatically receive a
-    </section>
+          notification.
-    <section>
+          {% endtrans %}
-      <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          </p>
-      <p>
+        </section>
-        {% trans %}
+        <section>
-        A: gnunet-gtk is a separate download. The package
+          <h3>{{ _("Is the code free?") }}</h3>
-        contains various GTK+ based graphical interfaces, including a
+          <p>
-        graphical tool for configuration.
+          {% trans %}
-        {% endtrans %}
+          A: GNUnet is free software, available under the
-      </p>
+          <a href="https://www.gnu.org/licenses/agpl-3.0.en.html">GNU Affero Public License (AGPL)</a>.
-    </section>
+          {% endtrans %}
-  </article>
+          </p>
-<!--
+        </section>
-<h2>{{ ("Q?") }}</h2>
+        <section>
+          <h3>{{ _("Are there any known bugs?") }}</h3>
-<h2>{{ ("Q?") }}</h2>
+          <p>
+          {% trans %}
-<h2>{{ ("Q?") }}</h2>
+          A: We track the list of currently known bugs in the
-->
+          <a href="https://bugs.gnunet.org/">Mantis system</a>.
+          Some bugs are occasionally reported directly to developers or the developer
+          mailing list. This is discouraged since developers often do not have the time
+          to feed these bugs back into the Mantis database. Please report bugs directly
+          to the bug tracking system. If you believe a bug is sensitive, you can set its
+          view status to private (this should be the exception).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          <p>
+          {% trans %}
+          A: gnunet-gtk is a separate download. The package
+          contains various GTK+ based graphical interfaces, including a
+          graphical tool for configuration.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why does gnunet-service-nse create a high CPU load?") }}</h3>
+          <p>
+          {% trans %}
+          A: The gnunet-service-nse process will initially compute a so-called
+          &quot;proof-of-work&quot; which is used to convince the network that your
+          peer is real (or, rather, make it expensive for an adversary to mount a Sybil
+          attack on the network size estimator). The calculation is expected to take a
+          few days, depending on how fast your CPU is. If the CPU load is creating a
+          problem for you, you can set the value &quot;WORKDELAY&quot; in the
+          &quot;nse&quot; section of
+          your configuration file to a higher value. The default is &quot;5 ms&quot;.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNUnet compare to Tor?") }}</h3>
+          <p>
+          {% trans %}
+          A: Tor focuses on anonymous communication and censorship-resistance for TCP
+          connections and, with the Tor Browser Bundle, for the Web in particular.
+          GNUnet does not really have one focus; our theme is secure decentralized
+          networking, but that is too broad to be called a focus.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNUnet compare to I2P?") }}</h3>
+          <p>
+          {% trans %}
+          A: Both GNUnet and I2P want to build a better, more secure, more decentralized
+          Internet. However, on the technical side, there are almost no overlaps.
+          <br><br>
+          I2P is written in Java, and has (asymmetric) tunnels using onion (or garlic)
+          routing as the basis for various (anonymized) applications. I2P is largely used
+          via a Web frontend.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is still undergoing major development. It is largely not yet ready
+          for usage beyond developers. Your mileage will vary depending on the
+          functionality you use, but you will always likely run into issues with
+          our current low-level transport system. We are currently in the process of
+          rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNUnet build using distributed ledger technologies?") }}</h3>
+          <p>
+          {% trans %}
+          A: No. GNUnet is a new network protocol stack for building secure,
+          distributed, and privacy-preserving applications.
+          While a ledger could be built using GNUnet, we currently have no plans in
+          doing so.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="features" class="subnav-anchor"></a>{{ _("Features") }}</h2>
+        <section>
+          <h3>{{ _("What can I do with GNUnet?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can do
+          more than just one thing. Naturally, the implementation and documentation of
+          some of the features that exist are more advanced than others.
+          {% endtrans %}
+          </p>
+          <p>
+          {% trans %}
+          For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully
+          decentralized and censorship-resistant replacement for DNS and a mechanism for
+          IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG).
+          {% endtrans %}
+          See also: <a href="{{ url_localized('applications.html') }}">Applications</a>.
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is it possible to surf the WWW anonymously with GNUnet?") }}</h3>
+          <p>
+          {% trans %}
+          A: It is not possible use GNUnet for anonymous browsing at this point.
+          We recommend that you use Tor for anonymous surfing.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is it possible to access GNUnet via a browser as an anonymous WWW?") }}</h3>
+          <p>
+          {% trans %}
+          A: There is currently no proxy (like fproxy in Freenet) for GNUnet that would
+          make it accessible via a browser. It is possible to build such a proxy and
+          all one needs to know is the protocol used between the browser and the proxy and
+          the GNUnet code for file-sharing.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          <p>
+          {% trans %}
+          A: There are actually a few graphical user interfaces for different functions.
+          gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for file-sharing.
+          There are a few other gnunet-XXX-gtk GUIs of lesser importance.
+          Note that in order to obtain the GUI, you need to install the gnunet-gtk
+          package, which is a separate download.
+          gnunet-gtk is a meta GUI that integrates most of the other GUIs in one window.
+          One exception is gnunet-setup, which must still be run separately at this time
+          (as setup requires the peer to be stopped).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Which operating systems does GNUnet run on?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is being developed and tested primarily under Debian GNU/Linux.
+          Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch,
+          FreeBSD and macOS.
+          We have reports of working versions on many other GNU/Linux distributions;
+          in the past we had reports of working versions on NetBSD, OpenBSD and Solaris.
+          However, not all of those reports are recent, so if you cannot get GNUnet to
+          work on those systems please let us know.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="gns" class="subnav-anchor"></a>GNU Name System</h2>
+        <section>
+          <h3>{{ _("Who runs the GNS root zone?") }}</h3>
+          <p>
+          {% trans %}
+          A: Short answer: you. The long answer is the GNUnet will ship with a
+          default configuration of top-level domains. The governance of this default
+          configuration is not yet established. In any case, the user will be able
+          to modify this configuration at will. We expect normal users to have
+          no need to edit their own GNS zone(s) unless they host services themselves.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Where is the per-user GNS database kept?") }}</h3>
+          <p>
+          {% trans %}
+          A: The short answer is that the database is kept at the user's GNUnet peer.
+          Now, a user may run multiple GNUnet peers, in which case the database could be
+          kept at each peer (however, we don't have code for convenient replication).
+          Similarly, multiple GNUnet peers can share one instance of the database ---
+          the &quot;gnunet-service-namestore&quot; can be accessed from remote
+          (via TCP). The actual data can be stored in a Postgres database, for which
+          various replication options are again applicable. Ultimately, there are many
+          options for how users can store (and secure) their GNS database.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the expected average size of a GNS namestore database?") }}</h3>
+          <p>
+          {% trans %}
+          A: Pretty small. Based on our user study where we looked at browser histories
+          and the number of domains visited, we expect that GNS databases will only
+          grow to a few tens of thousands of entries, small enough to fit even on mobile
+          devices.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNS resistant to the attacks on DNS used by the US?") }}</h3>
+          <p>
+          {% trans %}
+          A: We believe so, as there is no entity that any government could force to
+          change the mapping for a name except for each individual user (and then the
+          changes would only apply to the names that this user is the authority for).
+          So if everyone used GNS, the only practical attack of a government would be to
+          force the operator of a server to change the GNS records for his server to
+          point elsewhere. However, if the owner of the private key for a zone is
+          unavailable for enforcement, the respective zone cannot be changed and any
+          other zone delegating to this zone will achieve proper resolution.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS compare to other name systems?") }}</h3>
+          <p>
+          {% trans %}
+          A: A scientific paper on this topic 
+          <a href="https://grothoff.org/christian/ns2018.pdf">has been published
+          </a> and below is a table from the publication.
+          For detailed descriptions please refer to the paper.
+          {% endtrans %}
+          <table>
+            <thead>
+              <td></td>
+              <td>MitM manipulation</td>
+              <td>Zone walk</td>
+              <td>Client observation (network)</td>
+              <td>Client observation (operator)</td>
+              <td>Traffic amplification</td>
+              <td>Censorship/legal attacks</td>
+              <td>Ease of migration</td>
+            <thead>
+            <tbody>
+              <tr>
+              <td>DNS</td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+++</td>
+              </tr>
+              <tr>
+              <td>DNSSEC</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>DNSCurve</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>DoT/DoH</td>
+              <td><i class="fa fa-check"></i></td>
+              <td>n/a</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>Confid. DNS</td>
+              <td><i class="fa fa-times"></i></td>
+              <td>n/a</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>++</td>
+              </tr>
+              <tr>
+              <td>Namecoin</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td>-</td>
+              </tr>
+              <tr>
+              <td>GNS</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td>--</td>
+              </tr>
+              <tr>
+              <td>RAINS</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>--</td>
+              </tr>
+            </tbody>
+          </table>
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and CoDoNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the
+          authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and
+          there are still registrars that determine who owns a name.
+          <br><br>
+          With GNS, we decentralize the database and also decentralize the
+          responsibility for naming: each user runs their own personal root zone and is
+          thus in complete control of the names they use. GNS also has many additional
+          features (to keep names short and enable migration) which don't even make
+          sense in the context of CoDoNS.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and SocialDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: Like GNS, SocialDNS allows each user to create DNS mappings. However, with
+          SocialDNS the mappings are shared through the social network and subjected to
+          ranking. As the social relationships evolve, names can thus change in
+          surprising ways.
+          <br><br>
+          With GNS, names are primarily shared via delegation, and thus mappings will
+          only change if the user responsible for the name (the authority) manually
+          changes the record.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and ODDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: ODDNS is primarily designed to bypass the DNS root zone and the TLD
+          registries (such as those for ".com" and ".org"). Instead of using those,
+          each user is expected to maintain a database of (second-level) domains
+          (like "gnu.org") and the IP addresses of the respective name servers.
+          Resolution will fail if the target name servers change IPs.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and Handshake?") }}</h3>
+          <p>
+          {% trans %}
+          A: Handshake is a blockchain-based method for root zone governance.
+          Hence, it does not address the name resolution process itself but
+          delegates resolution into DNS after the initial TLD resolution.
+          Not taking sustainablility considerations into account, Handshake
+          could be used as an additional supporting GNS root zone governance
+          model, but we currently do not have such plans in mind.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and TrickleDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: TrickleDNS pushes (&quot;critical&quot;) DNS records between DNS resolvers
+          of participating domains to provide &quot;better availability, lower query
+          resolution times, and faster update propagation&quot;. Thus TrickleDNS is
+          focused on defeating attacks on the availability (and performance) of record
+          propagation in DNS, for example via DDoS attacks on DNS root servers.
+          TrickleDNS is thus concerned with how to ensure distribution of authoritative
+          records, and authority remains derived from the DNS hierarchy.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Does GNS require real-world introduction (secure PKEY exchange) in the style of the PGP web of trust?") }}</h3>
+          <p>
+          {% trans %}
+          A: For security, it is well known that an initial trust path between the two
+          parties must exist. However, for applications where this is not required,
+          weaker mechanisms can be used. For example, we have implemented a
+          first-come-first-served (FCFS) authority which allows arbitrary users to
+          register arbitrary names. The key of this authority is included with every
+          GNUnet installation. Thus, any name registered with FCFS is in fact global and
+          requires no further introduction. However, the security of these names
+          depends entirely on the trustworthiness of the FCFS authority.
+          The authority can be queried under the &quot;.pin&quot; TLD.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How can a legitimate domain owner tell other people to not use his name in GNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: Names have no owners in GNS, so there cannot be a &quot;legitimate&quot;
+          domain owner. Any user can claim any name (as his preferred name or
+          &quot;pseudonym&quot;) in his NICK record. Similarly, all other users can
+          choose to ignore this preference and use a name of their choice (or even
+          assign no name) for this user.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Did you consider the privacy implications of making your personal GNS zone visible?") }}</h3>
+          <p>
+          {% trans %}
+          A: Each record in GNS has a flag &quot;private&quot;. Records are shared with
+          other users (via DHT or zone transfers) only if this flag is not set.
+          Thus, users have full control over what information about their zones is made
+          public.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?") }}</h3>
+          <p>
+          {% trans %}
+          A: The question presumes that (a) virtual hosting is only necessary because of
+          IPv4 address scarcity, and (b) that LEHOs are only useful in the context of
+          virtual hosting. However, LEHOs are also useful to help with X.509 certificate
+          validation (as they specify for which legacy hostname the certificate should
+          be valid). Also, even with IPv6 fully deployed and &quot;infinite&quot; IP
+          addresses being available, we're not sure that virtual hosting would
+          disappear. Finally, we don't want to have to wait for IPv6 to become
+          commonplace, GNS should work with today's networks.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why does GNS not use a trust metric or consensus to determine globally unique names?") }}</h3>
+          <p>
+          {% trans %}
+          A: Trust metrics have the fundamental problem that they have thresholds.
+          As trust relationships evolve, mappings would change their meaning as they
+          cross each others thresholds. We decided that the resulting unpredictability
+          of the resolution process was not acceptable. Furthermore, trust and consensus
+          might be easy to manipulate by adversaries.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How do you handle compromised zone keys in GNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: The owner of a private key can create a revocation message. This one can
+          then be flooded throughout the overlay network, creating a copy at all peers.
+          Before using a public key, peers check if that key has been revoked.
+          All names that involve delegation via a revoked zone will then fail to
+          resolve. Peers always automatically check for the existence of a revocation
+          message when resolving names.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Could the signing algorithm of GNS be upgraded in the future?") }}</h3>
+          <p>
+          {% trans %}
+          A: Yes. In our efforts to standardize GNS, we have already modified the protocol
+          to support alternative delegation records.
+          <br>
+          <br>
+          Naturally, deployed GNS implementations would have to be updated to support
+          the new signature scheme. The new scheme can then be run in parallel with
+          the existing system by using a new record type to indicate the use of a
+          different cipher system.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How can a GNS zone maintain several name servers, e.g. for load balancing?") }}</h3>
+          <p>
+          {% trans %}
+          A: We don't expect this to be necessary, as GNS records are stored (and
+          replicated) in the R5N DHT. Thus the authority will typically not be contacted
+          whenever clients perform a lookup. Even if the authority goes (temporarily)
+          off-line, the DHT will cache the records for some time. However, should having
+          multiple servers for a zone be considered truly necessary, the owner of the
+          zone can simply run multiple peers (and share the zone's key and database
+          among them).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why do you believe it is worth giving up unique names for censorship resistance?") }}</h3>
+          <p>
+          {% trans %}
+          A: The GNU Name system offers an alternative to DNS that is censorship
+          resistant. As with any security mechanism, this comes at a cost (names are not
+          globally unique). To draw a parallel, HTTPS connections use more bandwidth and
+          have higher latency than HTTP connections. Depending on your application,
+          HTTPS may not be worth the cost. However, for users that are experiencing
+          censorship (or are concerned about it), giving up globally unique names may
+          very well be worth the cost. After all, what is a &quot;globally&quot; unique
+          name worth, if it does not resolve?
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why do you say that DNS is 'centralized' and 'distributed'?") }}</h3>
+          <p>
+          {% trans %}
+          A: We say that DNS is 'centralized' because it has a central component /
+          central point of failure --- the root zone and its management by IANA/ICANN.
+          This centralization creates vulnerabilities. For example, the US government
+          was able to reassign the management of the country-TLDs of Afganistan and Iraq
+          during the wars at the beginning of the 21st century.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS protect against layer-3 censorship?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNS does not directly help with layer-3 censorship, but it does help
+          indirectly in two ways:
+          <ol>
+            <li> Many websites today use virtual hosting, so blocking a particular IP
+              address causes much more collateral damage than blocking a DNS name.
+              It thus raises the cost of censorship.</li>
+            <li> Existing layer-3 circumvention solutions (such as Tor) would benefit from
+              a censorship resistant naming system. Accessing Tor's &quot;.onion&quot;
+              namespace currently requires users to use unmemorable cryptographic
+              identifiers. With nicer names, Tor and tor2web-like services would be even
+              easier to use.
+          </ol>
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Does GNS work with search engines?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNS creates no significant problems for search engines, as they can use GNS
+          to perform name resolution as well as any normal user. Naturally, while we
+          typically expect normal users to install custom software for name resolution,
+          this is unlikely to work for search engines today. However, the DNS2GNS
+          gateway allows search engines to use DNS to resolve GNS names, so they can
+          still index GNS resources. However, as using DNS2GNS gateways breaks the
+          cryptographic chain of trust, legacy search engines will obviously not obtain
+          censorship-resistant names.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS compare to the Unmanaged Internet Architecture (UIA)?") }}</h3>
+          <p>
+          {% trans %}
+          A: UIA and GNS both share the same basic naming model, which actually
+          originated with Rivest's SDSI. However, UIA is not concerned about integration
+          with legacy applications and instead focuses on universal connectivity between
+          a user's many machines. In contrast, GNS was designed to interoperate with DNS
+          as much as possible, and to also work as much as possible with the existing
+          Web infrastructure. UIA is not at all concerned about legacy systems (clean
+          slate).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?") }}</h3>
+          <p>
+          {% trans %}
+          A: First of all, in GNS you can explicitly see the trust chain, so you know if
+          a name you are resolving belongs to a friend, or a friend-of-a-friend, and can
+          thus decide how much you trust the result. Naturally, the trusted-computing
+          base (TCB) can become arbitrarily large this way --- however, given the name
+          length restriction, for an individual name it is always less than about 128
+          entities.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS handle SRV/TLSA records where service and protocol are part of the domain name?") }}</h3>
+          <p>
+          {% trans %}
+          A: When GNS splits a domain name into labels for resolution, it detects the
+          &quot;_Service._Proto&quot; syntax, converts &quot;Service&quot; to the
+          corresponding port number and &quot;Proto&quot; to the corresponding protocol
+          number. The rest of the name is resolved as usual. Then, when the result is
+          presented, GNS looks for the GNS-specific &quot;BOX&quot; record type.
+          A BOX record is a record that contains another record (such as SRV or TLSA
+          records) and adds a service and protocol number (and the original boxed record
+          type) to it.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="errors" class="subnav-anchor"></a>{{ _("Error messages") }}</h2>
+        <section>
+          <h3>{{ _("I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. Should I worry?") }}</h3>
+          <p>
+          {% trans %}
+          A: Right now, this is expected and a known cause for high
+          latency in GNUnet.  We have started a major rewrite to address
+          this and other problems, but until the Transport Next
+          Generation (TNG) is ready, these warnings are expected.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Error opening `/dev/net/tun': No such file or directory?") }}</h3>
+          <p>
+          {% trans %}
+          A: If you get this error message, the solution is simple. Issue the following
+          commands (as root) to create the required device file
+          {% endtrans %}
+          <code class="block">
+            # mkdir /dev/net<br>
+            # mknod /dev/net/tun c 10 200<br>
+          </code>
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("'iptables: No chain/target/match by that name.' (when running gnunet-service-dns)?") }}</h3>
+          <p>
+          {% trans %}
+          A: For GNUnet DNS, your iptables needs to have &quot;owner&quot; match
+          support.
+          This is accomplished by having the correct kernel options. Check if your
+          kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or 'm' (and the
+          module is loaded).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("'Timeout was reached' when running PT on Fedora (and possibly others)?") }}</h3>
+          <p>
+          {% trans %}
+          A: If you get an error stating that the VPN timeout was reached, check if your
+          firewall is enabled and blocking the connections.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'") }}</h3>
+          <p>
+          {% trans %}
+          A: This error usually occurs when your linker fails to locate one of GNUnet's
+          libraries. This can have two causes. First, it is theoretically possible that
+          the library is not installed on your system; however, if you compiled GNUnet
+          the normal way and/or used a binary package, that is highly unlikely. The more
+          common cause is that you installed GNUnet to a directory that your linker
+          does not search. There are several ways to fix this that are described below.
+          If you are 'root' and you installed to a system folder (such as /usr/local),
+          you want to add the libraries to the system-wide search path. This is done by
+          adding a line "/usr/local/lib/" to /etc/ld.so.conf and running "ldconfig".
+          If you installed GNUnet to /opt or any other similar path, you obviously have
+          to change "/usr/local" accordingly.
+          If you do not have 'root' rights or if you installed GNUnet to say
+          "/home/$USER/", then you can explicitly tell your linker to search a
+          particular directory for libraries using the "LD_LIBRARY_PATH" environment
+          variable. For example, if you configured GNUnet using a prefix of
+          "$HOME/gnunet/" you want to run:
+          {% endtrans %}
+          </p>
+          <code>
+            $ export LD_LIBRARY_PATH=$HOME/gnunet/lib:$LD_LIBRARY_PATH<br>
+            $ export PATH=$HOME/gnunet/bin:$PATH
+          </code>
+          </p>
+          {% trans %}
+          to ensure GNUnet's binaries and libraries are found. In order to avoid having to do so each time, you can add the above lines (without the "$") to your .bashrc or .profile file. You will have to logout and login again to have this new profile be applied to all shells (including your desktop environment).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What error messages can be ignored?") }}</h3>
+          <p>
+          {% trans %}
+          A: Error messages flagged as "DEBUG" should be disabled in binaries
+          built for end-users and can always be ignored.
+          Error messages flagged as "INFO" always refer to harmless events that
+          require no action. For example, GNUnet may use an INFO message to
+          indicate that it is currently performing an expensive operation that
+          will take some time. GNUnet will also use INFO messages to display
+          information about important configuration values.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="fs" class="subnav-anchor"></a>{{ _("File-sharing")}}</h2>
+        <section>
+          <h3>{{ _("How does GNUnet compare to other file-sharing applications?") }}</h3>
+          <p>
+          {% trans %}
+          A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most
+          other P2P networks, GNUnet was designed with security in mind as the
+          highest priority. We intend on producing a network with comprehensive
+          security features. Many other P2P networks are open to a wide variety
+          of attacks, and users have little privacy. GNUnet is also Free
+          Software and thus the source code is available, so you do not have to
+          worry about being spied upon by the software. The following table
+          summarises the main differences between GNUnet and other systems.
+          The information is accurate to the best of our knowledge.
+          The comparison is difficult since there are sometimes differences
+          between various implementations of (almost) the same protocol.
+          In general, we pick a free implementation as the reference
+          implementation since it is possible to inspect the free code. Also,
+          all of these systems are changing over time and thus the data below
+          may not be up-to-date. If you find any flaws, please let us know.
+          Finally, the table is not saying terribly much (it is hard to compare
+          these systems this briefly), so if you want the real differences, read
+          the research papers (and probably the code).
+          {% endtrans %}
+          </p>
+          <table width="90%" border="0" cellpadding="0" cellspacing="0"><tbody><tr><th >Network</th>
+                <th ><a>GNUnet FS</a></th>
+                <th ><a>OneSwarm</th>
+                <th ><a>Napster</th>
+                <th ><a>Direct Connect</th>
+                <th ><a>FastTrack</th>
+                <th ><a>eDonkey</th>
+                <th ><a>Gnutella</th>
+                <th ><a>Freenet</th>
+              </tr><tr><th >Distributed Queries</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >hubs</td>
+                <td >super-peers</td>
+                <td >DHT (eMule)</td>
+                <td >yes</td>
+                <td >yes</td>
+              </tr><tr><th >Multisource Download</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+              </tr><tr><th >Economics</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+              </tr><tr><th >Anonymity</th>
+                <td >yes</td>
+                <td >maybe</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+              </tr><tr><th >Language</th>
+                <td >C</td>
+                <td >Java</td>
+                <td >often C</td>
+                <td >C++</td>
+                <td >C</td>
+                <td >C++</td>
+                <td >often C</td>
+                <td >Java</td>
+              </tr><tr><th >Transport Protocol</th>
+                <td >UDP, TCP, SMTP, HTTP</td>
+                <td >TCP</td>
+                <td >TCP</td>
+                <td >TCP?</td>
+                <td >UDP, TCP</td>
+                <td >UDP, TCP</td>
+                <td >TCP</td>
+                <td >TCP</td>
+              </tr><tr><th >Query Format (UI)</th>
+                <td >keywords / CHK</td>
+                <td >filename / SHA?</td>
+                <td >keywords</td>
+                <td >filename, THEX</td>
+                <td >filename, SHA</td>
+                <td >filename, MD4?</td>
+                <td >filename, SHA</td>
+                <td >secret key, CHK</td>
+              </tr><tr><th >Routing</th>
+                <td >dynamic (indirect, direct)</td>
+                <td >static (indirect, direct)</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always indirect</td>
+              </tr><tr><th >License</th>
+                <td >GPL</td>
+                <td >GPL</td>
+                <td >GPL (knapster)</td>
+                <td >GPL (Valknut)</td>
+                <td >GPL (giFT)</td>
+                <td >GPL (eMule)</td>
+                <td >GPL (gtk-gnutella)</td>
+                <td >GPL</td>
+              </tr></tbody>
+          </table>
+          <p>
+          {% trans %}
+          Another important point of reference are the various anonymous
+          peer-to-peer networks.
+          Here, there are differences in terms of application domain and how
+          specifically anonymity is achieved.
+          Anonymous routing is a hard research topic, so for a superficial
+          comparison like this one we focus on the latency.
+          Another important factor is the programming language.
+          Type-safe languages may offer certain security benefits; however, this may come at the cost of significant increases in resource consumption which in turn may reduce anonymity.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Are there any known attacks (on GNUnet's file-sharing application)?") }}</h3>
+          <p>
+          {% trans %}
+          A: Generally, there is the possibility of a known plaintext attack on
+          keywords, but since the user has control over the keywords that are
+          associated with the content he inserts, the user can take advantage of
+          the same techniques used to generate reasonable passwords to defend
+          against such an attack. In any event, we are not trying to hide
+          content; thus, unless the user is trying to insert information into
+          the network that can only be shared with a small group of people,
+          there is no real reason to try to obfuscate the content by choosing a
+          difficult keyword anyway.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What do you mean by anonymity?") }}</h3>
+          <p>
+          {% trans %}
+          A: Anonymity is the lack of distinction of an individual from a
+          (large) group. A central goal for anonymous file-sharing in GNUnet is
+          to make all users (peers) form a group and to make communications in
+          that group anonymous, that is, nobody (but the initiator) should be
+          able to tell which of the peers in the group originated the message.
+          In other words, it should be difficult to impossible for an adversary
+          to distinguish between the originating peer and all other peers.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What does my system do when participating in GNUnet file sharing?") }}</h3>
+          <p>
+          {% trans %}
+          A: In GNUnet you set up a node (a peer). It is identified by an ID (hash
+          of its public key) and has a number of addresses it is reachable by
+          (may have no addresses, for instance when it's behind a NAT).
+          You specify bandwidth limits (how much traffic GNUnet is allowed to
+          consume) and datastore quote (how large your on-disk block storage is)
+          . Your node will then proceed to connect to other nodes, becoming
+          part of the network.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="contrib" class="subnav-anchor"></a>{{ _("Contributing")}}</h2>
+        <section>
+          <h3>{{ _("How can I help translate this webpage into other languages?") }}</h3>
+          <p>
+          {% trans %}
+          A: First, you need to register an account with our weblate system.
+          Please send an e-mail with the desired target language to
+          translators@gnunet.org or ask for help on the #gnunet chat on
+          irc.freenode.net. Typically someone with sufficient permissions will
+          then grant you access. Naturally, any abuse will result in the loss
+          of permissions.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("I have some great idea for a new feature, what should I do?") }}</h3>
+          <p>
+          {% trans %}
+          A: Sadly, we have many more feature requests than we can possibly
+          implement. The best way to actually get a new feature implemented is
+          to do it yourself --- and to then send us a patch.
+          {% endtrans %}
+          </p>
+        </section>
+      </article>
+    </div> <!-- col -->
+  </div> <!-- row-->
+  <!--
+    <h2>{{ ("Q?") }}</h2>
+    <h2>{{ ("Q?") }}</h2>
+    <h2>{{ ("Q?") }}</h2>
+  -->
 </div>
 {% endblock body_content %}
diff --git a/template/glossary.html.j2 b/template/glossary.html.j2
index 789074e9..59b9276f 100644
--- a/template/glossary.html.j2
+++ b/template/glossary.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/gns.html.j2 b/template/gns.html.j2
index 114e0d21..b824ae35 100644
--- a/template/gns.html.j2
+++ b/template/gns.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/gnurl.html.j2 b/template/gnurl.html.j2
index 5556bd17..d0e1bb99 100644
--- a/template/gnurl.html.j2
+++ b/template/gnurl.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
  <article class="container">
    <header>
      <h1>gnurl (libgnurl)</h1>
diff --git a/template/gsoc-2018-gnunet-webui.html.j2 b/template/gsoc-2018-gnunet-webui.html.j2
index ec65ee5b..69feea8c 100644
--- a/template/gsoc-2018-gnunet-webui.html.j2
+++ b/template/gsoc-2018-gnunet-webui.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
  <article class="d-flex flex-column p-2 bd-highlight">
    <div class="container">
      <div class="text-center">
diff --git a/template/gsoc.html.j2 b/template/gsoc.html.j2
index 6fdc58be..d324b7b2 100644
--- a/template/gsoc.html.j2
+++ b/template/gsoc.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -9,7 +10,7 @@
  <div class="row">
    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
-      <a class="nav-link" href="#current">{{ _("Ideas 2021") }}</a>
+      <a class="nav-link" href="#current">{{ _("Ideas 2024") }}</a>
      <!--<a class="nav-link" href="#past">{{ _("Past projects") }}</a>-->
      <a class="nav-link" href="#finished">{{ _("Finished projects") }}</a>
      </nav>
@@ -20,13 +21,13 @@
        <p>
        {% trans %}
          As a GNU project, GNUnet has participated in the Google Summer of Code (GSoC) for a number of years. This page lists all current, past, and finished projects.
-          If you want to participate and apply for any of the ideas for 2020 below or any past project which is not yet finished (or even your own idea), please contact us either in IRC or mailing list.
+          If you want to participate and apply for any of the ideas for 2020 below or any past project which is not yet finished (or even your own idea), please contact us on the mailing list.
        {% endtrans %}
        </p>
      </section>
-      <h2><a name="current" class="subnav-anchor"></a>{{ _("Ideas 2021") }}</h2>
+      <h2><a name="current" class="subnav-anchor"></a>{{ _("Ideas 2024") }}</h2>
      <section>
        <h4>Transport Next Generation (TNG): Communicator plugins</h4>
@@ -54,56 +55,213 @@
            We expect that this project can be worked on by multiple students
            as there are a lot of protocols to choose from.
+            A QUIC communicator has been written as part of GSoC 2023.
            The tasks would consist of:
            <ol>
              <li>Deciding which communicators to implement.</li>
              <li>Test the communicators.</li>
              <li>Documentation.</li>
            </ol>
+            Expected outcome:
+            <ol>
+              <li>At least one new communicator.</li>
+              <li>Documentation of communicator protocol and how to use.</li>
+            </ol>
            Advantageous skills/languages/frameworks:
            <ol>
              <li>C</li>
-              <li>Knowledge of HTTPS, QUIC, Bluetooth or WiFi.</li>
+              <li>Knowledge of HTTPS, Bluetooth or WiFi.</li>
            </ol>
            <br/>
-            <strong>Difficulty:</strong> Average, but depends on selected protocols.
+            <strong>Difficulty:</strong> Average, but depends on selected protocols and library.
+            <br/>
+            <strong>Size:</strong> 175h
            <br/>
            <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt
          {% endtrans %}
        </p>
      </section>
+      <!-- Single-process peer -->
+      <section>
+        <h4>Single-process peer</h4>
+        <p>
+          {% trans %}
+            For special platforms such as Android, GNUnet must be usable
+            as a single-peer shared library.
+            Since GNUnet's design fundamentally revolves around a multi-process
+            model that communicate via IPCs, this requires a major change
+            in how GNUnet processes are instantiated.
+            A lot of progress in this direction has already been made but
+            some issues still remain.
+            The project tasks are to:
+            <ol>
+              <li>Get familiar with the GNUnet scheduler and envisioned single-process architecture.</li>
+              <li>Implement the single-process scheduler and main loop.</li>
+              <li>Demonstrate the functioning of this change (e.g. in a simple Android App)</li>
+            </ol>
+            Expected outcome:
+            <ol>
+              <li>A new single-process shared library to link against.</li>
+              <li>Documentation on when and how to build the single-process library.</li>
+              <li>A demo application.</li>
+            </ol>
+            Advantageous skills/languages/frameworks:
+            <ol>
+              <li>C</li>
+              <li>Socket programming</li>
+              <li>Scheduler and IO</li>
+            </ol>
+            <br/>
+            <strong>Difficulty:</strong> Difficult
+            <br/>
+            <strong>Size:</strong> 175h
+            <br/>
+            <strong>Mentors:</strong> Martin Schanzenbach
+          {% endtrans %}
+        </p>
+      </section>
+      <!-- Pluggable REST service components -->
      <section>
-        <h4>REST: Multi-user support</h4>
+        <h4>Pluggable REST service components</h4>
        <p>
          {% trans %}
-            The REST API currently only supports a single user system.
+            In the process of supporting a single-process GNUnet peer,
-            This is an issue as on multi-user systems, access control
+            the subsystem REST plugins have been consolidated into a single,
-            must be enfoced on a per-user basis.
+            large REST server that depends on all subsystems.
-            In this project, the REST service must be extended to
+            In this work, the student should define and implement a new architure
-            support user authentication.
+            that runs each subsystem's REST interface in its own service,
-            This includes the correct handling of user context switches.
+            thus making the REST service more resilient and easier to extend.
+            The planned projects tasks are to:
            <ol>
-              <li>Implement user authentication.</li>
+              <li>Get familiar with the existing REST service.</li>
-              <li>Test the access control.</li>
+              <li>Plan a multi-processes architecture for REST services.</li>
-              <li>Document the changes to the REST API.</li>
+              <li>Test and document the use of the new architecture / REST service layer.</li>
+            </ol>
+            Expected outcome:
+            <ol>
+              <li>A new multi-process REST service architecture.</li>
+              <li>The current REST service is modified or replaced with a multi-process service per subsystem.</li>
+              <li>Architecture and usage documentation.</li>
            </ol>
            Advantageous skills/languages/frameworks:
            <ol>
              <li>C</li>
-              <li>Knowledge of user authentication subsystems on Linux/Unix.</li>
+              <li>Socket programming</li>
-              <li>REST/HTTP Authentication methods</li>
            </ol>
            <br/>
-            <strong>Difficulty:</strong> Beginner
+            <strong>Difficulty:</strong> Medium
+            <br/>
+            <strong>Size:</strong> 175h
            <br/>
            <strong>Mentors:</strong> Martin Schanzenbach
          {% endtrans %}
        </p>
      </section>
+      <!-- GTK4 upgrade of gnunet-gtk -->
+      <section>
+        <h4>gnunet-gtk gtk4 upgrade</h4>
+        <p>
+          {% trans %}
+            Our GTK interface for GNUnet is written using libglade and Gtk.
+            It is currently designed and compatible with Gtk+3 with already possibly including a variety of deprecated functions.
+            In this project the requirements for a Gtk4 migration shall be worked out and the codebase migrated to the most recent stable Gtk4 release.
+            The difficulty of this project largely depends on the students
+            proficiency with build tools and Gtk.
+            There non-exhaustive task list would be:
+            <ol>
+              <li>Get familiar with the existing gnunet-gtk architecture.</li>
+              <li>Get familiar with Gtk4 and work out a migration path.</li>
+              <li>Migrate gnunet-gtk to gtk4.</li>
+              <li>(Optional) Ad-hoc UI improvements where applicable</li>
+            </ol>
+            Advantageous skills/languages/frameworks:
+            <ol>
+              <li>C</li>
+              <li>Gtk</li>
+              <li>User interfaces</li>
+            </ol>
+            <br/>
+            <strong>Difficulty:</strong> Medium
+            <br/>
+            <strong>Size:</strong> 350h
+            <br/>
+            <strong>Mentors:</strong> Martin Schanzenbach
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>Integration of GNU Anastasis into the GNU Taler wallet</h4>
+        <p>
+          {% trans %}
+          The goal of this project is to enable users to store their GNU Taler wallet backup encryption keys in the GNU Anastasis distributed key backup and recovery system, and to use GNU Taler to pay GNU Anastasis service providers for key storage and recovery. The project will focus on implementing the GNU Anastasis user interface on Android inspired by the existing Gtk+ and WebUI and integrating the result with the rest of the GNU Taler Android App.
+          {% endtrans %}
+        <p>
+          {% trans %}
+            <strong>Mentors:</strong> Christian Grothoff (GNU Anastasis) and Florian Dold (GNU Taler)
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Required Skills: Android UI development
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Duration: 350h
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Difficulty level: medium
+          {% endtrans %}
+        </p>
+      </section>
+      <!-- Past projects: Previously proposed, but left unfinished. Inspiration for students. -->
+      <!--<h2><a name="past" class="subnav-anchor"></a>{{ _("Past projects") }}</h2>
+      <p>
+        Past projects: Previously proposed, but left unfinished. Inspiration for students.
+      </p>
+      <section>
+        <h4>Rust templates for GNUnet services</h4>
+        <p>
+          {% trans %}
+          The goal is to either build upon the (outdated) <a href="https://github.com/canndrew/gnunet-rs">GNUnet Rust
+          bindings</a> or to follow the path of <a href="GNUnet Go">https://github.com/bfix/gnunet-go</a>
+          which tries to reimplement most of the GNUnet stack.
+          The end result should be an extension template for GNUnet in the form
+          of the existing <a href="https://git.gnunet.org/gnunet-ext.git/">C template</a>
+          which allows to quickly start implementing services and libraries
+          for GNUnet.
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            <strong>Mentors:</strong> Martin Schanzenbach
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Required Skills: Solid knowledge of Rust and ideally asynchronuous IO.
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Duration: 350h
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Difficulty level: medium
+          {% endtrans %}
+        </p>
+      </section>
      <section>
        <h4>re:claimID/GNUnet Browser Plugin</h4>
@@ -180,42 +338,6 @@
          {% endtrans %}
        </p>
      </section>
-      <section>
-        <h4>Rust templates for GNUnet services</h4>
-        <p>
-          {% trans %}
-          The goal is to either build upon the (outdated) <a href="https://github.com/canndrew/gnunet-rs">GNUnet Rust
-          bindings</a> or to follow the path of <a href="GNUnet Go">https://github.com/bfix/gnunet-go</a>
-          which tries to reimplement most of the GNUnet stack.
-          The end result should be an extension template for GNUnet in the form
-          of the existing <a href="https://git.gnunet.org/gnunet-ext.git/">C template</a>
-          which allows to quickly start implementing services and libraries
-          for GNUnet.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            <strong>Mentors:</strong> Martin Schanzenbach
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            Required Skills: Solid knowledge of Rust and ideally asynchronuous IO.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            Difficulty level: medium
-          {% endtrans %}
-        </p>
-      </section>
-      <!-- Past projects: Previously proposed, but left unfinished. Inspiration for students. -->
-      <!--<h2><a name="past" class="subnav-anchor"></a>{{ _("Past projects") }}</h2>
-      <p>
-        Past projects: Previously proposed, but left unfinished. Inspiration for students.
-      </p>
            <section>
        <h4>Android Port</h4>
        <p>
@@ -234,6 +356,11 @@
        </p>
        <p>
          {% trans %}
+            Duration: 350h
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
            <strong>Mentors:</strong> <a href="https://www.goebel-consult.de/">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff
          {% endtrans %}
        </p>
diff --git a/template/index.html.j2 b/template/index.html.j2
index 6bc85b2f..50aa4d6e 100644
--- a/template/index.html.j2
+++ b/template/index.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <!-- Jumbotron -->
 <div>
  <div class="container">
@@ -10,8 +11,9 @@
    </div>
    <div class="container text-center">
-      <img src="{{ url_static('images/gnunet-logo-dark-text.png') }}"  alt="GNUnet" />
+    <img src="{{ url_static('images/gnunet-logo.svg') }}"  alt="GNUnet" />
-    </div>
+    <!--  <a class="nav-link" href="https://www.gnu.org/gnu40"><img src="https://www.gnu.org/gnu40/GNU40_badge-sm.png" alt="[ Celebrate 40 years of GNU! ]" /></a>-->
+      </div>
  </div>
 </div>
@@ -26,7 +28,7 @@
        <h2>{{ _("Latest news") }}</h2>
        <p>
        {% for item in newsdata[:3] %}
-        <a class="link" href="news/{{ item['page'] }}" title="{{ item['date']}}">{{ item['date'] }}: {{ item['title'] }}</a><br/>
+        <a class="link" href="{{ url_localized('news/' + item['page']) }}" title="{{ item['date']}}">{{ item['date'] }}: {{ item['title'] }}</a><br/>
        {% endfor %}
        <br/>
        <a class="link" href="{{ url_localized('news/index.html')}}">{{ _("Older news entries") }}</a>
@@ -226,6 +228,53 @@
      <div class="col-lg-2"></div>
      <div class="col-lg-6">
        <section>
+        <h2>{{ _("The state of the art is inefficient") }}</h2>
+        <p>
+          {% trans %}
+          The ongoing hype around distributed ledgers and blockchains
+          is detrimental to the health of our planet.
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+      <div class="col-lg-3 homepageicon">
+        <i class="fas fa-industry"></i>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2 homepageicon">
+        <span class="fas fa-globe-europe"></span>
+      </div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Sustainability") }}</h2>
+        <p>
+        {% trans url=url_localized('news/2021-05-DISSENS.html') %}
+        GNUnet does not require a decentralized, public ledger.
+        This eliminates the need for wasteful, continuous consensus
+        mechanisms, which do not scale and are ecologically unsustainable.
+        GNUnet and its applications employ decentralization only
+        <a href="{{ url }}"> where it
+        provides the most value and use more efficient technology stacks where
+        needed</a>.
+          {% endtrans %}
+        </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
        <h2>{{ _("Decentralization is the key, but hard") }}</h2>
        <p>
diff --git a/template/install-on-archpi.html.j2 b/template/install-on-archpi.html.j2
index 66e904b2..72d2b079 100644
--- a/template/install-on-archpi.html.j2
+++ b/template/install-on-archpi.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/install-on-debian9.html.j2 b/template/install-on-debian9.html.j2
index 2a3cde03..b867ab8a 100644
--- a/template/install-on-debian9.html.j2
+++ b/template/install-on-debian9.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/install-on-macos.html.j2 b/template/install-on-macos.html.j2
index e97efd75..b9e14836 100644
--- a/template/install-on-macos.html.j2
+++ b/template/install-on-macos.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -164,7 +165,7 @@ vpn (gnunet-service-vpn)
  <p>
  You might see configure failing telling you that it ``cannot run C compiled programs.''.
  In this case, you might need to open/run Xcode once and you will be prompted to
-  install additonal packages.
+  install additional packages.
  Then, you might have to manually install the command line tools from here https://developer.apple.com/download/more/ (you need an Apple ID for this).
  Install those and execute
  </p>
diff --git a/template/install-on-netbsd.html.j2 b/template/install-on-netbsd.html.j2
index b36eaa22..0370b29d 100644
--- a/template/install-on-netbsd.html.j2
+++ b/template/install-on-netbsd.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/install-on-openwrt.html.j2 b/template/install-on-openwrt.html.j2
index 7ea7f7a3..5cff8461 100644
--- a/template/install-on-openwrt.html.j2
+++ b/template/install-on-openwrt.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/install-on-ubuntu1804.html.j2 b/template/install-on-ubuntu1804.html.j2
index 94ea5cb2..19a507f6 100644
--- a/template/install-on-ubuntu1804.html.j2
+++ b/template/install-on-ubuntu1804.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
diff --git a/template/install.html.j2 b/template/install.html.j2
index 2fccfd3c..2c0093e7 100644..100755
--- a/template/install.html.j2
+++ b/template/install.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -7,13 +8,11 @@
  </header>
  <div class="row container justify-content-center">
-    <div class="alert" style="background-color: #419edb;">
+    <div class="alert alert-info">
-      <div class="alert-content">
 {% trans %}
          Notice: GNUnet is still undergoing major development. It is
          largely <i>not yet ready</i> for usage beyond developers.
 {% endtrans %}
-      </div>
    </div>
 {% trans %}
 <p>Please be aware that this project is still in an early alpha
@@ -31,13 +30,18 @@ If you have any queries about the installation or the usage, please <a href="eng
    We recommend to use binary packages provided by the package manager integrated
    within your Operating System. GNUnet is reportedly available for at least:
    <ul>
-      <li><a href="https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet">Alpine</a></li>
+      <li><a href="https://pkgs.alpinelinux.org/package/edge/community/x86_64/gnunet">Alpine</a></li>
-      <li><a href="https://www.archlinux.org/packages/community/x86_64/gnunet/">Arch</a></li>
+      <li><a href="https://aur.archlinux.org/packages/gnunet/">Arch (AUR)</a></li>
      <li><a href="https://packages.debian.org/search?keywords=gnunet">Debian</a></li>
-      <li><a href="https://copr.fedorainfracloud.org/coprs/yosl/gnunet/">Fedora (Copr)</a></li>
+      <li>
+        <a href="https://copr.fedorainfracloud.org/coprs/schanzen/gnunet/package/gnunet/">Fedora (copr)</a>:
+        <code class="block">
+          # dnf copr enable schanzen/gnunet
+        </code>
+      </li>
      <li><a href="https://guix.gnu.org/en/packages/G/">Guix</a></li>
      <li><a href="https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.rb">Homebrew</a></li>
-      <li><a href="https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-unstable&query=gnunet">NixOS</a></li>
+      <li><a href="https://search.nixos.org/packages?from=0&size=50&sort=relevance&query=gnunet">NixOS</a></li>
      <li><a href="install-on-openwrt.html">OpenWrt</a></li>
    </ul>
    If GNUnet is available for your Operating System and it is missing,
@@ -46,12 +50,12 @@ If you have any queries about the installation or the usage, please <a href="eng
    get in touch with us at gnunet-developers@gnu.org if you require
    help with this job.
-    If you were using an Operating System with the Alpine package manager,
+    If you were using an Operating System with the APT package manager,
    GNUnet could be installed as simple as:
    {% endtrans %}
  </p>
  <code class="block">
-    $ apk add gnunet
+    $ apt-get install gnunet
  </code>
  <p>
   Please beware that some distributions may include outdated GNUnet packages!
@@ -96,11 +100,11 @@ If you have any queries about the installation or the usage, please <a href="eng
  </div>
  <p>
   {% trans %}
-   Alternatively, get the sources from git by entering:
+   To compile gnunet from the git source you can do so by entering:
   {% endtrans %}
  </p>
  <code class="block">
-    $ git clone https://gnunet.org/git/gnunet.git
+    $ git clone https://git.gnunet.org/git/gnunet.git
  </code>
  <p>
   {% trans %}
@@ -153,15 +157,15 @@ If you have any queries about the installation or the usage, please <a href="eng
 <!--
  <div class="row container justify-content-center text-center">
    <div class="col-md">
-      <p><a href="install-on-ubuntu1804.html"><img src="{{ url('static/images/ubuntu-logo32.png') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-ubuntu1804.html"><img src="{{ url('images/ubuntu-logo32.png') }}" class="distro-logo"></a></p>
      <h3>Ubuntu 18.04</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-debian9.html"><img src="{{ url('static/images/debian-logo.svg') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-debian9.html"><img src="{{ url('images/debian-logo.svg') }}" class="distro-logo"></a></p>
      <h3>Debian 9</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-netbsd.html"><img src="{{ url('static/images/NetBSD_Logo.svg') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-netbsd.html"><img src="{{ url('images/NetBSD_Logo.svg') }}" class="distro-logo"></a></p>
      <h3>NetBSD</h3>
    </div>
  </div>
@@ -171,15 +175,15 @@ If you have any queries about the installation or the usage, please <a href="eng
      <h1><a href="install-on-macos.html">Apple<br/>macOS</a></h1>
    </div>
    <div class="col-md">
-      <p><a href="install-on-archpi.html"><img src="{{ url('static/images/archlinux-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
+      <p><a href="install-on-archpi.html"><img src="{{ url('images/archlinux-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
      <h3>Arch Linux/Arch-Pi</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-openwrt.html"><img src ="{{ url('static/images/openwrt-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
+      <p><a href="install-on-openwrt.html"><img src ="{{ url('images/openwrt-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
      <h3>OpenWrt</h3>
    </div>
    <div class="col-md">
-      <p><a href="https://wiki.gentoo.org/wiki/Overlay:Youbroketheinternet"><img alt="gentoo linux" src ="{{ url('static/images/gentoo-logo.svg') }}" class="distro-logo" style="width:170px;height:auto"></a></p>
+      <p><a href="https://wiki.gentoo.org/wiki/Overlay:Youbroketheinternet"><img alt="gentoo linux" src ="{{ url('images/gentoo-logo.svg') }}" class="distro-logo" style="width:170px;height:auto"></a></p>
    </div>
  </div>
 -->
diff --git a/template/l2o/index.html.j2 b/template/l2o/index.html.j2
new file mode 100644
index 00000000..9ce82969
--- /dev/null
+++ b/template/l2o/index.html.j2
@@ -0,0 +1,272 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="#idea">{{ _("Project motivation") }}</a>
+      <a class="nav-link" href="#testframework">{{ _("New Test Framework") }}</a>
+      <a class="nav-link" href="#milestones">{{ _("Milestones") }}</a>
+      <a class="nav-link" href="#milestone1">{{ _("Milestone 1") }}</a>
+      <a class="nav-link" href="#milestone2">{{ _("Milestone 2") }}</a>
+      <a class="nav-link" href="#milestone3">{{ _("Milestone 3") }}</a>
+      <a class="nav-link" href="#milestone4">{{ _("Milestone 4") }}</a>
+      <a class="nav-link" href="#milestone5">{{ _("Milestone 5") }}</a>
+      <a class="nav-link" href="#milestone6">{{ _("Milestone 6") }}</a>
+      <a class="nav-link" href="#milestone7">{{ _("Milestone 7") }}</a>
+      <a class="nav-link" href="#milestone8">{{ _("Milestone 8") }}</a>
+      <a class="nav-link" href="#milestone9">{{ _("Milestone 9") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <section>
+        <p>
+        {% trans %}
+          This project was funded through the NGI Assure Fund, a fund established by <a href="https://nlnet.nl/project/GNUnet-L2/">NLnet</a>.</br>
+        {% endtrans %}
+        </p>
+      </section>
+      <h2><a name="idea" class="subnav-anchor"></a>{{ _("Project motivation") }}</h2></br>
+      <section>
+        <h4>The GNUnet transport subsystem</h4></br>
+        <p>
+          {% trans %}
+          The <a href="https://docs.gnunet.org/handbook/gnunet.html#TRANSPORT-Subsystem">current</a> GNUnet TRANSPORT architecture with its pluggable transport mechanism (TCP, UDP, HTTP(S) and other protocols) together with the ATS subsystem for bandwidth allocation and choosing plugins has several <a href="https://docs.gnunet.org/handbook/gnunet.html#TRANSPORT_002dNG-Subsystem">issues</a> with its design.
+          With the Layer-2-Overlay project we like to implement the <a href="https://docs.gnunet.org/handbook/gnunet.html#Design-goals-of-TNG">design goals</a> of the future GNUnet TRANSPORT Next Generation (TNG) subsystem.
+          One major change in the design is to separate the protocol plugins into processes (now called communicators) detached from the main transport service. Three communicators were already implemented (TCP, UDP and UNIX sockets).
+          The old transport code is hard to maintain, because it is cluttered with "manipulation" support code for TESTBED (the actual testing framework). Testing TRANSPORT is a hard task, especially with TESTBED which has its own design flaws, and test code which is very hard to read to get an idea what the test code is doing. Therefore the first task (milestone 1) is to implement a new testing framework which uses network namespaces to make testing of TNG much easier. Have a look into what is planed for Layer-2-Overlay in the <a href="#milestones">milestones</a>.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h2><a name="testframework" class="subnav-anchor"></a>{{ _("New Test Framwork") }}</h2></br>
+      <p>The new testing framework consists of two major parts. First the command style pattern borrowed from the GNU Taler project, second a network namespace setup, to have a suitable test setup for testing several network topologies with lossy connections, firewalls, etc..</p></br>
+      <h3><a name="cmd" class="subnav-anchor"></a>{{ _("Command Style Pattern") }}</h3></br>
+      
+      <section>
+        <p>
+          {% trans %}
+          The new style of writing tests in GNUnet is borrowed from the <a href="https://docs.taler.net/developers-manual.html#testing-library">GNU Taler testing library</a>. In <a href="#milestone1">milestone 1</a> we implemented commands to setup the <a href="#netjails">netjails</a>, the test environment for each peer, to start a single peers and sending a simple test message. Because some commands depend on other commands to be finished, and those commands are asynchronous, we needed additional functionality in the command interpreter library to block execution until some commands are finished (e.g. all peers needs to be running, before peers starting to send messages). For a detailed description have a look into the <a href="testng.html">testing ng documentation</a>.           
+            {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="netjails" class="subnav-anchor"></a>{{ _("Netjails") }}</h3></br>
+      
+      <section>
+        <p>
+          {% trans %}
+                  To do extensive testing of the new transport implementation one needs to simulate various network topologies to enable faking network characteristics like lossy connections or firewalls. To achieve this we are working with <a href="https://www.man7.org/linux/man-pages/man8/ip-netns.8.html">network namespace</a>. We have commands for starting and stopping network namespaces. Those commands are scripts, which are using several shell commands to setup the network namespace. A third script then is responsible for start a GNUnet helper. This helper can load plugins. Each plugin represents some test case. Per node in the network namespaces one helper is started, which means on each node is a local interpreter loop running. For a detailed description have a look into the <a href="testng.html">testing ng documentation</a>. 
+            {% endtrans %}
+        </p></br>
+      </section>
+      <h2><a name="milestones" class="subnav-anchor"></a>{{ _("Milestones") }}</h2></br>
+      <p>All milestones are finished.</p></br>
+      <h3><a name="milestone1" class="subnav-anchor"></a>{{ _("Milestone 1 Test Infrastructure and minimal Test Case") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+        The first subtask consists of implementing a framework for setting up VLANs between network namespaces and a framework to test communication between peers which are running in those VLANs. Finally a minimal Test Case will be implemented. Despite the fact that the transport service is already able to use several communicators (transport protocol implementations), it will only use the tcp communicator, not the unix socket nor the udp communicator, which already are in place and working.
+        <ul>    
+    <li>SUID helpers to setup network namespace and starting peers with network namespace.</li>
+    <li>Basic transport-level operations (get address, send, receive, connect).</li>
+    <li>Peers connected through test and transfer data.</li>
+    </ul></br>
+            {% endtrans %}
+        </p>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          First MVP which uses the TCP communicator to send messages between peers. The deliverable can be verified through out the specific test cases running in the GNUnet CI.
+          <a href="mile1.html">Details</a>
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone2" class="subnav-anchor"></a>{{ _("Milestone 2 Enhancing Test Framework") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+            To test more complex functionality we need to enhance the capabilities of the testing framework. Hooks for performance measurement will be implemented.
+            <ul>        
+    <li>Enhancing transport-level operations.</li>
+    <li>Block execution of commands at a peer. (Barriers).</li>
+    </ul>
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          Outcome of this deliverable are advanced test cases (again verifiable in the GNUnet continuous integration (CI)).
+<a href="mile2.html">Details</a>
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone3" class="subnav-anchor"></a>{{ _("Milestone 3 UDP integration") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+            With this subtask I will implement enhanced L2O features like using unidirectional transport protocols with backchannels. Addresses by which a peer can be reached can be delivered on handshake or by  UDP broadcast. With this milestone the transport service will be able to use more than one communicator (pluggable transport).
+            <ul>        
+    <li>unidirectional communication and backchannels.</li>
+    <li>UDP broadcast.</li>
+    </ul>
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4>
+        <p>
+          {% trans %}
+          The CI contains test cases which uses the UDP protocol to message between peers and to learn about “foreign” peers.
+          <a href="mile3.html">Details</a>
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone4" class="subnav-anchor"></a>{{ _("Milestone 4 Distance Vector") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+            In this subtask I will enhance connectivity to peers not directly connected. Therefore peers have to act as relay. To achieve this there is the distance vector protocol. The DV algorithm sends out so called learn messages to other peers. If those learn messages are coming back to the initiating peer via some other peer and the path does not return to any other peer we have a circle path. If there are bidirectional connections between peers somewhere in the DV path and the learn message comes back to a peer we call it inverse path.
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          The CI contains test cases with a setup of peers not connected directly. The test cases proof that each peer can reach any other peer. We have test cases for the circle path and for the inverse path.
+          <a href="mile4.html">Details</a>
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone5" class="subnav-anchor"></a>{{ _("Milestone 5 NAT Traversal") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            This subtask will make peers behind NAT reachable. Two simple traversal methods will be implemented.
+            <ul>
+    <li>NAT traversal via UpnPC.</li>
+    <li>Autonomous NAT Traversal using fake ICMP messages.</li>
+    </ul>
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+          The CI contains test case with a peer setup containing peer behind a NAT. The test cases 
+        proof that each peer can be reached, even if that peer is behind a NAT. The test case are       measuring the performance. This measurement is used to compare with the outcome of the  next milestone. This result of this milestone will be a first stable release. <a href="mile5.html">Details</a>
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone6" class="subnav-anchor"></a>{{ _("Milestone 6 Optimization") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            In this subtask I will implement algorithms (flow and congestion control, quality of service optimizations) which will select the optimal transport protocol for a given situation. 
+I will analyze potential performance gains by integrating libraries of the interpeer project. If the effort of integrating interpeer presumably would lead to better performance than other optimizations of the same amount of work, this integration is done.
+I will finish the project with a performance analysis to optimize the selection logic.
+       <ul>
+    <li>Queue management.
+    <li>Interpeer project synergy
+        <ol>
+        <li>Analysis of the interpeer project in regard to integrate it into GNUnet.</li>
+        <li>Optional integration into GNUnet, if it can be done at all and in a reasonable amount of work.</li>
+        </ol>
+    <li>Commands for performance measurement(s).</li>           
+    <li>Performance analysis.</li>
+    </ul>
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                The test cases in the CI are measuring the performance gains. This measurement can be compared with the measurement of milestone 5. Again one outcome of this milestone will be a stable release.<br/>
+      Documentation of the interpeer project analysis. More  <a href="mile6.html">Details</a>.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone7" class="subnav-anchor"></a>{{ _("Milestone 7 Removing deprecated code") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+             The code of the old transport API and of the ATS API will be removed from the code base. This is
+mainly the use of the API in the Core layer, and suggesting addresses to connect to other peers in
+all kinds of other GNUnet layers. Additionally all tests which rely on the removed code will be set
+inactive. All usages of the old APIs will be removed. If it is not much work to replace the old with the
+new API this will be done directly, otherwise there will be a TODO comment what needs to be doneto make that part of the code working again with the new code. Documentation of code that will be
+deleted without replacement, because the functionality is missing in the new API.  
+          {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                Removed APIs from code base, deactivated dependent tests and either documentation of what is
+necessary for the integration of the new API, or if the effort for this is as high as the documentation
+directly the implementation. More  <a href="mile7.html">Details</a>.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone8" class="subnav-anchor"></a>{{ _("Milestone 8 Make GNUnet start again") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+             All missing implementations of the new API will be finished, necessary to make GNUnet start and
+being usable for its basic functionality (DHT, GNS, CADET, FS, Messenger …). 
+          {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                GNUnet running with new API. More  <a href="mile8.html">Details</a>.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone9" class="subnav-anchor"></a>{{ _("Milestone 9 Testing and Fixing") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+             Because all integration tests are deactivated, and there are no resources to rewrite them at the
+time being, extensive manual testing and certainly bug fixing is necessary. 
+          {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                GNUnet release running with new API. More  <a href="mile9.html">Details</a>.
+          {% endtrans %}
+        </p><br/>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile1.html.j2 b/template/l2o/mile1.html.j2
new file mode 100644
index 00000000..f354d8e3
--- /dev/null
+++ b/template/l2o/mile1.html.j2
@@ -0,0 +1,136 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 1</h2>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Master Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/test_transport_api_cmd_simple_send.c</td><td width="60%" style="vertical-align: top;">Binary for starting the simple send test. Obsolete in current code base!</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/netjail_start.sh</td><td width="60%" style="vertical-align: top;">Script to setup the netjail topology. Will be execute by the following command. </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_netjail_start.c</td><td width="60%" style="vertical-align: top;">Command to create the netjail setup.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/netjail_exec.sh</td><td width="60%" style="vertical-align: top;">Script to execute a local test interpreter per node.  Will be execute by the following command.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_netjail_start_testsystem.c</td><td width="60%" style="vertical-align: top;">Command to start the helper processes.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_netjail_stop_testsystem.c</td><td width="60%" style="vertical-align: top;">Command to stop the helper processes.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/netjail_stop.sh</td><td width="60%" style="vertical-align: top;">Script to stop the netjail topology.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_netjail_stop.c</td><td width="60%" style="vertical-align: top;">Command to stop the test setup.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Local Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/gnunet-cmds-helper.c</td><td width="60%" style="vertical-align: top;">Helper to start the local interpreter loop.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/test_transport_plugin_cmd_simple_send.c</td><td width="60%" style="vertical-align: top;">Plugin which creates the cmds for the simple send test case.</td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_system_create.c</td><td width="60%" style="vertical-align: top;">Command to create a local test system.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/transport_api_cmd_start_peer.c</td><td width="60%" style="vertical-align: top;">Command to start a peer.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/transport_api_cmd_connecting_peers.c</td><td width="60%" style="vertical-align: top;"> Command to connect two peers.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td>src/transport/transport_api_cmd_send_simple.c</td><td width="60%" style="vertical-align: top;">Command to send a simple message from one peer to another.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/transport_api_cmd_stop_peer.c</td><td width="60%" style="vertical-align: top;">Command to stop a peer.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_system_destroy.c</td><td width="60%" style="vertical-align: top;">Command to destroy the local test system.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_local_test_finished.c</td><td>Command to send a message to the master loop, if the local loop has finished.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/test_transport_api2_tcp_node1.conf</td><td width="60%" style="vertical-align: top;">Configuration for the first node running during the simple send test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td  width="40%" style="vertical-align: top;">src/transport/test_transport_api2_tcp_node2.conf</td><td width="60%" style="vertical-align: top;">Configuration for the second node running during the simple send test case.</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile2.html.j2 b/template/l2o/mile2.html.j2
new file mode 100644
index 00000000..092995b9
--- /dev/null
+++ b/template/l2o/mile2.html.j2
@@ -0,0 +1,86 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 2</h2>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Master Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/test_transport_simple_send.sh</td><td width="60%" style="vertical-align: top;">Introduced scripts to start the tests. The script checks, if a kernel parameter is set to allow unprivileged users to                                                                   create network namespaces. The script than starts the following gerneric binary in a network namespace.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/test_transport_start_with_config.c</td><td width="60%" style="vertical-align: top;">A generic binary to start a test case which will be configured by a configuration file.</td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing.c</td><td width="60%" style="vertical-align: top;">Added code to read netjail topology from a file.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/topo.sh</td><td width="60%" style="vertical-align: top;">Script which reads the topology from a file for the use in the other netjail scripts.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">All already existing commands.</td><td width="60%" style="vertical-align: top;">All commands changed to work with the topology data.</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Local Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_send_peer_ready.c</td><td width="60%" style="vertical-align: top;">Command to send a message to the master loop if a peer has started in local loop.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/testing/testing_api_cmd_local_test_prepared.c</td><td width="60%" style="vertical-align: top;">Command to send a message to the master loop if a peer is ready to shutdown.</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/transport/transport_api_cmd_start_peer.c</td><td width="60%" style="vertical-align: top;">Command now uses a configuration template for the peer configuration.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">test_transport_simple_send_topo.conf</td><td width="60%" style="vertical-align: top;">Topology configuration file for the simple send test case.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile3.html.j2 b/template/l2o/mile3.html.j2
new file mode 100644
index 00000000..b4c93add
--- /dev/null
+++ b/template/l2o/mile3.html.j2
@@ -0,0 +1,115 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 3</h2>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Bug fixing") }}</h4>
+        <p>
+          {% trans %}
+          Some bugs in the tng service and communicator code which were found with new tests were fixed.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Master Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_udp_backchannel.sh</td><td width="55%" style="vertical-align: top;">Added script to start the udp backchannel test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_broadcast.sh</td><td width="55%" style="vertical-align: top;">Added script for the UDB broadcast test.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_string.sh</td><td width="55%" style="vertical-align: top;">Added script as an example to start a test with inline topology configuration string.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">All commands</td><td width="55%" style="vertical-align: top;">Changed code to handle strings with topology information.</td>
+                </tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/testing/netjail_start.sh</td><td width="55%" style="vertical-align: top;">Changed the netjail start script to configure port forwarding for specific protocols (tcp, udp).</td>
+                </tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/testing/netjail_*.sh</td><td width="40%" style="vertical-align: top;">Moved to contrib/netjail directory</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Local Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_plugin_cmd_simple_send_broadcast.c</td><td width="40%" style="vertical-align: top;">New plugin for the udp broadcast test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_plugin_cmd_udp_backchannel.c</td><td width="40%" style="vertical-align: top;">New plugin for the udp backchannel test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/transport_api_cmd_backchannel_check.c</td><td width="40%" style="vertical-align: top;">Command to check for a udp backchannel specific log entry.</td>
+                </tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/testing/testing_api_cmd_block_until_external_trigger.cc</td><td width="40%" style="vertical-align: top;">Command to block the local loop until triggered by a external signal.</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_broadcast_topo.conf</td><td width="40%" style="vertical-align: top;">Topology configuration for the broadcast test.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">test_transport_udp_backchannel_topo.conf</td><td width="40%" style="vertical-align: top;">Topology configuration file for the udp backchannel test case.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile4.html.j2 b/template/l2o/mile4.html.j2
new file mode 100644
index 00000000..7a54503e
--- /dev/null
+++ b/template/l2o/mile4.html.j2
@@ -0,0 +1,108 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 4</h2><br/>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("TNG Service") }}</h4><br/>
+        <p>
+          {% trans %}
+          <ul>
+                <li>Added caching for Core messages, if confirmed virtual link is missing.</li>
+                <li>Addd caching for DV forwarding, if confirmed virtual link is missing.</li>
+                <li>Fixed bugs in fragmentation logic.</li>
+                <li>Fixed bugs in fragmentation logic.</li>
+                <li>Fixed bugs in flow control logic.</li>
+                <li>Fixed Bug with lifetime of DV learn message. (Validation against replay attack still missing.)</li>
+                <li>Fixed Bug in rekeying logic of the TCP communicator</li>
+          </ul>
+          {% endtrans %}
+        </p>
+        <p>
+        Even more details in commits <a href='https://git.gnunet.org/gnunet.git/commit/?id=fc99f54070e04c043c14f2244f85833ecf6b00c4'>fc99f54070e04c043c14f2244f85833ecf6b00c4</a>, <a href='https://git.gnunet.org/gnunet.git/commit/?id=95a1edacccd9b3bf769a144a12d41946d0ac25dc'>95a1edacccd9b3bf769a144a12d41946d0ac25dc</a> and <a href='https://git.gnunet.org/gnunet.git/commit/?id=247230d737e3e4709392148bfabbde25871b6914'>247230d737e3e4709392148bfabbde25871b6914</a>
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Master Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_dv_inverse.sh</td><td width="55%" style="vertical-align: top;">Added script to start the inverse distance vector test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_dv_circle.sh</td><td width="55%" style="vertical-align: top;">Added script to start the circle distance vector test case.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Local Loop") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/transport_api_cmd_connecting_peers.c</td><td width="40%" style="vertical-align: top;">Added logic to handle counting additonal connection per peer.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_plugin_cmd_simple_send_dv.c</td><td width="40%" style="vertical-align: top;">Added plugin which creates the commands for the distance vector test cases.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_distance_vector_inverse_topo.conf</td><td width="40%" style="vertical-align: top;">Configuration for the DV inverse path test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_distance_vector_circle_topo.conf</td><td width="40%" style="vertical-align: top;">Configuration for the DV circle path test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/testing/netjail_start.sh</td><td width="40%" style="vertical-align: top;">Enhanced port forwarding configuration to restrict port forwarding to specific source IPs.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">contrib/netjail/topo.sh</td><td width="40%" style="vertical-align: top;">Make specific nodes configurable as source node for IP forwarding.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">src/testing/testing.c</td><td width="40%" style="vertical-align: top;">Helper methods to retrieve the number of additional connections globally and per peer, and which peer is allowed as source for IP forwarding.</td>
+                <tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile5.html.j2 b/template/l2o/mile5.html.j2
new file mode 100644
index 00000000..ddb8c9d7
--- /dev/null
+++ b/template/l2o/mile5.html.j2
@@ -0,0 +1,153 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 5</h2><br/>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Testing Framework") }}</h4><br/>
+        <p>
+          {% trans %}
+          <ul>
+                <li>Added so called barrier functionality, which is a set of commands to easy implement a barrier. A barrier is some point in time during execution of a test which if reached can trigger some action. For details have a look into commits <a href='https://git.gnunet.org/gnunet.git/commit/?id=34e1c58cb39a649c9a4c551681cedf19807b85f0'>34e1c58cb39a649c9a4c551681cedf19807b85f0</a>, <a href='https://git.gnunet.org/gnunet.git/commit/?id=ba4d141be09651b452270fc21f062d50bd3f738a'>ba4d141be09651b452270fc21f062d50bd3f738a</a> and <a href='https://git.gnunet.org/gnunet.git/commit/?id=2c2b2911e1585dc378dbb88d4dd6aaec37b00316'>2c2b2911e1585dc378dbb88d4dd6aaec37b00316</a>.</li>
+          </ul>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("TNG Service") }}</h4><br/>
+        <p>
+          {% trans %}
+          <ul>
+                <li>Added nat reversal code to tcp communicator. Prepared udp communicator.</li>
+                <li>Added tcp icmp nat hole punching test case script, and fixed bugs occuring during shutdown.</li>
+                <ul>
+                        <li>src/transport/test_transport_nat_icmp_tcp.sh</li>
+                </ul>
+                <li>Added performance test case.</li>
+                <ul>
+                        <li>src/transport/test_transport_plugin_cmd_simple_send_performance.c</li>
+                        <li>src/transport/test_transport_simple_send_performance.sh</li>
+                        <li>src/transport/test_transport_simple_send_performance_topo.conf</li>
+                        <li>src/transport/transport_api_cmd_send_simple_performance.c</li>
+                </ul>
+                <li>Fixed bug happening during check for pending validation requests after
+    nat reversal.</li>
+                <li>Fixed bug of QueueEntry deleted too early.</li>
+                <li>Fixed bug about missing synchronisation between client and service queue
+    in Transport Core API.</li>
+                <li>Fixed bug of not sending the changed window size, which takes into account the used and lost data.</li>
+          </ul>
+          {% endtrans %}
+        </p>
+        <p>
+        Even more details in commits fc99f54070e04c043c14f2244f85833ecf6b00c4, 95a1edacccd9b3bf769a144a12d41946d0ac25dc and 247230d737e3e4709392148bfabbde25871b6914
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <ul>
+                <li>Added configuration to be able to start executables on a router node</li>
+                <ul>
+                        <li>contrib/netjail/netjail_core.sh</li>
+                        <li>contrib/netjail/netjail_start.sh</li>
+                        <li>contrib/netjail/topo.sh</li>
+                </ul>
+          </ul></br>
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_nat_upnp_topo.conf</td><td width="40%" style="vertical-align: top;">Added topology file for nat upnp test case</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="60%" style="vertical-align: top;">contrib/netjail/netjail_start.sh</td><td width="40%" style="vertical-align: top;">Handing over the global number of the router node to the script running
+    on that node. (8e1bf27b11)</td>
+                <tr>
+          </table></br>
+          <ul>
+                <li>miniupnpd only works with public IP addresses. (c524f91a6)</li>
+                <ul>
+                        <li>contrib/netjail/netjail_start.sh</li>
+                        <li>src/testing/gnunet-cmds-helper.c</li>
+                        <li>src/testing/testing.c</li>
+                </ul>
+          </ul>
+          <ul>
+                <li>Changed the format of the interface names to make miniupnpd happy. (4aec035ea)</li>
+                <ul>
+                        <li>contrib/netjail/netjail_core.sh</li>
+                        <li>src/testing/testing_api_cmd_netjail_start_cmds_helper.c</li>
+                </ul>
+          </ul>
+          <ul>
+                <li>Cleanup after scripts which were running on netjail nodes. (9d6ace0b9)</li>
+                <ul>
+                        <li>contrib/netjail/netjail_stop.sh</li>
+                </ul>
+          </ul></br>
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_nat_icmp_tcp_topo.conf</td><td width="40%" style="vertical-align: top;">Added topology file for tcp icmp nat hole punching test case.</td>
+                <tr>
+          </table></br>
+          <ul>
+                <li>Added code to configure connection attempts to natted peers. (6de2cb8f7a)</li>
+                <ul>
+                        <li>src/testing/testing.c</li>
+                        <li>src/transport/transport_api_cmd_connecting_peers.c</li>
+                </ul>
+          </ul>
+          <ul>
+                <li>Added code in the netjail scripts to enable router nodes to forward icmp requests
+    and response. (a21cb1820)</li>
+                <ul>
+                        <li>contrib/netjail/netjail_core.sh</li>
+                        <li>contrib/netjail/netjail_start.sh</li>
+                </ul>
+          </ul>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Performance Measurement") }}</h4>
+        <p>
+          {% trans %}
+          The outcome of the performance measurement was ~24 MByte/s for packets with size of 65000 bytes. To follow up on this measurement one has to get the mean time the packets of 65000 bytes needed to reach another peer, to calculate the data rate, by doing<br/><br/>
+          <code>grep "mean time traveled" 1b8b9ebe2_test.out|tail -1</code><br/><br/>
+          on the log file <a href="/l2o/1b8b9ebe2_test.out">1b8b9ebe2_test.out</a> of the performance test case.
+          
+          For this measurement the TNG layer was using tcp only, because there was an unfixed bug, if running tcp and udp in parallel.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("API Documentation") }}</h4>
+        <p>
+          {% trans %}
+          Documentation of the new <a href='https://docs.gnunet.org/doxygen/d2/dc4/group__TNG.html'>TNG Api</a>.
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile6.html.j2 b/template/l2o/mile6.html.j2
new file mode 100644
index 00000000..ceb9ca4f
--- /dev/null
+++ b/template/l2o/mile6.html.j2
@@ -0,0 +1,83 @@
+ {% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 6</h2><br/>
+      <section>
+        <h4>{{ _("TNG Service") }}</h4><br/>
+        <p>
+          {% trans %}
+          <ul>
+                <li>Introduced frags_in_flight flag. With this flag we check if fragments of a PendingMessage are being send right now, to not resend single fragments, but the PendingMessage at once.</li>
+                <li>The time to wait for resending a PendingMessage - which was fragmented - is calculated, depending on the number of fragments present, and how much of the PendingMessage was already fragmented.</li>
+                <li>ValidationState now contains the addres prefix of the address being validated, because we have to check which communicator gave us the validation response.</li>
+                <li>Handling flow control takes used window size into account, together with data loss.</li>
+                <li>We do not update queue performance if PendingMessage was resend.</li>
+                <li>Changed test case to except 0.5% packet loss.</li>
+                <li>Removed misplaced sending of an acknowlegement in udp communicator.</li>
+                <li>GNUNET_SERVICE_client_continue was misplaced after receiving CORE Ack, blocking the service.</li>
+                <li>Fixed bug when checking, if fragment sub tree is done.</li>
+                <li>Fixed bug in calculation of delay for PendingAcknowledgement.</li>
+                <li>Fixed bug in calculation of subtree fragment message size.</li>
+                <li>Fixed bug that additional queues for the same communicator inherit the validity period.</li>
+                <li>Fixed logic bug when searching for QueueEntry matching acknowledgement.</li>
+                <li>Fixed misplaced increase of queue length.</li>
+          </ul>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Configuration") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                 <tr>
+                        <td width="60%" style="vertical-align: top;">src/transport/test_transport_simple_send_performance_topo.conf</td><td width="40%" style="vertical-align: top;">Changed configuration to use TCP and UDP together.</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Performance Measurement") }}</h4>
+        <p>
+          {% trans %}
+          The outcome of the performance measurement was ~66 MByte/s for packets with size of 65000 bytes. To follow up on this measurement one has to get the mean time the packets of 65000 bytes needed to reach another peer, to calculate the data rate, by doing<br/><br/>
+          <code>grep "mean time traveled" 811c040a2_test.out|tail -1</code><br/><br/>
+          on the log file <a href="/l2o/811c040a2_test.out">811c040a2_test.out</a> of the performance test case.
+          The performance increased from ~24 MByte/s measured with the code revision of milestone 5 by using TCP only to ~66 MByte/s measured with the code revision of milestone 6 for packet size of 65000 bytes using TCP and UDP together.
+          There are still possibilities to increase performance documented as TODOs in the source code.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Synergie with Interpeer Channeler project.") }}</h4>
+        <p>
+          {% trans %}
+          The Interpeer library Channeler and the L2O project have some goals in common. These include independence of the transmission protocol used, congestion control, reliability. Other goals of the Channeler project are not goals of the L2O project, but are already implemented or planned for other layers of GNUnet, such as multiplexing and ordered delivery of packages. There are also goals of the L2O project that are not goals of the Channeler project, such as metadata protection and identity assurance of communication partners. Due to these half overlapping half disjoint targets it is not reasonable that on project makes use of the other as a whole. However, parts of one project may well be applicable in the other. Since the Channeler project is not yet completed, it is not yet possible to identify the interesting parts beyond doubt. Interesting for the further development of L2O is the "Zero-Copy and Buffering" functionality of the Channeler project. This is also planned for future versions of L2O.
+          In conclusion, both projects can benefit from each other. At this point in time, it is still too early to tackle this concretely.
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile7.html.j2 b/template/l2o/mile7.html.j2
new file mode 100644
index 00000000..e75caf17
--- /dev/null
+++ b/template/l2o/mile7.html.j2
@@ -0,0 +1,62 @@
+ {% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 7</h2><br/>
+      <section>
+        <h4>{{ _("Marked old transport API as deprecated") }}</h4><br/>
+        <p>
+          {% trans %}
+          To make the search for the old API methods easier, those methods were marked as deprecated in their header files.</br></br>
+          
+          See branch l20integration revision 664286d.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Removed usage of old transport API methods") }}</h4><br/>
+        <p>
+          {% trans %}
+          Removed usage of old transport API methods and exchanged them with API methods of L2O or deleted without replacement, if there is no corresponding functionality in L2O.</br></br>
+          In the process, the subsystems cadet, core, dhtu, fs and topology were touched.</br></br>
+          The blacklist and friend functionality in subsystem topology was deleted without replacement, as well as the bandwith allocation in the fs (file sharing) subsystem.</br></br>
+          In the transport subsystem itself, old API methods are still used until the code is finally removed in Milestone 9. There is a cli tool gnunet-transport in the transport subsystem which needs be rewritten partially to get infromation from L2O which can not retrieved via the old API anymore.</br></br>
+          Additionally there is a peerinfo cli tool gnunet-peerinfo, which needs to be rewritten partially too.</br></br>
+          
+          See branch l20integration revision b78f993.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Deactivated tests which rely on old transport API methods") }}</h4><br/>
+        <p>
+          {% trans %}
+          All test which rely on the old transport API methods were deactivated. They are still in the code base, but they just wouldn't work.</br></br> 
+          
+          See branch l20integration revision 72b4f42.
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile8.html.j2 b/template/l2o/mile8.html.j2
new file mode 100644
index 00000000..8af78816
--- /dev/null
+++ b/template/l2o/mile8.html.j2
@@ -0,0 +1,86 @@
+ {% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 8</h2><br/>
+      <section>
+        <h4>{{ _("Added command to execute a script") }}</h4><br/>
+        <p>
+          {% trans %}
+          A command to start any kind of script was added. As of now this command blocks until the script finished. In the context of this milestone this command is later used to execute a script which blocks until it finds a specific file.</br></br>
+          
+          See branch l20integration revision 40a5a65.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Added generic start script for test cases") }}</h4><br/>
+        <p>
+          {% trans %}
+          We do not want to have a specific start script for every test case. This start script asks for a test case configuration to use.</br></br>
+          
+          See branch l20integration revision 80971b6.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Moved start peer command to testing subsystem") }}</h4><br/>
+        <p>
+          {% trans %}
+          A start script was added, that can be used by test cases in all subsystems, and which starts the new transport subsystem.</br></br> 
+          
+          See branch l20integration revision 03a5d17.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Added Testcase that just runs two peers, and blocks") }}</h4><br/>
+        <p>
+          {% trans %}
+          This testcase just runs to peers with the new transport subsystem and runs the command that executes a script that blocks until </br></br> 
+          
+          See branch l20integration revision 4ba7b5f.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Manually testing") }}</h4><br/>
+        <p>
+          {% trans %}
+          With the above mentioned test case, it was possible to get GNUnet running with the new transport (L2O) subsystem, do manually testing. Some bugs were already fixed:</br></br> 
+          <ul>
+                <li>Fixed bug that core subsystem is not calling GNUNET_TRANSPORT_core_receive_continue. See branch l20integration revision 61bbc04.</li>
+                <li>Fixed bug that QueueEntry of another queue still holds reference to PendingMessage. See branch l20integration revision aec63bf.</li>
+          </ul>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Status") }}</h4><br/>
+        <p>
+          {% trans %}
+          The core and cadet subsystems were manually tested regarding integration with transport. They are boh working.
+          Next subsystems to test: dhtu, fs and topology.
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/mile9.html.j2 b/template/l2o/mile9.html.j2
new file mode 100644
index 00000000..1e5c9220
--- /dev/null
+++ b/template/l2o/mile9.html.j2
@@ -0,0 +1,338 @@
+ {% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 9</h2><br/>
+      
+      <section>
+        <h4>{{ _("Added api to store hellos with peerstore service") }}</h4><br/>
+        <p>
+          {% trans %}
+          This functionality was formerly implemented in the peerinfo service.</br></br> 
+          
+          See revision 0f8b712.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Added api to get notified when hellos are stored with peerstore service") }}</h4><br/>
+        <p>
+          {% trans %}
+          This functionality was formerly implemented in the peerinfo service. After storing hellos with the peerstore service this was needed there.</br></br>
+          
+          See revision 55a25ef.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Changed new hello uri api to allow to change the expiration time") }}</h4><br/>
+        <p>
+          {% trans %}
+          This change was necessary to create the bootstrap hello which must be valid indefinitely.</br></br>
+          
+          See revision 39bcd0f.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Exchanged peerinfo api to store hellos with new peerstore api") }}</h4><br/>
+        <p>
+          {% trans %}
+          The new api needed to be exchange in all GNUnet packages.</br></br> 
+          
+          See revision 23a2640.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Change watch to return actual values, before watching.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The watch api of the peerstore service was changed to return all values for a given key, before notifying the caller about ne values being stored.</br></br> 
+          
+          See revision 86ae84f.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("The old hello design replaced by the new  hello design.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The new hello design was exchanged in all GNUnet packages.</br></br> 
+          
+          See revision a362cd5.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Cli tool for changing hello files in contrib can change file from old to new hello design.") }}</h4><br/>
+        <p>
+          {% trans %}
+          A cli tool for changing the bootstrap hello file in the contrib/hello directory was changed to rewritethe hello bootstrap file from old to new format. </br></br> 
+          
+          See revision 8ea9223.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Moved code to scan and import hello file into peerstore from peerinfo.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The peerinfo service service was scanning a hostlist file and the data was used by the hostlist server. This code was moved to the peerstore service.</br></br> 
+          
+          See revision 20d6f3.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Moved code to testing to have more generic test setup, which can be used not only from within transport.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The new testing framework was transport specific Now it can be used in other packages too.</br></br> 
+          
+          See revision 02a1fda.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Code moved to the core package to get rid of circular dependencies.") }}</h4><br/>
+        <p>
+          {% trans %}
+          After changes to be able to use the testing framework more generic the dependencies needed to be fixed..</br></br> 
+          
+          See revision 1016d6d.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Changed method GNUNET_HELLO_builder_get_expiration_time to not need parameter GNUNET_HELLO_Builder.") }}</h4><br/>
+        <p>
+          {% trans %}
+          A small function syntax fix.</br></br> 
+          
+          See revision 84913b.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Changed the behavior of GNUNET_PEERSTORE_watch to also return the values allready stored for the key.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The watch functionality first returns all values for a given key, before notifying the caller about new values for that key.</br></br> 
+          
+          See revision e1341d1.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Changed address and hello format to new TNG format.") }}</h4><br/>
+        <p>
+          {% trans %}
+          All occurencies in GNUnet packages were changed from old to new hello format.</br></br> 
+          
+          See revision 66ecfe2.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Fixed bug in bootstrap code.") }}</h4><br/>
+        <p>
+          {% trans %}
+          Unnecessary check removed. Fixed small coding error.</br></br> 
+          
+          See revision 3bd35e8.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Fixed validation bug.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The validation of other peers in the transport package was not working in some cases, because validation did not use monotonic time, and first_challenge_use wasn't reset.</br></br> 
+          
+          See revision 88cb4be.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Fixed wrong group name.") }}</h4><br/>
+        <p>
+          {% trans %}
+          A wrong group name was used for a DHT block entry.</br></br> 
+          
+          See revision 8127d51.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Task added to start reading the hostlist entries only after a certain period of time has elapsed.") }}</h4><br/>
+        <p>
+          {% trans %}
+          Reading hostlist entries and compiling the hostlist response to a hostlist request was started too early, even though the peer did not created its own hello.</br></br> 
+          
+          See revision 7761b42.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Added test config to have a peer running the hostlist server.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The configuration of the test case had to be changed to let one peer run a hostlist server.</br></br> 
+          
+          See revision 3c761cd.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Changed hostlist server to use a hello cache.") }}</h4><br/>
+        <p>
+          {% trans %}
+          The host list server needed a cache for the entries, because with storing entries in the peerstore, only the new hellos were notified to the hostlist server.</br></br> 
+          
+          See revision e4b146e.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Bootstrap: Fixed bug to not replace hellos for a peer.") }}</h4><br/>
+        <p>
+          {% trans %}
+          Hellos are store with a specific key GNUNET_PEERSTORE_HELLO_KEY and option GNUNET_PEERSTORE_STOREOPTION_MULTIPLE instead of GNUNET_PEERSTORE_STOREOPTION_REPLACE.</br></br> 
+          
+          See revision 0516538.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Hello: Fix another bug in cli tool to generate contrib hello file.") }}</h4><br/>
+        <p>
+          {% trans %}
+          Use the actuall private key of the installed peer, not the peer id from file.</br></br> 
+          
+          See revision e0d28ef.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Cadet: Fixed issue #7542") }}</h4><br/>
+        <p>
+          {% trans %}
+          Cadet still used the legacy DHT hello block format, changed to the new URL-based block format.</br></br> 
+          
+          See revision 9376034.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Added DDLs for handling GNUNET_PEERSTORE_StoreHelloContext.") }}</h4><br/>
+        <p>
+          {% trans %}
+          Changed code to store hellos in new format in peerstore in transport and topology subsystem.</br></br> 
+          
+          See revision 233a6be.
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("A long list of Bugs which where fixed.") }}</h4><br/>
+        <p>
+          {% trans %}
+          <ul>
+                <li>c1783c1: TNG: Adding missing manual test case topology file.</li>
+                <li>8093c8e: Changed relative path to no force test config</li>
+                <li>aa9bebd: TNG: Fixed bug in handling hello to start validation.</li>
+                <li>21be887: Introduced closure to hold store context when caling function to add hello in peerstore.</li>
+                <li>0ecf00f: Hello: Fixed usage of GNUNET_HELLO_builder_iterate.</li>
+                <li>8ebef9f: Cadet: Changes to use DhtHelloMessage instead of HelloUriMessage, and to hand over not a HelloMessage, but a block to the dht.</li>
+                <li>2b87bab: Peerstore: Fixed memory related bugs.</li>
+                <li>a71b245: Testing: Exchange binary name for transport in test case configuration.</li>
+                <li>7da7937: Transport: Fixed null pointer in address iteration code to start validation.</li>
+                <li>060b681: Transport: Fixed bug while setting up key material for backchannel.</li>
+                <li>53ad5e4: Transport: Fixed bug while setting up key material for backchannel.</li>
+                <li>57d31ec: Transport: Fixed bug in free pending messages and queue entries.</li>
+                <li>20f5e2a: Transport: Fixed bug in ring buffer for core messages.</li>
+                <li>2c71a76: Topology: Fixed small bug.</li>
+                <li>d46e0b7: Hello: Changed bootstrap peer hello file to new bootstrap peer.</li>
+                <li>29e2e51: Peerstore: Make peerstore start immediately. Added option to use included hello.</li>
+                <li>1848ece: Hello: Change error handling of GNUNET_HELLO_builder_add_address usage.</li>
+                <li>4e77b10: Peerstore: We replace existing hellos. Only the origin peer merges hellos.</li>
+                <li>8e8c3f1: Transport: Added missing dekrement when removing QueueEntry from DLL.</li>
+                <li>a919091: Transport: Added missing dekrement of global communicator queue counter.</li>
+                <li>1513057: Transport: Using the correct TransportClient for dekrementing the global communicator queue counter.</li>
+                <li>23246e1: Transport: Fixed check when to stop FC retransmission.</li>
+                <li>015cef0: Transport: Removed logging that lead to an assertion.</li>
+                <li>ea2420b: Transport: Fixed check of value gotten from peerstore.</li>
+                <li>5934318: Transport: Destroy closed ProtoQueue.</li>
+                <li>f5fa8ef: Transport: Added logging in case of UDP errors, and destroy queue in case of errors.</li>
+                <li>e2a4d6c: Transport: Fixed bug in handling of AckPending.</li>
+                <li>c9b0b25: Transport: Removed misplaced removal of QueueEntry.</li>
+                <li>7f7571b: Transport: Fixed bugs in core message cache.</li>
+                <li>bc81b0a: Transport: We need to check if a message was cached when resuming communicators.</li>
+                <li>433c13c: Transport: Fixed bug handling queue length and QueueEntry when queue has no capacity.</li>
+                <li>3becc2d: Transport: Fixed bug to check each queue for validity separately.</li>
+                <li>2d955b1: Transport: More useful debug logging für service.</li>
+                <li>f1510f7: Transport: Fixed using wrong function to calculate mean time when to send next fragment.</li>
+                <li>ec57587: Peerstore: Fixed wrong assert when checking DLL with watches.</li>
+                <li>4274265: Transport: Added logging in case of UDP errors, and destroy queue in case of errors.</li>
+                <li>8d3c8c3: Transport: Fixed bug in handling of AckPending.</li>
+                <li>edd8e08: Transport: Removed misplaced removal of QueueEntry.</li>
+                <li>3b906ef: Transport: Fixed bugs in core message cache.</li>
+                <li>ca73eed: Transport: We need to check if a message was cached when resuming communicators.</li>
+                <li>e39ed50: Transport: Fixed bug handling queue length and QueueEntry when queue has no capacity.</li>
+                <li>f08eae1: Transport: Fixed bug to check each queue for validity separately.</li>
+                <li>6a27b67: Transport: Fixed using wrong function to calculate mean time when to send next fragment.</li>
+                <li>da2f9f7: Peerstore: Fixed wrong assert when checking DLL with watches.</li>
+                <li>6565677: Transport: Fixed counting of fragments of a message</li>
+                <li>26b05be: Transport: Introduced variable to count the round of fragments of a message being (re)send.</li>
+                <li>e22e637: Transport: Fixed ring buffer.</li>
+                <li>f387a7b: Util: Introduced GNUNET_TIME_relative_multiply_double.</li>
+                <li>36a9952: Transport: Added cleanup task to remove QueueEntry we got no ACK for.</li>
+                <li>164badb: Transport: Changed logic to first create a queue before starting validation.</li>
+                <li>894754f: Core: Added missing GNUNET_TRANSPORT_core_receive_continue.</li>
+                <li>b9cd040: Transport: Fixed bug in logic getting root parent of fragment which is a DV box.</li>
+                <li>84b76e3: Transport: Resuming communicators in case of core restarting.</li>
+                <li>78b0a9a: Transport. Fixed bug in logic freeing timedout QueueEntry.</li>
+                <li>0d9df1c: Fixed bug calculating next resend of fragments.</li>
+                <li>c69a0e9: Transport: first_challenge_use has to be reset in case of revalidation.</li>
+                <li>01b7a5d: Transport: When to resend a validation challenge and when to start revalidation needs to be seperate logic.</li>
+                <li>5f56628: Transport: Fixed bug in logic releasing resources and notifying communicators after caching messages to core.</li>
+                <li>94caa7d: Transport: Fixed bug in resend logic for fragments, especially for DV boxes.</li>
+                <li>67c90f8: Core: Fixed bug to stop keepalive after handling ping.</li>
+                <li>a3b9d98: Transport: Fixed fragmentation logic.</li>
+                <li>4254ee1: Core: Removed unnecessary client continue.</li>
+                <li>1d88d65: Transport: Added check for DV box, when checking for last applicable fragment during freeing some fragment.</li>
+                <li>4402b56: Transport: Added logging to debug freeing of fragments.</li>
+                <li>25ffc82: Transport: Inform Core about all VirtualLinks not only neighbours.</li>
+                <li>aaf07c7: Core: Added logic to decrease restart delay of connection to Transport depending on how long the connection to Transport lasted.</li>
+          </ul></br></br>
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>{{ _("Status") }}</h4><br/>
+        <p>
+          {% trans %}
+          The hostlist, and topology subsystems  and the bootstrap functionality were manually tested. Everything was working without errors. No known errors in other subsystems. Branch merged into master. New Transport and Hello released with version 0.21.
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/l2o/testng.html.j2 b/template/l2o/testng.html.j2
new file mode 100644
index 00000000..69905711
--- /dev/null
+++ b/template/l2o/testng.html.j2
@@ -0,0 +1,119 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Layer-2-Overlay") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>The next generation testing framework</h2><br/>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("Netjail setup and execution") }}</h4><br/>
+        <p>
+          {% trans %}
+          Netjail is the GNUnet naming for having several <a href="https://www.man7.org/linux/man-pages/man8/ip-netns.8.html">network namespaces</a>, being isolated from each other to test how GNUnet nodes with limited connectivity behave, and how the new transport next generation implementation can help to circumvent the connectivity obstacles. The network namespaces are span a network with globally known nodes and several subnets separated from each other via a single router.
+          We have three scripts for the test setup:
+          
+          <ul>
+            <li>netjail_start.sh: A script to setup the network namespaces. This script takes three arguments. The first is either the name of a configuration for the test setup topology or a string containing the topology information. The second is the process id of the test. The third is a flag if the first parameter contains the name of the configuration file or the topology string.</li>
+            <li>netjail_exec.sh: A script to run some command in a specific namespace. This script takes eight arguments. The first is the index of a node in a namespace for which we like to execute a command. The second is the index of the namespace of the node. The third is the command to execute, the fourth is the number of subnets, the fifth the number of nodes in each subnet, the sixth is the identifier used by the <a href="https://www.man7.org/linux/man-pages/man8/ip-netns.8.html">ip-netns</a> command, the sixth is a flag is the topology information is given via a topology file of a string containing the topology information..</li>
+            <li>netjail_stop.sh: A script which remove all the network namespace setup by netjail_start.sh. The arguments are the same as those for netjail_start.sh.</li>
+            </ul>
+            The is a generic test binary (test_transport_start_with_config) which will start the above mentioned scripts. Because creating network namespaces is only permitted for privileged users the generic test binary is not start directly, but via scripts. This script starts the generic binary using the command unshare. Using unshare one can create a namespace with its own user namespace, where creating network namespaces is allowed. Precondition to do this with unshare, is to set the kernel.unprivileged_userns_clone kernel parameter.  
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h4><a name="cmdhelper" class="subnav-anchor"></a>{{ _("CMD helper and testcase plugins") }}</h4><br/>
+      
+      <section>
+        <p>
+          {% trans %}
+          Although netjail_exec.sh can execute an arbitrary command in the ng testing framework a special command is used: gnunet-cmds-helper
+          This commands itself is of a special kind named helper processes which communicates via GNUNET_MessageHeaders on stdin/stdout with the process that started the helper. The gnunet-cmds-helper is used to load testcase plugins. Those plugins are implementations of an api which is used to start different test cases. Those plugins are dynamically loaded by gnunet-cmds-helper. Each plugin defines the commands which are running in a local interpreter loop started by the helper on that specific network namespace node. The plugins are also responsible for the communication via the helper with the master interpreter loop.
+            {% endtrans %}
+        </p><br/>
+      </section>
+      <h4><a name="cmdpattern" class="subnav-anchor"></a>{{ _("Command Pattern") }}</h4><br/>
+      
+      <section>
+        <p>
+          {% trans %}
+          The testing framework borrowed from the <a href="https://docs.taler.net/developers-manual.html#testing-library">GNU Taler testing library</a> was extended to handle asychronous commands. Therefore a struct GNUNET_TESTING_AsyncContext was added to struct GNUNET_TESTING_Command. By default the continuation function of GNUNET_TESTING_AsyncContext is the interpreter_next function of the interpreter loop (blocking asynchronous command) which will be executed calling GNUNET_TESTING_async_finish, when the asynchronous task finished, but also can be any other function to be executed when the asynchronous task is non blocking.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h4><a name="cmdpattern" class="subnav-anchor"></a>{{ _("Topology Configuration") }}</h4><br/>
+      
+      <section>
+        <p>
+          {% trans %}
+          The topology of the netjail setup can be configured via a configuration file, or with a configuration string handed over to the generic binary for starting netjail based tests.</br></br>
+Both method can be examined in two example test scripts</br></br>
+test_transport_send_simple.sh</br></br>
+and</br></br>
+test_transport_send_simple_string.sh</br></br>
+The Syntax of the configuration is as follows.</br></br> 
+The configuration string is structured by lines and the delimiter ':' used for seperating key/value(s) pairs and the chars '{' and '}' for grouping several key/value pairs as value and '|' to separate a group of values from the key/value(s) pair identifying a line. Below you find the EBNF of the configuration syntax.</br></br>
+config = line, {line} ;<br/><br/>
+line = ( "M:", NumberOfNodesPerSubnet ) | ( "N:", NumberOfSubnets ) | ( "X:", NumberOfGlobalNodes ) | NumberOfAdditionalConnections | ( "T:", GlobalPluginName ) | ( GlobalPeer, "|", KValue ) | ( "R:", IndexOfSubnetRouter, "|", RValue ) | ( SubnetPeer, "|", PValue ) ;<br/><br/>
+NumberOfNodesPerSubnet = Zero | NaturalNumber ;<br/><br/>
+NumberOfSubnets = NaturalNumber ;<br/><br/>
+NumberOfGlobalNodes = NaturalNumber ;<br/><br/>
+NumberOfAdditionalConnections = "AC:", NaturalNumber 
+GlobalPluginName = "libgnunet_test_transport_plugin_cmd_", PluginName ;<br/><br/>
+GlobalPeer = "K", ":", IndexOfGlobalNode ;<br/><br/>
+KValue = EstablishConnectionToPeerViaProtocol ;<br/><br/>
+IndexOfSubnetRouter = Zero | NaturalNumber ;<br/><br/>
+RValue = OpenTCP, "|", OpenUDP ;<br/><br/>
+SubnetPeer = "P:", SubnetIndex, ":", NodeIndexInSubnet ;<br/><br/>
+PValue = EstablishConnectionToPeerViaProtocol, { "|", "{", NumberOfAdditionalConnections, "}" } ;<br/><br/>
+Zero = "0" ;<br/><br/>
+NaturalNumber = NumeralWithoutZero, { Numeral } ;<br/><br/>
+PluginName = Letter , { ( Letter | "_" ) } ;<br/><br/>
+IndexOfGlobalNode = Zero | NaturalNumber ;<br/><br/>
+EstablishConnectionToPeerViaProtocol = "{" "connect", ":" EstablishConnectionToPeerViaProtocolValues "}" ;<br/><br/>
+OpenTCP = OpenTCPNoSource | OpenTCPWithSource ;<br/><br/>
+OpenUDP = OpenUDPNoSource | OpenUDPWithSource ;<br/><br/>
+SubnetIndex = NaturalNumber ;<br/><br/>
+NodeIndexInSubnet = NaturalNumber ;<br/><br/>
+NumeralWithoutZero = "0" | Numeral ;<br/><br/>
+Numeral = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;<br/><br/>
+Letter = "A" | "B" | ... | "Z" | "a" | ... | "z";<br/><br/>
+EstablishConnectionToPeerViaProtocolValues = EstablishConnectionToPeerViaProtocolValue { "|", EstablishConnectionToPeerViaProtocolValue }
+OpenTCPNoSource = "{tcp_port:", switch, "}" ;<br/><br/>
+OpenUDPNoSource = "{udp_port:", switch, "}" ;<br/><br/>
+OpenTCPWithSource = "{tcp_port:", SubnetPeer, { "tcp_port", SubnetPeer } ;<br/><br/>
+OpenTUDWithSource = "{udp_port:", SubnetPeer, { "udp_port", SubnetPeer } ;<br/><br/>
+EstablishConnectionToPeerViaProtocolValue = "{", ( GlobalPeer | SubnetPeer ), ":", Protocol, "}" ;<br/><br/>
+switch = On | Off ;<br/><br/>
+Protocol = "tcp" | "udp" ;<br/><br/>
+On = 1 ;<br/><br/>
+Off = 0 ;<br/><br/>
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/livingstandards.html.j2 b/template/livingstandards.html.j2
index f8d1d580..c8372ccc 100644
--- a/template/livingstandards.html.j2
+++ b/template/livingstandards.html.j2
@@ -1,11 +1,12 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
  <div class="container-fluid">
    <div class="container">
      <article>
        <div class="row">
          <div class="container text-center">
-            <h1>{{ _("Living Standards") }}</h1>
+            <h1>Living Standards</h1>
            <section>
              <p>
                {% trans %}
@@ -16,11 +17,21 @@
          </div>
        </div>
        <ul>
-          <li><b>LSD0000</b>: The Distributed Hash Table</li>
+          <li><b>LSD0000</b>: Reserved</li>
          <li><b>LSD0001</b>: <a href="https://lsd.gnunet.org/lsd0001">The GNU Name System</a></li>
-          <li><b>LSD0002</b>: <a href="https://lsd.gnunet.org/lsd0002">re:claimID</a></li>
+          <li><b>LSD0002</b>: <a href="https://lsd.gnunet.org/lsd0002">re:claimID (work-in-progress)</a></li>
-          <li><b>LSD0003</b>: <a href="https://lsd.gnunet.org/lsd0003">Byzantine Fault Tolerant Set Reconciliation</a></li>
+          <li><b>LSD0003</b>: <a href="https://lsd.gnunet.org/lsd0003">Byzantine Fault Tolerant Set Reconciliation (work-in-progress)</a></li>
+          <li><b>LSD0004</b>: <a href="https://lsd.gnunet.org/lsd0004">The R5N Distributed Hash Table (work-in-progress)</a></li>
        </ul>
+        Unspecified components and subsystems:
+        <ul>
+          <li>CADET: Secure node-to-node communication.</li>
+          <li>CONVERSATION: Voice communication.</li>
+          <li>FILE-SHARING</li>
+          <li>CORE: Secure peer-to-peer neighbour communication.</li>
+          <li>TRANSPORT: Connectivity.</li>
+        </ul>
      </article>
    </div>
  </div>
diff --git a/template/news/2011-11-24-archived-vfork.html.j2 b/template/news/2011-11-24-archived-vfork.html.j2
new file mode 100644
index 00000000..61249c38
--- /dev/null
+++ b/template/news/2011-11-24-archived-vfork.html.j2
@@ -0,0 +1,62 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>vfork and the signal race</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+Many articles uniformly claim that using vfork should be
+<a href="https://web.archive.org/web/20150924082249/http://tldp.org/HOWTO/Secure-Programs-HOWTO/avoid-vfork.html">avoided</a>
+and that the only difference between vfork and fork is (or used-to-be)
+<a href="https://web.archive.org/web/20150924082249/http://www.unixguide.net/unix/programming/1.1.2.shtml">performance</a>
+and that thus vfork is
+<a href="https://web.archive.org/web/20150924082249/http://stackoverflow.com/questions/4856255/the-difference-between-fork-vfork-exec-and-clone">obsolete</a>.
+Here, I wanted to document a technical case where vfork is actually required and where using fork instead of vfork (or operating system implementors implementing vfork as an alias for fork) causes a hard-to-find data race.
+</p>
+<p>
+GNUnet uses a hypervisor process (gnunet-service-arm) to control the peer's service processes. Services are started (vfork+exec) on-demand. The hypervisor is also responsible for stopping the services and sends a SIGTERM signal to the services to stop them. SIGTERM must be used to allow the services to shutdown gracefully. Naturally, after shutting down a service with a signal, the hypervisor waits for SIGCHILD and then cleans up with waitpid. Once all services processes have completed, the hypervisor can exit as well. It should also be noted that the hypervisor handles SIGTERM (by shutting down all services), so a signal handler is installed for that signal.
+</p>
+<p>
+The reason why we must use vfork is the following. After the hypervisor has started the service, it might be asked to stop the service at any time. We've actually managed (by scripting it) to reliably trigger a case where the hypervisor would start a service (fork) and then receive a request to terminate the service and issues the SIGTERM signal to the child before the child process had a chance to call exec. As a result, the SIGTERM would go to the (existing) handler of the hypervisor's code, then the child process would be exec'ed and essentially the signal was thereby lost in the race between kill and exec:
+</p>
+<p>
+If exec wins, the signal either kills the process hard during the service startup phase, which is fine, or the service process might handle it normally and terminate --- also fine).
+</p>
+<p>
+If kill wins the race, the signal would be lost and the hypervisor would wait 'forever' for the child to terminate.
+</p>
+<p>
+The solution with vfork is elegant and simple: by blocking the parent, vexec guarantees that the parent's signal handler is no longer active (and replaced by default handlers or the child's custom handlers) by the time the parent is able to issue a 'kill'.
+</p>
+<p>
+In conclusion, with parents that issue 'kill' on child processes, the use of vfork can make an important semantic difference and not only (possibly) offer performance advantages. The situation above cannot be easily fixed by other means and thus vfork is an important POSIX call that should be supported properly by all quality implementations. A possible hack to work around a lack of vfork would be to create a pipe in the parent, set it to close-on-exec, fork the child, close the write end and then do a blocking read from the read end. Once you get a read error, the child has exec'ed. Rather ugly in my opinion.
+</p>
+<p>
+Currently, gnunet-service-arm can hang indefinitely on systems that do not provide a correct implementation of vfork (however, in practice normal users should never encounter this).
+</p>
+<p>
+<b>better suggestion from Thomas Bushnell</b>
+<br>
+I just got an alternative suggestion to using either a pipe and vfork from Thomas Bushnell, which I like and will use:
+"The hypervisor at start creates a global variable hypervisor_pid, initialized from getpid().
+The signal handler in the hypervisor then does this:
+<br>
+<code class="block">
+if getpid() == hypervisor_pid<br>
+  kill_all_children_and_exit();<br>
+else<br>
+  exit();<br>
+</code>
+In this way, if the child is between fork and exec when the parent gets its kill, and then it tries to kill the child, and the kill happens before the child execs (the problematic case you describe), then the child simply enters the hypervisor's signal handler, notices that it's not the hypervisor, and exits.
+<br>
+Thomas"
+<br>
+Thanks for the suggestion!
+</p>
+<p>
+Thomas's suggestion is all fine and well, except that it doesn't work on OS X. As the attached simple program "killing-child-kills-parent.c" demonstrates, OS X manages to sometimes either deliver the signal to the wrong process (?) or not update getpid() between fork+exec or is otherwise generally broken. The program simply installs a signal handler in the parent with the guard suggested by Thomas, then forks + exec's "sleep" and then immediately kills the child. So we expect the signal to either reach our signal handler (child between fork+exec), causing the child to 'exit', or to reach 'sleep' which should also die. Somehow instead the "Should NEVER get this signal!" message is printed. Well, OS X is known to be a pile of crap, so no surprise. Using 'vfork' instead of fork gets us the desired behavor -- howver, this is clearly just a hack. So vfork is back (on OS X) as of SVN 25495.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2013-11-15-special-use-gns.html.j2 b/template/news/2013-11-15-special-use-gns.html.j2
new file mode 100644
index 00000000..329e74d3
--- /dev/null
+++ b/template/news/2013-11-15-special-use-gns.html.j2
@@ -0,0 +1,14 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Special-Use Domain Names of Peer-to-Peer Name Systems</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+We just submitted our draft for
+<a href="https://web.archive.org/web/20140901155643/https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/">Special-Use Domain Names of Peer-to-Peer Name Systems</a> to IETF.
+The intention is to reserve the TLDs ".exit", ".i2p", ".gnu",
+".onion" and ".zkey" for use by the GNUnet, I2P and Tor peer-to-peer overlay
+networks.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2013-12-28-archived-typos-pkeys.html.j2 b/template/news/2013-12-28-archived-typos-pkeys.html.j2
new file mode 100644
index 00000000..a541ef94
--- /dev/null
+++ b/template/news/2013-12-28-archived-typos-pkeys.html.j2
@@ -0,0 +1,16 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Typo-Protected Public Keys</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+When users type in public keys (such as the 53-characters of a GNS zone), they might make typos. The usual way to fix typos is to add a checksum, further increasing the length of the sequence that has to be typed in.
+<br>
+We can fix this by including the checksum of the public key in the public key itself, simply by trying new private keys until the corresponding public key happens to have a checksum (over the other bits) in the bits designated for the checksum. If a checksum is 16 bits, we would only need to try 216 keys. The basic idea of brute-forcing keys to match a particular pattern <a href="https://web.archive.org/web/20141008173738/https://bitcointalk.org/index.php?topic=84569.0">was proposed before</a> for creating "vanity" public keys, but this might be another practical variant.
+</p>
+<p>
+<b>Acknowledgements</b><br/>
+The idea popped up in a discussion on the need for short public keys for GNS with Dan Bernstein and Tanja Lange at 30c3.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2018-06.html.j2 b/template/news/2018-06.html.j2
new file mode 100644
index 00000000..08428466
--- /dev/null
+++ b/template/news/2018-06.html.j2
@@ -0,0 +1,108 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.0pre66</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.0pre66.<br>
+  This is a pre-release to assist developers and downstream packagers to test the package before the final release after four years of development.
+</p>
+<p>
+  In terms of usability, users should be aware that there are still a very large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (~200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.0 release and especially this pre-release are only suitable for early adopters with some reasonable pain tolerance. 
+</p>
+<h4 class="western">License change</h4>
+<p>
+  GNUnet 0.11.0pre66 is the first release that will be made under the GNU Affero General Public License v3+. After a significant amount of internal discussion lead constructively by lynX (thanks!), the conclusion has been that the IPC and REST APIs should be extended with support for an GNUNET_MESSAGE_TYPE_AGPL or /agpl request that enables users of these client/service-style APIs to download the source code.
+</p>
+<p>
+  Naturally, the discussion on licensing may not necessarily end here, but at this point we are not aware of any dissent in the community and this release seems to be the right time to make such a change. While the final decision was not subjected to a broad feedback round, this was done simply on the grounds that this placement of the AGPL API seems to addresses all concerns that were raised. Finally, thanks to the copyright assignment all developers are participating in, the community will be able to revise this decision later if necessary.
+</p>
+<p>
+  It should also be noted that this change does not impose additional restrictions on the licensing models of GNU Taler or pEp: both projects have agreements with GNUnet e.V. that ensure that they can make decisions that fit these applications (not to mention significant parts of GNU Taler are already AGPLv3+ already).
+</p>
+<h4 class="western">About GNUnet</h4>
+<p>
+  GNUnet is a framework for secure peer-to-peer networking. GNUnet&#39;s primary design goals are to protect the privacy of its users and to guard itself against attacks or abuse. At this point, GNUnet offers four primary applications on top of the framework:
+</p>
+<p>
+  The file-sharing service allows anonymous censorship-resistant file-sharing. Files, searches and search results are encrypted to make it hard to control, track or censor users. GNUnet&#39;s anonymity protocol (gap) is designed to make it difficult to link users to their file-sharing activities. Users can also individually trade-off between performance and anonymity. Despite providing anonymity, GNUnet&#39;s excess-based economy rewards contributing users with better performance.
+</p>
+<p>
+  The VPN service allows offering of services within GNUnet (using the .gnu TLD) and can be used to tunnel IPv4 and IPv6 traffic over the P2P network. The VPN can also be used for IP protocol translation (6-to-4, 4-to-6) and it is possible to tunnel IP traffic over GNUnet (6-over-4, 4-over-6). Note that at this stage, it is possible for peers to determine the IP address at which services are hosted, so the VPN does not offer anonymity.
+</p>
+<p>
+  The GNU Name System (GNS) provides a fully-decentralized and censorship resistant replacement for DNS. GNS can be used alongside DNS and can be integrated with legacy applications (such as traditional browsers) with moderate effort. GNS provides censorship-resistance, memorable names and cryptographic integrity protection for the records. Note that at this stage, it is possible for a strong adversary to determine which peer is responsible for a particular zone, GNS does not offer strong anonymity. However, GNS offers query privacy, that is other participants can typically not decrypt queries or replies.
+</p>
+<p>
+  Conversation allows voice calls to be made over GNUnet. Users are identified using GNS and voice data is encrypted. However, Conversation does not provide anonymity at this stage --- other peers may observe a connection between the two endpoints and it is possible to determine the IP address associated with a phone.
+</p>
+<p>
+  Other applications, including in particular the SecuShare social networking application, are still strictly experimental.
+</p>
+<p>
+  For developers, GNUnet offers:
+</p>
+<ul>
+  <li>Access to all subsystems via clean C APIs</li>
+  <li>Mostly written in C, but extensions possible in other languages</li>
+  <li>Multi-process architecture for fault-isolation between components</li>
+  <li>Use of event loop and processes instead of threads for ease of development</li>
+  <li>Extensive logging and statistics facilities</li>
+  <li>Integrated testing library for automatic deployment of large-scale experiments with tens of thousands of peers</li>
+</ul>
+<h4 class="western">Noteworthy improvements in 0.11.0pre66</h4>
+<ul>
+  <li>Improved documentation, converting Drupal handbook to Texinfo (thanks ng0!)</li>
+  <li>GNU Name System now can take over arbitrary TLDs, and support for conversion from DNS zones to GNS exists</li>
+  <li>Critical bugfixes in CORE, DHT and CADET subsystems</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists over 350 individual issues that were resolved (see <a href="https://gnunet.org/bugs/changelog_page.php">Changelog</a>)
+</p>
+<h4 class="western">Known Issues</h4>
+<p>
+  We have a few issues that are most likely not resolved in the final release. Users should be aware of these issues, which we hope to address shortly.
+</p>
+<ul>
+  <li>There are known major design issues in TRANSPORT, ATS and CORE which will need to be addressed for usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The Web site and manuals still need significant rework.</li>
+  <li>Subsystems related to SecuShare and RPS remain experimental.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at https://gnunet.org/bugs/ which lists about 200 more specific issues.
+</p>
+<h4>Availability</h4>
+<p>
+  The GNUnet 0.11.0pre66 source code is available from all GNU FTP mirrors. The GTK frontends (which includes the gnunet-setup tool) are a separate download. Please note that some mirrors might still be synchronizing.
+</p>
+<ul>
+  <li>GNUnet on a FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0pre66.tar.gz</li>
+  <li>GNUnet GTK on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
+  <li>GNUnet FUSE on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
+  <li>GNUnet on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-0.11.0pre66.tar.gz</li>
+  <li>GNUnet GTK on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
+  <li>GNUnet FUSE on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
+</ul>
+<p>
+  Note that GNUnet is now started using &quot;gnunet-arm -s&quot;. GNUnet should be stopped using &quot;gnunet-arm -e&quot;.
+</p>
+<h4 class="western">Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff,
+  Matthias Wachs, Bart Polot, Sree Harsha Totakura, Nathan S. Evans,
+  Martin Schanzenbach, Julius B&uuml;nger, Nils Gillmann, Philipp
+  T&ouml;lke, Florian Dold, &#1056;&#1091;&#1089;&#1083;&#1072;&#1085;
+  &#1048;&#1078;&#1073;&#1091;&#1083;&#1072;&#1090;&#1086;&#1074;,
+  tg(x), David Barksdale, Christian Fuchs, Nils Durner, Omar Tarabai,
+  Maximilian Szengel, Supriti Singh, lurchi, David Brodski, xrs, Fabian
+  Oehlmann, Carlo von lynX, Christophe Genevey Metat, Jeffrey Burdges,
+  Safey A.Halim, Daniel Golle, Phil, Bruno Cabral, Ji Lu, Heikki
+  Lindholm, Markus Teich, t3sserakt, Claudiu Olteanu, Marcello
+  Stanisci, Moon, anryko, Arthur Dewarumez, Julien Morvan, Adnan H, Lin
+  Tong, Andreas Fuchs, Christian Rupp, jah, Alejandra Morales, Matthias
+  Kolja Miehl, Andrew Cann, Antonio Ojea, Pascal Mainini, amirouche and
+  hark. 
+</p>
+{% endblock body_content %}
diff --git a/template/news/2018-07.html.j2 b/template/news/2018-07.html.j2
new file mode 100644
index 00000000..e8c14fea
--- /dev/null
+++ b/template/news/2018-07.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Second GNUnet Hacker Meeting 2018 at La D&#233;centrale, Switzerland</h1>
+  <p>
+    The GNUnet hackers met for the second time this year. The primary goal was to squash bugs to bring out a new release. Aside from this we worked hard on improving the documentation and to launch this new website.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.0.html.j2 b/template/news/2019-0.11.0.html.j2
new file mode 100644
index 00000000..ddf04623
--- /dev/null
+++ b/template/news/2019-0.11.0.html.j2
@@ -0,0 +1,72 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.0 released</h1>
+  <p>
+    We are pleased to announce the release of GNUnet 0.11.0.<br>
+  This is a major release after about five years of development.  In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.0 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.0</h4>
+<ul>
+  <li>The Web site and manuals have undergone significant rework. You can find an archive of the old Web site at <a href="http://web.archive.org/web/*/gnunet.org">archive.org</a>.</li>
+  <li>The code now builds again on macOS. GNUnet on macOS is <i>experimental</i>. While it builds and seems to run fine, some tests are known to fail.</li>
+  <li>Build process now works properly with libidn2</li>
+  <li>Except for <tt>gnunet-qr</tt>, all Python code was migrated to Python 3.7.</li>
+  <li>Fixed security issues in secret sharing cryptography logic</li>
+  <li>Services running out of file descriptors on <tt>accept()</tt> no longer busy wait</li>
+  <li>Fixed crash in gnunet-gns2dns proxy</li>
+  <li>GNS responses are now padded to minimize information disclosure from the size</li>
+  <li>Fixed API issues and (rare) crash bugs in CADET</li>
+  <li>The experimental SecuShare code is not included in the release, you can now find it in the <a href="https://git.gnunet.org/gnunet-secushare.git/">gnunet-secushare</a> Git repository.</li>
+  <li>The Ascension tool (separate download) now allows importing DNS zones into GNS via AXFR.</li>
+  <li>GNUnet now includes a decentralised identity attribute sharing service: reclaimID. A ready-to-use client can be found in an <a href="https://gitlab.com/reclaimid/client">external repo</a>.</li>
+  <li>The code now builds again on NetBSD. GNUnet on NetBSD is <i>experimental</i>. While it builds and seems to run fine, full support requires more changes in the core of GNUnet It will soon be available via pkgsrc.</li>
+  <li>Many things changed on the build system side. If you package GNUnet for an operating system or otherwise package manager, make sure that you read the README.</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=258">over 100 individual issues</a> that were resolved since 0.11.0pre66.
+</p>
+  <h4>Known Issues</h4>
+  <ul>
+    <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+    <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+    <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+    <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+    <li>The RPS subsystem remains experimental.</li>
+    <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+  </ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 150 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people
+  contributed code and were thus easily identified:
+  Christian Grothoff, Matthias Wachs, Bart Polot, Sree Harsha Totakura,
+  Nathan S. Evans, Martin Schanzenbach, Julius B&#xFC;nger, ng0,
+  Philipp T&#xF6;lke, Florian Dold, &#x420;&#x443;&#x441;&#x43B;&#x430;&#x43D; &#x418;&#x436;&#x431;&#x443;&#x43B;&#x430;&#x442;&#x43E;&#x432;, tg(x), David Barksdale,
+  Christian Fuchs, Nils Durner, Omar Tarabai, Maximilian Szengel, Supriti
+  Singh, lurchi, David Brodski, xrs, Fabian Oehlmann, Carlo von lynX,
+  Christophe Genevey Metat, Jeffrey Burdges, Safey A.Halim, Daniel Golle,
+  Phil, Bruno Cabral, Ji Lu, Heikki Lindholm, Markus Teich, t3sserakt,
+  Claudiu Olteanu, Marcello Stanisci, Moon, Hernani Marques, anryko, Arthur Dewarumez,
+  Julien Morvan, Adnan H, rexxnor, Lin Tong, Andreas Fuchs, Christian Rupp, jah,
+  Alejandra Morales, Bernd Fix, Feideus, Matthias Kolja Miehl, Andrew Cann, Antonio Ojea,
+  Pascal Mainini, amirouche and hark.
+  <a href="https://bugs.gnunet.org/view.php?id=5569">Special thanks</a> to Florian Weimer.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.1.html.j2 b/template/news/2019-0.11.1.html.j2
new file mode 100644
index 00000000..82f27c85
--- /dev/null
+++ b/template/news/2019-0.11.1.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.1 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.1.
+  <br>
+  This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.1 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.1.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.1</h4>
+<ul>
+  <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
+  <li>REST and GNS proxy configuration options for address binding were added</li>
+  <li>gnunet-publish by default no longer includes creation time</li>
+  <li>Unreliable message ordering logic in CADET was fixed</li>
+  <li>Various improvements to build system and documentation</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312"> 14 individual issues</a> that were resolved since 0.11.0.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.2.html.j2 b/template/news/2019-0.11.2.html.j2
new file mode 100644
index 00000000..504a203c
--- /dev/null
+++ b/template/news/2019-0.11.2.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.2 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.2.
+<br>
+  This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.2 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.2.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.2</h4>
+<ul>
+  <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
+  <li>REST and GNS proxy configuration options for address binding were added</li>
+  <li>gnunet-publish by default no longer includes creation time</li>
+  <li>Unreliable message ordering logic in CADET was fixed</li>
+  <li>Various improvements to build system and documentation</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312">14 individual issues</a> that were resolved since 0.11.0.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.3.html.j2 b/template/news/2019-0.11.3.html.j2
new file mode 100644
index 00000000..50b207a1
--- /dev/null
+++ b/template/news/2019-0.11.3.html.j2
@@ -0,0 +1,52 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.3 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.3.
+<br>
+  This is a bugfix release for 0.11.2, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.3 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.3.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.3 (since 0.11.2)</h4>
+<ul>
+  <li>gnunet-zoneimport now handles <tt>-h</tt> correctly</li>
+  <li><tt>iptables</tt> and other similar binaries are no longer hard-coded but detected at configure time (with hard-coded fallback locations).</li>
+  <li><tt>make uninstall</tt> now properly uninstalls all files</li>
+  <li>Passing the no longer available <tt>--with-nssdir</tt> configuration option now results in a hard error.</li>
+  <li><tt>GNUNET_memcmp()</tt> and <tt>GNUNET_is_zero()</tt> macros introduced for improved type safety (but not yet used consistently).</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.4.html.j2 b/template/news/2019-0.11.4.html.j2
new file mode 100644
index 00000000..9aad565f
--- /dev/null
+++ b/template/news/2019-0.11.4.html.j2
@@ -0,0 +1,50 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.4 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.4.
+<br>
+  This is a bugfix release for 0.11.3, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.4 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.4.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.4 (since 0.11.3)</h4>
+<ul>
+  <li><tt>gnunet-arm -s </tt> no longer logs into the console by default and instead into a logfile (in $GNUNET_HOME).</li>
+  <li>The reclaim subsystem is no longer experimental. See also <a href="https://reclaim-identity.io">re:claimID</a>. Further, the internal encryption scheme moved from ABE to GNS-style encryption.</li>
+  <li>GNUnet now depends on a more recent version of libmicrohttpd.</li>
+  <li>The REST API now includes read-only access to the configuration.</li>
+  <li>All manpages are now in mdocml format.</li>
+  <li><tt>gnunet-download-manager.scm</tt> removed.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.5.html.j2 b/template/news/2019-0.11.5.html.j2
new file mode 100644
index 00000000..049aa8b5
--- /dev/null
+++ b/template/news/2019-0.11.5.html.j2
@@ -0,0 +1,47 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.5 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.5.
+<br>
+  This is a bugfix release for 0.11.4, mostly fixing a few minor bugs and improving performance, in particular for identity management with a large number of egos. In the wake of this release, we also launched the <a href="https://rest.gnunet.org">REST API documentation</a>. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.5 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-gtk saw some minor changes to adopt it to API changes in the main code related to the identity improvements. gnunet-fuse was not released again, as there were no changes and the 0.11.0 version is expected to continue to work fine with gnunet-0.11.5.
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.5 (since 0.11.4)</h4>
+<ul>
+  <li><tt>gnunet-identity</tt> is much faster when creating or deleting egos given a large number of existing egos.</li>
+  <li>GNS now supports CAA records.</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Marcello Stanisci, ng0, Martin Schanzenbach and Bernd Fix.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.6.html.j2 b/template/news/2019-0.11.6.html.j2
new file mode 100644
index 00000000..3ee063b3
--- /dev/null
+++ b/template/news/2019-0.11.6.html.j2
@@ -0,0 +1,52 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.6 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.6.
+<br>
+  This is a bugfix release for 0.11.5, fixing a lot of minor bugs, improving stability and code quality. Further, our videos are back on the homepage. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.6 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse was not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.6.
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.6 (since 0.11.5)</h4>
+<ul>
+  <li><tt>gnunet-identity</tt> can now print private keys.</li>
+  <li>The <tt>REST</tt> service can be configured to echo the HTTP Origin header value for Cross-Origin-Resource-Sharing (CORS) when it is called by a browser plugin. Optionally, a CORS Origin to echo can be also be directly configured.</li>
+  <li><tt>re:claimID</tt> tickets are now re-used whenever possible.</li>
+  <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
+  <li><tt>TRANSPORT</tt>, <tt>TESTBED</tt> and <tt>CADET</tt> tests now pass again on macOS.</li>
+  <li><tt>CADET</tt>: Replaced enum <tt>GNUNET_CADET_ChannelOption</tt> with <tt>GNUNET_MQ_PriorityPreferences</tt> in preparation of API changed in the future.</li>
+  <li>The GNS proxy Certification Authority is now generated using gnutls-certtool, if available, with opennssl/certtool as fallback.</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Martin Schanzenbach, Julius B&uuml;nger, ng0, Christian Grothoff, Alexia Pagkopoulou, rexxnor, xrs, lurchi and t3sserakt.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.7.html.j2 b/template/news/2019-0.11.7.html.j2
new file mode 100644
index 00000000..f2b38231
--- /dev/null
+++ b/template/news/2019-0.11.7.html.j2
@@ -0,0 +1,56 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.7 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.7.
+<br>
+  This is a bugfix release for 0.11.6, fixing a lot of minor bugs, improving stability and code quality. Further, win32 support was removed for reasons you may read below. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.7 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse is not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.7. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.7 (since 0.11.6)</h4>
+<ul>
+  <li><tt>ARM</tt>: GNUnet CLI tools are now able to detect if gnunet(-arm) is not running and will exit with a warning (before the command would just hang and wait for GNUnet to be started). #5906</li>
+  <li>win32 and mingw support were dropped, which resulted in a significant number of lines of code to be gone. The code has been unmaintained in our code base for many years and there are no known users. For details and further reasons refer to the discussion <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-09/msg00002.html">in our archives</a>.</li>
+  <li>Removal of plibc, win32 and mingw support means you can now compile gnunet without requiring a Cxx compiler (you just need a C compiler). #5877</li>
+  <li><tt>REST</tt>: The new config endpoints can now be used to read and write the GNUnet config. #5808</li>
+  <li><tt>REST</tt>: The service is not started per user in multiuser setups.</li>
+  <li><tt>REST</tt>: Added tests for namestore and GNS. #5638</li>
+  <li><tt>re:claimID / OIDC</tt>: Now supports <a href="https://tools.ietf.org/html/rfc7636">PKCE</a>. #5807</li>
+  <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
+  <li><tt>CREDENTIAL</tt> subsystem reworked and renamed to <tt>ABD</tt> (attribute-based delegation).</li>
+  <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00023.html">Minor TRANSPORT fixes</a> and <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00022.html">NAT changes</a>.</li>
+  <li><tt>GNS</tt> prepared code for <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001 changes</a>. #5920</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Martin Schanzenbach, ng0, Christian Grothoff, Alexia Pagkopoulou, Andreas Ebner, Corvus Corax, xrs and t3sserakt.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.8.html.j2 b/template/news/2019-0.11.8.html.j2
new file mode 100644
index 00000000..9a92eaac
--- /dev/null
+++ b/template/news/2019-0.11.8.html.j2
@@ -0,0 +1,47 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.8 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.8.
+<br>
+  This is a hotfix release for 0.11.7. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.8 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse and gnunet-gtk were not released again, as there were no changes and the 0.11.0/0.11.7 versions are expected to continue to work fine with gnunet-0.11.8. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.8 (since 0.11.7)</h4>
+<ul>
+  <li><tt>GNS</tt> Portability fixes.</li>
+  <li><tt>PQ</tt>: Fixed build with postgresql plugin. (Regression introduces as part of #5733)</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Daniel Golle.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.12.0.html.j2 b/template/news/2019-0.12.0.html.j2
new file mode 100644
index 00000000..6cf68160
--- /dev/null
+++ b/template/news/2019-0.12.0.html.j2
@@ -0,0 +1,85 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.11.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.11.x GNUnet network, and interactions between old and new peers
+  will result in signature verification failures.  0.11.x peers will <b>NOT</b>
+  be able to communicate with Git master or 0.12.x peers.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.12.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.12.0 (since 0.11.8)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Changed key derivation protocols to adhere with <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001</a>. <a href="https://bugs.gnunet.org/view.php?id=5921">#5921</a></li>
+      <li>Names are not expected to be UTF-8 (as opposed to IDNA). <a href="https://bugs.gnunet.org/view.php?id=5922">#5922</a></li>
+      <li>NSS plugin now properly handles non-standard IDNA names. <a href="https://bugs.gnunet.org/view.php?id=5927">#5927</a></li>
+      <li>NSS plugin will refuse to process requests from root (as GNUnet code should never run as root). <a href="https://bugs.gnunet.org/view.php?id=5927">#5907</a></li>
+      <li>Fixed BOX service/protocol label parsing (for TLSA et al)</li>
+    </ul>
+  </li>
+  <li><tt>GNS/NSE</tt>: Zone revocation proof of work algorithm changed to be less susceptible to specialized ASIC hardware.
+  <a href="https://bugs.gnunet.org/view.php?id=3795">#3795</a></li>
+  <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Improved and documented RSA binary format. <a href="https://bugs.gnunet.org/view.php?id=5968">#5968</a></li>
+      <li>Removed redundant hashing in EdDSA signatures. <a href="https://bugs.gnunet.org/view.php?id=5398">#5398</a></li>
+      <li>The <tt>gnunet-logread</tt> script for log auditing (requires perl) can now be installed.</li>
+      <li>Now using <a href="https://tweetnacl.cr.yp.to/">TweetNaCl</a> for ECDH implementation.</li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: A significant number of build system issued have been fixed and improvements implemented, including:
+    <ul>
+      <li>GLPK dependency dropped.</li>
+      <li>Fixed guix package definition.</li>
+    </ul>
+  </li>
+  <li><tt>Documentation</tt>: Improvements to the handbook and documentation.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Florian Dold, xrs, Naomi Phillips and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.12.1.html.j2 b/template/news/2019-0.12.1.html.j2
new file mode 100644
index 00000000..7911fcd1
--- /dev/null
+++ b/template/news/2019-0.12.1.html.j2
@@ -0,0 +1,26 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.1 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.1.
+<br>
+  This is a very minor release. It largely fixes one function that is
+  needed by GNU Taler 0.6.0.  Please read the release notes
+  for GNUnet 0.12.0, as they still apply. Updating is only recommended
+  for those using GNUnet in combination with GNU Taler.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>D8423BCB326C7907033929C7939E6BE1E29FC3CC</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-02.html.j2 b/template/news/2019-02.html.j2
new file mode 100644
index 00000000..0925eb75
--- /dev/null
+++ b/template/news/2019-02.html.j2
@@ -0,0 +1,75 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>2019-02: Topics for GSoC 2019</h1>
+<p>
+  GNUnet is participating in the Google Summer of Code again through GNU. If you are interested in any of these projects, reach out to us!
+</p>
+<section>
+  <h4>Android Port</h4>
+  <p>
+    It is time for GNUnet to run properly on Android.  Note that GNUnet is written in C, and this is not about rewriting GNUnet in Java, but about getting the C code to run on Android.<br>
+    Mentor: <a href="https://www.goebel-consult.de/">Hartmut Goebel</a>
+  </p>
+</section>
+<section>
+  <h4>Help with Continuous Integration setup</h4>
+  <p>
+    There is a push for migrating our CI to Gitlab.  The CI should eventually not just run "make check" on various platforms, but also perform tests with multiple peers running in different VMs with specific network topologies (i.e. NAT) between them being simulated. The CI should also be integrated with Gauger for performance regression analysis.  Running jobs only when dependencies have changed and scripting more granular triggers or ideally automatic dependency discovery (as done by the autotools) is also important.<br>
+    Mentor: TBD
+  </p>
+</section>
+<section>
+  <h4>Migrate gnunet-qr from Python 2.7 to C using libzbar</h4>
+  <p>
+    Python 2.7 is reaching its end-of-life, and we want to get rid of the dependency on Python. The existing gnunet-qr tool is a rather simple wrapper around python-zbar, which itself wraps  libzbar. The goal of this project is to directly use libzbar to scan QR codes for GNUnet / the GNU Name System (see also <a href="https://bugs.gnunet.org/view.php?id=5562">#5562</a>).<br>
+    Mentor: Christian Grothoff
+  </p>
+</section>
+<section>
+  <h4>re:claimID OpenID Connect performance improvements</h4>
+  <p>
+    reclaimID is a decentralized identity system build on top of the GNU Name System. Upon authorization, the user provides a requesting party (RP) such as a website with an authorization ticket (e.g. piggybacked in an OpenID authorization code). The RP uses information contained in this ticket to
+  </p>
+  <ol>
+    <li> Retrieve the decryption key from GNS</li>
+    <li> Retrieve the user attributes from GNS</li>
+  </ol>
+  <p>
+    The GNS lookups ensure that the RP receives up-to-date attributes and functional decryption keys. However, in particular the RP-specific encryption key resolution can be slow and even fail depending on the network topology. We propose that in an initial exchange, in particular OpenID authorization code flows, we try to incorporate key and maybe even an attribute set in the ticket exchange. In order to mitigate this issue, this project is meant to investigate and implement how...
+  </p>
+  <ol>
+    <li> ... decryption keys can be added to an initial exchange in OpenID.</li>
+    <li> ... initial set(s) of attributes can be piggybacked in OpenID.</li>
+  </ol>
+  <p>
+    Mentor: Martin Schanzenbach
+  </p>
+</section>
+<section>
+  <h4>re:claimID alternative GNS-based encryption</h4>
+  <p>
+    re:claimID is a decentralized identity system build on top of the GNU Name System. The initial design and implementation of re:claimID includes an attribute-based encryption module in order to prevent unauthorized access to attributes in the name system. Our motivation for re:claimID was for it to be name system agnostic, which means the design theoretically also works for other name systems such as namecoin. Other name systems often do not have built-in mechanisms in order to do this. Hence, we implemented an ABE access control layer. Our ABE implementation requires two third party libraries: libpbc and libgabe. While we could merge libgabe into the gnunet service implementation of re:claimID, libpbc is a rather large, third party library which lacks packaging in distributions and for platforms. On the other hand, GNS supports record data encryption using symmetric keys as labels. If we make the access control layer of re:claimID more generic in order to support both ABE and GNS encryption, we could reduce the required depenencies. This would result in gnunet packages to include re:claimID by default. In short, the goals are to...
+  </p>
+  <ol>
+    <li> ... improve performance by reducing encryption overhead.</li>
+    <li> ... reduce dependencies.</li>
+  </ol>
+  <p>
+    Mentor: Martin Schanzenbach
+  </p>
+</section>
+<section>
+  <h4>Enable all networking applications to run over GNUnet out of the box</h4>
+  <p>
+    One great problem of the current Internet is the lack of disintermediation. When people want to talk they need a chat service. When they want to share files they need a file transfer service. Although GNUnet already possesses quite advanced integration into Linux networking, a little extra work is needed for existing applications like irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. Once people have added a person to their GNS they can immediately message, exchange files and suchlike directly, with nothing but the GNUnet in the middle, using applications that have been distributed with unix systems ever since the 1980&#39;s. We can produce an OS distribution where these things work out of the box with the nicknames of people instead of cloud services. For more information and context, read <a href="https://bugs.gnunet.org/view.php?id=4625">bug id 4625</a>.
+  </p>
+  <p>
+    Mentors: lynX &amp; dvn
+  </p>
+</section>
+{% endblock body_content %}
diff --git a/template/news/2019-06-DSTJ.html.j2 b/template/news/2019-06-DSTJ.html.j2
new file mode 100644
index 00000000..0d1d3c67
--- /dev/null
+++ b/template/news/2019-06-DSTJ.html.j2
@@ -0,0 +1,14 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Peer DSTJ is dead, long live peer Y924</h1>
+<p>
+  After some issues with our infrastructure we needed to replace our bootstrapping peer. To avoid problems when connecting to GNUnet the operator of a peer needs to update its node by removing the peer ID <i>DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</i> from the system. Here are two strategies to find copies of the respective file:
+</p>
+<ol>
+  <li><tt>$ locate DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
+  <li><tt>$ find / -name DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
+</ol>
+<p>
+  Update: DSTJ has now been blacklisted. Please update your GNUnet peer.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-06.html.j2 b/template/news/2019-06.html.j2
new file mode 100644
index 00000000..295138b9
--- /dev/null
+++ b/template/news/2019-06.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet Hacker Meeting 2019 at La D&#233;centrale, Switzerland</h1>
+  <p>
+    The members of the GNUnet community met again in the wonderful souroundings of St. Imier to hack on GNUnet. New people joined our sessions until late at night. From bug squashing to digging our own dog food, from workshops to theoretical discussions of new services and usecases. And of course, pizza was in the game. 
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-07-GHM_Aug_2019.html.j2 b/template/news/2019-07-GHM_Aug_2019.html.j2
new file mode 100644
index 00000000..c846432e
--- /dev/null
+++ b/template/news/2019-07-GHM_Aug_2019.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet Hacker Meeting in August 2019 at Wernsdort (near Berlin)</h1>
+  <p>
+    In August 2019, some of us met in Wernsdorf for focused work on GNUnet.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-10-GNSSpec1.html.j2 b/template/news/2019-10-GNSSpec1.html.j2
new file mode 100644
index 00000000..3941c162
--- /dev/null
+++ b/template/news/2019-10-GNSSpec1.html.j2
@@ -0,0 +1,19 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 1/4</h1>
+<p>
+  We are happy to announce the completion of the first milestone for the GNS Specification. The objective is to provide a detailed and comprehensive guide for implementors of the GNU Name System. The initial milestone consists of documenting the cryptographic principles of GNS data structures. This includes the specification of the GNS record wire and serialization formats as well as internationalization.<br>
+  <i>NOTE: The currently specified protocol is planned to be implemented for GNUnet 0.12. The current GNS implementation (0.11) exhibits minor but compatibility breaking deviations from this specification.</i> The draft specification <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  The next milestone will bring the resolver logic specification.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-10-ICANNPanel.html.j2 b/template/news/2019-10-ICANNPanel.html.j2
new file mode 100644
index 00000000..08885fa6
--- /dev/null
+++ b/template/news/2019-10-ICANNPanel.html.j2
@@ -0,0 +1,13 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet project invited to ICANN66</h1>
+<p>
+  We are delighted to announce that ICANN has invited the GNUnet project to speak at the <a href="https://meetings.icann.org/en/montreal66">next ICANN Annual General Meeting</a>. We have been invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>. ICANN generously offered to cover travel and accomodation.
+</p>
+<p>
+  The meeting will take place in Montreal between 2 - 7 November. The panel will tentatively be help on November 6th.
+</p>
+<p>
+  <b>UPDATE:</b> The panel is on Tueday, November 5th 13:30 EDT with the possibility of remote participation: <a href="https://66.schedule.icann.org/meetings/1116895">Link</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-11-ICANNUpdate.html.j2 b/template/news/2019-11-ICANNUpdate.html.j2
new file mode 100644
index 00000000..1edbbb8c
--- /dev/null
+++ b/template/news/2019-11-ICANNUpdate.html.j2
@@ -0,0 +1,10 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS&#64;ICANN66</h1>
+<p>
+  The <a href="https://meetings.icann.org/en/montreal66">ICANN Annual General Meeting</a> is concluded. We were invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>.
+</p>
+<p>
+  You can find the presentation on GNS in <a href="{{ url_localized('video.html') }}">our video section</a>. The handshake.org project, which proposes a decentralized, blockchain-based governance of the root zone (as opposed to governance by ICANN), joined us on the panel. The full video including questions and answers can be found <a href="https://icann.zoom.us/recording/share/M8N-Duq935XheIZoBedIwmi3VqRUAe2iOPwECiTNLxKwIumekTziMw?startTime=1572978711000">here</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-12-UpcomingTalks.html.j2 b/template/news/2019-12-UpcomingTalks.html.j2
new file mode 100644
index 00000000..b92d1cdd
--- /dev/null
+++ b/template/news/2019-12-UpcomingTalks.html.j2
@@ -0,0 +1,73 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Upcoming GNUnet Talks</h1>
+  <p>There will be various talks in the next few months on GNUnet and related
+  projects on both the Chaos Communication Congress (36C3) as well as FOSDEM.
+  Here is an overview:
+  </p>
+  <h2>Privacy and Decentralization @ 36c3 (YBTI)</h2>
+  <p>
+    We are pleased to have 5 talks to present as part of our
+    "youbroketheinternet/wefixthenet" session, taking place on the
+    <a href="https://oio.social/">OIO (Open
+    Infrastructure Orbit)</a> stage:
+  </p>
+    <ul>
+      <li>
+        "re:claimID - Self-sovereign, Decentralised Identity Management and
+        Personal Data Sharing" by Hendrik Meyer zum Felde
+        will take place at 2019-12-27 18:30 in OIO Stage.
+        <a href="https://talks.oio.social/36c3-oio/talk/XHLTUD/">Info</a>
+      </li>
+      <li>
+        "Buying Snacks via NFC with GNU Taler" by Dominik Hofer
+        will take place at 2019-12-27 21:20 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/MMB78C/">Info</a>
+      </li>
+      <li>
+        "CloudCalypse 2: Social network with net2o" by Bernd Paysan
+        will take place at 2019-12-28 21:20 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/GUZH7V/">Info</a>
+      </li>
+      <li>
+        "Delta Chat: e-mail based messaging, the Rustocalypse and UX driven
+        approach" by holger krekel
+        will take place at 2019-12-29 17:40 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/WSLWVM/">Info</a>
+      </li>
+      <li>
+        "Cryptography of Killing Proof-of-Work" by Jeff Burdges
+        will take place at 2019-12-30 12:00 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/GGV8G3/">Info</a>
+      </li>
+    </ul>
+  <p>
+    In addition to these talks, we will be hosting a snack machine which
+    accepts <a href="https://taler.net">Taler</a> for payment.
+    The first of its kind! It will be filled
+    with various goodies, including Swiss chocolates, books, and electronics.
+    The machine will be located somewhere in the OIO assembly, and there
+    will be a station at which you may exchange Euro for digital Euro for
+    immediate use.
+    We welcome all to come try it out. :)
+  </p>
+  <h2>Decentralized Internet and Privacy devroom @FOSDEM 2020</h2>
+  <p>
+    We have 2 GNUnet-related talks at the
+    <a href="https://fosdem.org/2020/schedule/track/decentralized_internet_and_privacy/">
+    Decentralized Internet and Privacy devroom</a> at FOSDEM 2020 in February:
+  </p>
+  <ul>
+    <li>
+      GNUnet: A network protocol stack for building secure, distributed, and
+      privacy-preserving applications
+      <a href="https://fosdem.org/2020/schedule/event/dip_gnunet/">Info</a>
+    </li>
+    <li>
+      Knocking Down the Nest: secushareBOX - p2p, encrypted IoT and beyond...
+      <a href="https://fosdem.org/2020/schedule/event/dip_secusharebox/">Info</a>
+    </li>
+  </ul>
+{% endblock body_content %}
diff --git a/template/news/2020-01-0.12.2.html.j2 b/template/news/2020-01-0.12.2.html.j2
new file mode 100644
index 00000000..21375aa6
--- /dev/null
+++ b/template/news/2020-01-0.12.2.html.j2
@@ -0,0 +1,71 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.2 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.2.
+<br>
+  This is a new bugfix release.
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.12.2 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.12.2 (since 0.12.1)</h4>
+<ul>
+  <li>
+    <tt>GNS</tt>: Resolver clients are now able to specify a recursion depth limit.
+  </li>
+  <li>
+    <tt>TRANSPORT/TNG</tt>: The transport rewrite (aka TNG) is underway and
+    various transport components have been worked on, including TCP, UDP and UDS
+    communicators.
+  </li>
+  <li>
+    <tt>RECLAIM</tt>: Added preliminary support for third party attested
+    credentials.
+  </li>
+  <li>
+    <tt>UTIL</tt>: The cryptographic changes introduced in 0.12.0 broke ECDSA
+      ECDH and consequently other components. The offending ECDSA key normalization
+      was dropped.
+  </li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Christian Ulrich, dvn, lynx and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-01-GNSSpec2.html.j2 b/template/news/2020-01-GNSSpec2.html.j2
new file mode 100644
index 00000000..e673d35d
--- /dev/null
+++ b/template/news/2020-01-GNSSpec2.html.j2
@@ -0,0 +1,28 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 2/4</h1>
+<p>
+  We are happy to announce the completion of the second milestone for the GNS
+  Specification. The second milestone consists of documenting the GNS name
+  resolution process and record handling.<br>
+  With the release of GNUnet 0.12.x, the currently specified protocol is
+  implemented according to the specification. As before, the draft specification
+  <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  As already announced on the <a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-01/msg00000.html">mailing list</a>,
+  the Go implementation of GNS is also proceeding as planned and implements the
+  specification.
+</p>
+<p>
+  The next and third milestone will cover namespace revocation.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-05-GHM_Jun_2020.html.j2 b/template/news/2020-05-GHM_Jun_2020.html.j2
new file mode 100644
index 00000000..f270d87d
--- /dev/null
+++ b/template/news/2020-05-GHM_Jun_2020.html.j2
@@ -0,0 +1,8 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Online GNUnet Hacker Meeting in June 2020</h1>
+  <p>
+    We are happy to announce that we will have a GNUnet
+    Hacker Meeting from 17-21 of June 2020 taking place online. For more information see <a href="https://md.hasi.it/s/gnunet">here</a>.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2020-06-GNSSpec3.html.j2 b/template/news/2020-06-GNSSpec3.html.j2
new file mode 100644
index 00000000..2e69ccb9
--- /dev/null
+++ b/template/news/2020-06-GNSSpec3.html.j2
@@ -0,0 +1,25 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 3/4</h1>
+<p>
+  We are happy to announce the completion of the third milestone for the GNS
+  Specification. The third milestone consists of documenting the GNS zone
+  revocation process. As part of this, we have reworked the proof-of-work
+  algorithms in GNUnet also used for GNS revocations.<br>
+  The (protocol breaking) changes will be released as part of GNUnet 0.13.0.
+  The specification document <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  In preparation for the fourth and last milestone, we have started the
+  <a href="https://mailarchive.ietf.org/arch/msg/secdispatch/Kj8zXoQssiFLp8bM5l5n1OtXt7s/">IETF process to find a working group</a> and expect to present our
+  work initially at <a href="https://ietf.org/how/meetings/108/">IETF 108</a>.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.0.html.j2 b/template/news/2020-07-0.13.0.html.j2
new file mode 100644
index 00000000..ef8c0d89
--- /dev/null
+++ b/template/news/2020-07-0.13.0.html.j2
@@ -0,0 +1,103 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.13.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.13.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.12.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.12.x GNUnet network, and interactions between old and new peers
+  will result in signature verification failures.  0.12.x peers will <b>NOT</b>
+  be able to communicate with Git master or 0.13.x peers.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.13.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.0 (since 0.12.2)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
+      <li>NSS plugin "block" fixed. <a href="https://bugs.gnunet.org/view.php?id=5782">#5782</a></li>
+      <li>Broken set NICK API removed.<a href="https://bugs.gnunet.org/view.php?id=6092">#6092</a></li>
+      <li>New record flags: SUPPLEMENTAL. Records which are not explicitly
+       configured/published under a specific label but which are still
+       informational are returned by the resolver and flagged accordingly. <a href="https://bugs.gnunet.org/view.php?id=6103">#6103</a></li>
+      <li><tt>gnunet-namestore</tt> now complains when adding TLSA or SRV records outside of a BOX</li>
+    </ul>
+  </li>
+  <li>
+    <tt>CADET</tt>: Fixed tunnel establishment as well as an outstanding bug regarding tunnel destruction. <a href="https://bugs.gnunet.org/view.php?id=5822">#5822</a>
+  </li>
+  <li><tt>GNS/REVOCATION</tt>: Revocation proof of work has function changed to
+  argon2 and modified to reduce variance.</li>
+  <li><tt>RECLAIM</tt>: Increased ticket length to 256 bit. <a href="https://bugs.gnunet.org/view.php?id=6047">#6047</a></li>
+  <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Serialization / file format of ECDSA private keys harmonized with
+      other libraries. Old private keys will no longer work! <a href="https://bugs.gnunet.org/view.php?id=6070">#6070</a></li>
+      <li>Now using <a href="https://doc.libsodium.org/">libsodium</a> for EC
+      cryptography.</li>
+      <li>Builds against cURL which is not linked against gnutls are now possible but still not recommended.
+      Configure will warn that this will impede the GNS functionality. This change will make hostlist discovery
+      work more reliable for some distributions.</li>
+      <li><tt>GNUNET_free_non_null</tt> removed. <tt>GNUNET_free</tt> changed to not assert that the pointer is not NULL.
+      For reference see the <a href="https://taler.net/papers/codeblau-report-2020-q2.pdf">Taler security audit</a>.</li>
+      <li>AGPL request handlers added GNUnet and extension templates.</li>
+    </ul>
+  </li>
+  <li><b>(NEW) </b><tt>GANA Registry</tt>: We have established a registry to be used for names and numbers in GNUnet.
+  This includes constants for protocols including GNS record types and GNUnet peer-to-peer messages. See <a href="https://gana.gnunet.org">GANA</a>.</li>
+  <li><b>(NEW) </b><tt>Living Standards</tt>: LSD subdomain and LSD0001 website: <a href="https://lsd.gnunet.org/lsd0001">LSD0001</a></li>
+  <li><b>(NEW) </b><tt>Continuous integration</tt>: <a href="https://buildbot.gnunet.org">Buildbot</a> is back.</li>
+  <li><tt>Buildsystem</tt>: A significant number of build system changes:
+    <ul>
+      <li>libmicrohttpd and libjansson are now required dependencies.</li>
+      <li>New dependency: <a href="https://doc.libsodium.org/">libsodium</a>.</li>
+      <li>Fixed an issue with libidn(2) detection.</tt>
+    </ul>
+  </li>
+</ul>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/roadmap_page.php?version_id=338">0.13.0 bugtracker</a>.
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Jonathan Buchanan, t3sserakt, nikita and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.1.html.j2 b/template/news/2020-07-0.13.1.html.j2
new file mode 100644
index 00000000..b7670242
--- /dev/null
+++ b/template/news/2020-07-0.13.1.html.j2
@@ -0,0 +1,29 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.13.1 released</h1>
+<p>
+  This is a bugfix release for gnunet and gnunet-gtk specifically.
+  <br>
+  For gnunet, no changes to the source have been made. However,
+  the default configuration had to be modified to support the changes
+  made in 0.13.0.
+  <br>
+  For gnunet-gtk, this fixes a more serious issue where the
+  0.13.0 tarball failed to build.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-08-0.13.2.html.j2 b/template/news/2020-08-0.13.2.html.j2
new file mode 100644
index 00000000..3dfa7e61
--- /dev/null
+++ b/template/news/2020-08-0.13.2.html.j2
@@ -0,0 +1,58 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.13.2 released</h1>
+<p>
+  This is a bugfix release for gnunet 0.13.1.<br/>
+  It fixes some build issues and contains changes to the REST API
+  implmementation (no change in the API itself) as well as OpenID Connect related
+  fixes to re:claimID.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.2 (since 0.13.1)</h4>
+<ul>
+  <li><tt>REST</tt>:
+    <ul>
+      <li>Plugins may now handle any namespace. <a href="https://bugs.gnunet.org/view.php?id=6462">#6462</a></li>
+      <li>Fixed incomplete/missing cleanup and teardown of REST plugins.</li>
+    </ul>
+  </li>
+  <li><tt>RECLAIM</tt>:
+    <ul>
+      <li>Support for <tt>/.well-known/openid-configuration</tt>. <a href="https://bugs.gnunet.org/view.php?id=6463">#6463</a></li>
+      <li>Support for standard scope values (<tt>profile, address, email, phone</tt>) and corresponding mapping to standard claim values</li>
+      <li>Correct processing of <tt>claims</tt> parameter for individual claim requests.</li>
+      <li>Support for <tt>POST</tt> token request.</li>
+      <li>Support for public clients (Token request without client secrets).</li>
+      <li>Fixed urlencoding of parameters on redirect</li>
+    </ul>
+  </li>
+  <li><tt>UTIL</tt>: New string API for percent-encode/decode.</li>
+  <li><tt>MYSQL</tt>: Fix version detection and build against mysql-8 and later. <a href="https://bugs.gnunet.org/view.php?id=6465">#6465</a></li>
+  <li><tt>POSTGRESQL</tt>: Ensure postgresql fails hard if there is an error in the SQL. <a href="https://bugs.gnunet.org/view.php?id=6437">#6437</a></li>
+  <li><tt>Extensions</tt>:
+    <ul>
+      <li>Load GNSRECORD plugins within GNUnet's context.</li>
+      <li>Add convenience function to return GNUnet's default configuration.</li>
+    </ul>
+  </li>
+</ul>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Alessio Vanni, t3sserakt, Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-09-0.13.3.html.j2 b/template/news/2020-09-0.13.3.html.j2
new file mode 100644
index 00000000..dc9440c3
--- /dev/null
+++ b/template/news/2020-09-0.13.3.html.j2
@@ -0,0 +1,51 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.13.3 released</h1>
+<p>
+  Continuing to "release early / release often", we present
+  GNUnet 0.13.3. This is a bugfix release for gnunet 0.13.2.<br/>
+  It fixes some build issues and contains major changes to
+  the re:claimID API.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.3 (since 0.13.2)</h4>
+<ul>
+  <li><tt>REST</tt>:
+    <ul>
+      <li>re:claimID attestation API change reflected in endpoint naming.</li>
+      <li>Fix regression in <tt>NAMESTORE</tt> REST API endpoint processing.</li>
+    </ul>
+  </li>
+  <li><tt>RECLAIM</tt>:
+      "Attestations" renamed to "Credentials". Credentials are now converted to "Presentations" when a ticket is issued in preparation
+      for <a href="https://www.w3.org/TR/vc-data-model/">DID-style VCs</a> and Privacy-ABCs.
+  </li>
+  <li><tt>UTIL</tt>: Fix <tt>gnunet-qr</tt> device parameter.</li>
+  <li><tt>SET</tt>: Separated into set intersection (SETI) and set union subsystems (SETU).</a></li>
+  <li><tt>BUILD</tt>:
+    <ul>
+      <li>Fix build on OpenBSD.</li>
+      <li>Correctly check for required libsodium version. <a href="https://bugs.gnunet.org/view.php?id=6506">#6506</a></li>
+    </ul>
+  </li>
+</ul>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Jonathan Buchanan, Johannes Späth and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-11-0.14.0.html.j2 b/template/news/2020-11-0.14.0.html.j2
new file mode 100644
index 00000000..853b4548
--- /dev/null
+++ b/template/news/2020-11-0.14.0.html.j2
@@ -0,0 +1,81 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.14.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.14.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.13.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.13.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.13.x peers will be able to communicate with Git
+  master or 0.13.x peers, but some services - in particular GNS - will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.14.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.14.0 (since 0.13.3)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
+      <li>Crypto agility: The GNS protocol now supports other zone types besides ECDSA-based PKEYs.
+      However, the alternative EdDSA-based EDKEY crypto is not yet implemented. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
+      <li>PKEY zones: ECDSA zone record sets are now encrypted using AES-CTR. <a href="https://bugs.gnunet.org/view.php?id=6487">#6487</a></li>
+    </ul>
+  </li>
+  <li>
+    <tt>IDENTITY</tt>: Identities can now be created either as ECDSA (default) or EdDSA key pairs.</li>
+  </li>
+  <li>
+    <tt>POSTGRESQL</tt>: Allow NULL value returns and fix test cases. <a href="https://bugs.gnunet.org/view.php?id=6524">#6524</a>
+  </li>
+  <li><tt>UTIL</tt>:
+      String time conversion functions no longer localized to preserve reversibility. <a href="https://bugs.gnunet.org/view.php?id=6615">#6615</a>
+  </li>
+  <li><tt>Buildsystem</tt>: README updates to clarify runtime/compile/optional dependencies</li>
+  <li><b>(NEW)</b> <tt>MESSENGER</tt>: New messenger component (experimental)</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.0 bugtracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Daniel Golle, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-11-GNSSpec4.html.j2 b/template/news/2020-11-GNSSpec4.html.j2
new file mode 100644
index 00000000..13e0f28d
--- /dev/null
+++ b/template/news/2020-11-GNSSpec4.html.j2
@@ -0,0 +1,45 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 4/4 and Packaging 1+2</h1>
+<p>
+  We are happy to announce the completion of the fourth and last milestone for the GNS
+  Specification. The fourth milestone consists of involving a broader community
+  for feedback and improvements:
+<p>
+<ul>
+  <li><a href="https://news.ycombinator.com/item?id=23766947">Hacker News</a></li>
+  <li><a href="https://datatracker.ietf.org/meeting/108/session/secdispatch">IETF 108 secdispatch</a>
+  (see also associated discussions on the mailinglist)</li>
+  <li><a href="https://centr.org/news/news/alternative-dns.html">Reporting on IETF secdispatch</a></li>
+  <li><a href="https://mailarchive.ietf.org/arch/msg/din/jkbYgEsyuZCknyYQxN-LxDtWpsY/">IRTF DINRG</a></li>
+  <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-07/msg00043.html">Mailing list</a></li>
+</ul>
+<p>
+  Based on this and private feedback received, we updated the draft and
+  the implementation. Most notably, GNS now supports alternative cryptographic
+  schemes for zone keys ("crypto agility") which allows alternative zone types.
+  The (protocol breaking) changes will be released as part of GNUnet 0.14.0.
+  The specification document <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+  <li><a href="https://datatracker.ietf.org/doc/draft-schanzen-gns/">Link to IETF Datatracker (updated less frequently)</a></li>
+</ul>
+<p>
+  Further, work on packaging has been done on Alpine (Packaging 1) and Debian (Packaging 2) packages.
+  The packaging for Alpine is complete, the Debian package is in progress as
+  review and final integration is out of our hands. For reference see also:
+</p>
+<ul>
+  <li><a href="https://pkgs.alpinelinux.org/packages?name=gnunet&branch=edge">Alpine package</a></li>
+  <li><a href="https://salsa.debian.org/debian/gnunet/-/merge_requests/3">Debian package</a></li>
+</ul>
+<p>
+  We will continue to engage with IETF/IRTF as much as possible (online or in-person)
+  including future presentations and discussions at IETF/IRTF.
+  There is still a packaging task open for Fedora (3) which is still work in progress.
+  This work was (and other aspects still are) generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-03-0.14.1.html.j2 b/template/news/2021-03-0.14.1.html.j2
new file mode 100644
index 00000000..0249b984
--- /dev/null
+++ b/template/news/2021-03-0.14.1.html.j2
@@ -0,0 +1,48 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.14.1</h1>
+<p>
+Continuing to "release early / release often", we present
+GNUnet 0.14.1. This is a bugfix release for gnunet 0.14.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.14.1 (since 0.14.0)</h4>
+<ul>
+  <li><tt>TNG</tt>: Various improvements to communicators. <a href="https://bugs.gnunet.org/view.php?id=6361">#6361</a>,<a href="https://bugs.gnunet.org/view.php?id=5550">#5550</a>
+  </li>
+  <li><tt>GNS</tt>: Use autogenerated records header file from GANA.</li>
+  <li><tt>FS</tt>: Improve modularity of FS structs. <a href="https://bugs.gnunet.org/view.php?id=6743">#6743</a></li>
+  <li><tt>SETU</tt>: Various improvements as part of the ongoing work on <a href="https://lsd.gnunet.org/lsd0003">LSD0003</a>.</li>
+  <li><tt>IDENTITY</tt>: Fix wrong key construction for anonymous ECDSA identity.</li>
+  <li><tt>RPS</tt>: Code cleanup mostly addressing warnings.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Added a Base32 en/decoded CLI <tt>gnunet-base32</tt>.</li>
+      <li>Use timeflakes as UUIDs. <a href="https://bugs.gnunet.org/view.php?id=6716">#6716</a></li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: Fix libunistring detection. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.1 bugtracker</a>.
+</p>
+<h4>Thanks</h4>
+<p>
+This release was the work of many people. The following people contributed code and were thus easily identified:
+Christian Grothoff, Florian Dold, t3sserakt, TheJackiMonster, Elias Summermatter, Julius Bünger and Thien-Thi Nguyen.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-03-gsoc-update.html.j2 b/template/news/2021-03-gsoc-update.html.j2
new file mode 100644
index 00000000..d638549a
--- /dev/null
+++ b/template/news/2021-03-gsoc-update.html.j2
@@ -0,0 +1,13 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>No GSoC projects in 2021</h1>
+<p>
+  For 2021, <a href="https://lists.gnu.org/archive/html/summer-of-code/2021-03/msg00000.html">GNU has not been selected as a GSoC organization</a>.
+  This also means that <a href="{{ url_localized('gsoc.html')}}">GNUnet GSoC
+  projects</a> will not be offered through the GSoC programme.
+  Thanks to all of those interested in our proposed projects and their efforts
+  in preparing proposals, including preliminary discussions with us.
+  If you are still interested in tackling any of the proposed open issues, you
+  are very welcome to do so.
+<p>
+{% endblock body_content %}
diff --git a/template/news/2021-05-DISSENS.html.j2 b/template/news/2021-05-DISSENS.html.j2
new file mode 100644
index 00000000..d67f33a5
--- /dev/null
+++ b/template/news/2021-05-DISSENS.html.j2
@@ -0,0 +1,67 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>DISSENS: Decentralized Identities for Self-sovereign End-users (NGI TRUST)</h1>
+<p>
+  Since mid 2020, a consortium between <a class="link" href="https://taler.net">Taler Systems S.A.</a>,
+the <a class="link" href="https://bfh.ch">Bern University of Applied Sciences</a> and <a class="link" href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> has been working
+  on bringing privacy-friendly payments using GNU Taler and self-sovereign
+  identity using GNUnet's <a class="link" href="https://reclaim.gnunet.org">re:claimID</a>
+  together in an e-commerce framework.
+</p>
+<p>
+<img style="width: 100%; border: 1px solid #333" src="{{ url_static('dissens-overview.png')}}"/>
+</p>
+<h2>Content</h2>
+<p>
+  Registrations of accounts prior to receiving services online is the standard process for commercial offerings on the Internet which depend on two corner stones of the Web: Payment processing and digital identities. The use of third-party identity provider services (IdPs) is practical as it delegates the task of verifying and storing personal information. The use of payment processors is convenient for the customer as it provides one-click payments. However, the quasi-oligopoly of services providers in those areas include Google and Facebook for identities and PayPal or Stripe for payment processing. Those corporations are not only based in privacy-unfriendly jurisdictions, but also exploit private data for profit.
+</p>
+<p>
+DISSENS makes the case that what is urgently needed are fundamentally different, user-centric and privacy-friendly alternatives to the above.
+Self-sovereign identity (SSI) management is the way to replace IdPs with a user-centric, decentralized mechanism where data and access control is fully under the control of the data subject.
+In combination with a privacy-friendly payment system, DISSENS aims to achieve the same one-click user experience that is currently achieved by privacy-invasive account-based Web shops, but without the users having to setup accounts.
+</p>
+<p>
+To achieve this, DISSENS integrates re:claimID with the GNU Taler payment system in a pilot in order to demonstrate the practical feasibility and benefits of privacy enhancing technologies for users and commercial service providers.
+DISSENS also implements a reference scenario which includes credentials issued by the partners Fraunhofer AISEC and BFH for employees and students, respectively. Users are able to access and use a pilot service developed by Taler Systems S.A. while being able to claim specific discounts for students and researchers.
+</p>
+<p>
+This approach offers significant benefits over existing solutions built using other SSI systems such as <a class="link" href="https://www.sovrin.org">Sovrin</a> or <a class="link" href="https://www.serto.id">serto</a> (formerly uPort):
+</p>
+<b>No gatekeepers; No vendor lock-in:</b>
+<p>
+The approach is completely open to issuers and does not impose any registration restrictions (such as registration fees) in order to define domain specific credentials. Further, the system does not impose a consortium-based governance model — which tend to eventually be driven by commercial interests and not consumer interests. The design enables all participants in the ecosystem to participate without prior onboarding while at the same time being offered full transparency and control regarding their personal data and processes involved.
+</p>
+<b>Support for non-interactive business processes:</b>
+<p>
+At the same time, unlike the SSI systems cited above, re:claimID offers a way to access user information without online interaction with the user. Offline access of shared identity data is a crucial requirement in almost any business process as such processes often occur after direct interaction with the user. For example, customer information such as billing addresses are required in — possibly recurring — back office billing processes which occur well after interaction with a customer.
+</p>
+<b>Scalability and sustainability:</b>
+<p>
+Finally, both re:claimID as the SSI system as well as Taler do not suffer from the usual predicament Blockchain-based systems find themselves in: Both systems do not require a decentralized, public ledger. This eliminates the need for consensus mechanisms, which do not scale and are ecologically unsustainable. In fact, DISSENS employs decentralization only where it provides the most value and use more efficient technology stacks where needed: re:claimID builds on top of the <a class="link" href="{{ url_localized('gns.html') }}">GNU Name System</a>, which makes use of a DHT, an efficient (O(log n)) peer-to-peer data structure. For payments, GNU Taler uses centralized infrastructure operated by audited and regulated exchange providers and facilitates account-less end-to-end interactions between customers and services where all parties have O(1) transaction costs.
+</p>
+<p>
+The result of DISSENS will provide businesses and credential issuers with ready-to-use and standards-compliant templates to build privacy-friendly services in the Web.
+The aim of the DISSENS project was to design a technology stack which combines privacy-friendly online payments with self-sovereign personal data management. The result enables users to be in complete control over their digital identity and personal information while at the same time being able to selectively share information necessary to use commercial services. The pilot demonstrates a sustainable, user-centric, standard-compliant and accessible use case for public service employees and students in the domain of commercial food delivery.
+It serves as an easy-to-adapt template for the integration of other scenarios and use cases.
+</p>
+<h2>Future work</h2>
+<p>
+GNUnet is working on the underlying components mature to the point that Taler+re:claimID can be recommended to operators to enable for account-less shopping with or without verified credentials. This will also require the continuation of our
+work on the low-level transport rewrite as it is a core component of GNS which
+in turn is what makes re:claimID spin.
+</p>
+<h2>Links</h2>
+<ul>
+  <li>Mid-project <a class="link" href="https://gnunet.org/~schanzen/2021-01-18-reclaimID-Taler-Shopping.webm">demonstration video</a> (~7 MB).</li>
+  <li><a class="link" href="https://git.gnunet.org/bibliography.git/plain/docs/dissens2021.pdf">The paper</a> (also accepted for publication without appendix at the <a class="link" href="https://oid2021.compute.dtu.dk/">Open Identity Summit 2021</a>)</li>
+  <li><a class="link" href="https://wordpress.org/plugins/gnu-taler-payment-for-woocommerce/">Taler WooCommerce plugin</a> (wordpress.org)</li>
+  <li>The privacy credential library <a class="link" href="https://github.com/Fraunhofer-AISEC/libpabc">libpabc</a> (github.com).</li>
+  <li><a class="link" href="https://git.taler.net/woocommerce-taler.git">Setup scripts and installation documentation for a Taler + re:claimID + WooCommerce service</a> (taler.net).</li>
+  <li><a class="link" href="https://git.gnunet.org/gnunet-presentations.git/plain/2021dissens/reclaim.pdf">Slide deck</a>.</li>
+</ul>
+<p>
+</p>
+<p>
+  This work is generously funded by <a class="link" href="https://www.ngi.eu">the EC's Next Generation Internet (NGI) initiative</a> as part of their <a class="link" href="https://www.ngi.eu/ngi-projects/ngi-trust/">NGI TRUST</a> programme.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-08-0.15.0.html.j2 b/template/news/2021-08-0.15.0.html.j2
new file mode 100644
index 00000000..89ff00ac
--- /dev/null
+++ b/template/news/2021-08-0.15.0.html.j2
@@ -0,0 +1,82 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.15.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.15.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.14.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.14.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.14.x peers will be able to communicate with Git
+  master or 0.14.x peers, but some services - in particular GNS - will not be compatible.<br/>
+  The MESSENGER service goes out of experimental to be used by
+  libraries and applications as dependency. It handles decentralized
+  messaging in flexible groups by using the CADET service and messages
+  can be signed with your ego from the IDENTITY service. The service
+  is still in an early stage, so its protocol (currently version 0.1)
+  will likely adapt or change in future releases to some degree.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.15.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.15.0.tar.gz">gnunet-0.15.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.15.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.15.0.tar.gz">gnunet-gtk-0.15.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.15.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.15.0.tar.gz">gnunet-fuse-0.15.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.15.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.15.0 (since 0.14.1)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+      <ul>
+        <li>First-come-first-served GNUnet top-level domain ".pin" zone key and website updated a. <a href="https://fcfs.gnunet.org/">Register here.</a> <a href="https://bugs.gnunet.org/view.php?id=6832">#6832</a></li>
+        <li>New <a href="https://lsd.gnunet.org/lsd0001/#name-edkey">EDKEY zone keys</a>.</li>
+      </ul>
+  </li>
+  <li><tt>SCALARPRODUCT</tt>: Crypto ported to libsodium improving performance. <a href="https://bugs.gnunet.org/view.php?id=6818">#6818</a></li>
+  <li><tt>RECLAIM</tt>: Added support for <a class="link" href="https://github.com/Fraunhofer-AISEC/libpabc">BBS+ blind signature credentials</a> for selective disclosure.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Swap gnunet-config's default behaviour for the rewrite flag.</li>
+      <li>Config file is not not always written</li>
+      <li>Introduced new TIME helper functions</li>
+    </ul>
+  </li>
+  <li><tt>SETU</tt>: Implemented set union subsystem along with technical specification <a href="https://lsd.gnunet.org/lsd0003/">LSD0003</a>.</li>
+  <li><tt>MESSENGER</tt>: New messenger component moved out of experimental.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Daniel Golle, Alessio Vanni, Thien-Thi Nguyen, Elias Summermatter, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-12-GNSSpecISE.html.j2 b/template/news/2021-12-GNSSpecISE.html.j2
new file mode 100644
index 00000000..0b89efd0
--- /dev/null
+++ b/template/news/2021-12-GNSSpecISE.html.j2
@@ -0,0 +1,28 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Call for Reviews</h1>
+<p>
+  We are happy to announce that our GNS specification is currently under review
+  by the Independent Stream Editor (ISE).
+  We have already received feedback from the ISE and made significant,
+  mostly editorial changes to the specification.
+</p>
+<p>
+  We are inviting anyone reading this to review and provide feedback to the draft
+  and send it to <a href="mailto:gnunet-developers@gnu.org?subject=LSD0001">gnunet-developers@gnu.org</a>.
+  Even better, you could write an implementation in your favourite programming
+  language.
+</p>
+<p>
+  In other news, we are currently also working on the specification of the
+  <a href="https://lsd.gnunet.org/lsd0004">GNUnet DHT</a>.
+</p>
+<ul>
+  <li>IETF: <a href="https://datatracker.ietf.org/doc/draft-schanzen-gns/">Datatracker</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  This work was generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-02-0.16.0.html.j2 b/template/news/2022-02-0.16.0.html.j2
new file mode 100644
index 00000000..631b622e
--- /dev/null
+++ b/template/news/2022-02-0.16.0.html.j2
@@ -0,0 +1,89 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>GNUnet 0.16.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.16.0.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This is a new major release. It breaks protocol compatibility with the 0.15.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.15.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.15.x peers will be able to communicate with Git
+  master or 0.16.x peers, but some services - in particular GNS - will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.16.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.0.tar.gz">gnunet-0.16.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.15.0.tar.gz">gnunet-gtk-0.16.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.16.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.15.0.tar.gz">gnunet-fuse-0.16.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.16.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.16.0 (since 0.15.3)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+      <ul>
+        <li>New record flag: CRITICAL. For records that must be processed otherwise resolution must fail. <a href="https://bugs.gnunet.org/view.php?id=7169">#7169</a></li>
+        <li>Deletion of records and reduction of expiration times is now properly handled with respect to monotonically increasing expiratin times. <a href="https://bugs.gnunet.org/view.php?id=7170">#7170</a></li>
+        <li>VPN tunnel establishment is moved out of the GNS resolver to be handled by applications (such as the DNS2GNS service). <a href="https://bugs.gnunet.org/view.php?id=7171">#7171</a></li>
+        <li>Introduces new record type REDIRECT which replaces the previous (ab)use of CNAME records. <a href="https://bugs.gnunet.org/view.php?id=7172">#7172</a></li>
+        <li>The specification has been updated to reflect the changes. <a href="https://lsd.gnunet.org/lsd0001">LSD0001</a></li>
+      </ul>
+  </li>
+  <li><tt>DHT</tt>:
+    <ul>
+      <li>Routes can now be signed. <a href="https://bugs.gnunet.org/view.php?id=4164">#4164</a></li>
+      <li>Changed distance metric to a more traditional XOR. <a href="https://bugs.gnunet.org/view.php?id=7136">#7136</a></li>
+        <li>The specification has been updated to reflect the changes. <a href="https://lsd.gnunet.org/lsd0004">LSD0004</a></li>
+    </ul>
+  </li>
+  <li><tt>RECLAIM</tt>: Added some preliminary support for Decentralized Identifier (DID) and Verifiable Credentials (VCs).</li>
+  <li><tt>UTIL</tt>: Add Clause-Schnorr blind signatures. For use in <a href="https://taler.net/en/news/2022-02.html">Taler</a>.</li>
+  <li><tt>BUILD</tt>: Building from git now requires <tt>recutils</tt>. The bootstrap will generate up-to-date header files from <a href="https://gana.gnunet.org">GANA</a>.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Tristan Schwieren, Alessio Vanni, Florian Dold, Thien-Thi Nguyen, t3sserakt, Lucien Heuzeveldt, Gian Demarmels, madmurphy, TheJackiMonster and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-03-0.16.1.html.j2 b/template/news/2022-03-0.16.1.html.j2
new file mode 100644
index 00000000..d39cf8ca
--- /dev/null
+++ b/template/news/2022-03-0.16.1.html.j2
@@ -0,0 +1,36 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.16.1</h1>
+<p>
+This is a bugfix release for gnunet 0.16.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.16.1 (since 0.16.0)</h4>
+<ul>
+  <li><tt>GNS</tt>: There was a bug where private records were published.</li>
+  <li><tt>NAMESTORE</tt>: CLI now handles Tombstones better. There is also a warning for problematically short relative expiration times (&lt;15 minutes) when adding new records.</li>
+  <li><tt>Buildsystem</tt>:
+    <ul>
+      <li>Fix libsodium detection. <a href="https://bugs.gnunet.org/view.php?id=7153">#7153</a></li>
+      <li>Fix for facilitating <tt>autoreconf</tt> with the released tarball.</li>
+    </ul>
+  </li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.16.1 bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-03-0.16.2.html.j2 b/template/news/2022-03-0.16.2.html.j2
new file mode 100644
index 00000000..5ea4d941
--- /dev/null
+++ b/template/news/2022-03-0.16.2.html.j2
@@ -0,0 +1,32 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.16.2</h1>
+<p>
+This is a bugfix release for gnunet 0.16.1.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.2.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.16.2 (since 0.16.1)</h4>
+<ul>
+  <li><tt>DHT</tt>: Fix path signature handling.</li>
+  <li><tt>GNS</tt>: Fix BOX handling in zone apex.</li>
+  <li><tt>NAMESTORE</tt>: Prevent storing under invalid labels.</li>
+  <li><tt>Buildsystem</tt>: Fix build on *BSD and Guix.</li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.16.2 bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-03-0.16.3.html.j2 b/template/news/2022-03-0.16.3.html.j2
new file mode 100644
index 00000000..2d8f376f
--- /dev/null
+++ b/template/news/2022-03-0.16.3.html.j2
@@ -0,0 +1,30 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.16.3</h1>
+<p>
+This is a bugfix release for gnunet 0.16.2.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.16.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.16.3.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.16.3 (since 0.16.2)</h4>
+<ul>
+  <li><tt>GNS</tt>: Fix record processing in DHT.</li>
+  <li><tt>Buildsystem</tt>: Fix portability issues.</li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.16.2 bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-04-libgnunetchat-0.1.0.html.j2 b/template/news/2022-04-libgnunetchat-0.1.0.html.j2
new file mode 100644
index 00000000..9568827a
--- /dev/null
+++ b/template/news/2022-04-libgnunetchat-0.1.0.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>libgnunetchat 0.1.0 released</h1>
+<p>
+  We are pleased to announce the release of the client side library libgnunetchat 0.1.0.
+  <br/>
+  This library brings an abstraction layer using the client API from different GNUnet services to provide the functionality of a typical messenger application. The goal is to make developing such applications easier and independent of the GUI toolkit. So people can develop different interfaces being compatible with eachother despite visual differences, a few missing features or differences in overall design.
+  <br/>
+  The library relies on multiple services from GNUnet to implement its features. More information about that can be found <a href="https://git.gnunet.org/libgnunetchat.git/tree/README.md">here</a>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.0.tar.gz">libgnunetchat-0.1.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.1.0</h4>
+<ul>
+  <li>This release requires the GNUnet Messenger Service 0.1!</li>
+  <li>It allows account management (creation, listing and deletion).</li>
+  <li>Clients are able to switch between accounts during runtime.</li>
+  <li>The client can rename an account or update its key.</li>
+  <li>Contact exchange is possible via lobbies in form of URIs to be shared as text form or potentially QR encoded.</li>
+  <li>Each resource allows handling a user pointer for the client application.</li>
+  <li>Contacts and groups can be managed individually and given a custom nick name.</li>
+  <li>It is possible to request and open a direct chat with any contact.</li>
+  <li>Groups allow listing their members with custom user pointers related to the group memberships.</li>
+  <li>Chats can be left explicitly.</li>
+  <li>Each chat will be represented as context resource abstracting the variant of chat.</li>
+  <li>It is possible to send text messages, send files, share files and send read receipts explicitly.</li>
+  <li>Received messages allow checking for a read receipt status.</li>
+  <li>Messages can be deleted with a custom delay.</li>
+  <li>Files in a chat can be fully managed (they can be uploaded, downloaded, unindexed and provide a decrypted temporary preview if necessary) while being encrypted individually.</li>
+  <li>The status of each operation (upload, download, unindex) regarding files can be tracked.</li>
+  <li>Received invitations to new chats can be accepted.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/libgnunetchat.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>The test cases are not fully complete and they may fail because of timeouts erratically.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-05-messenger-gtk-0.7.0.html.j2 b/template/news/2022-05-messenger-gtk-0.7.0.html.j2
new file mode 100644
index 00000000..6c7c1982
--- /dev/null
+++ b/template/news/2022-05-messenger-gtk-0.7.0.html.j2
@@ -0,0 +1,68 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>Messenger-GTK 0.7.0 released</h1>
+<p>
+  We are pleased to announce the release of the Messenger-GTK application.
+  <br/>
+  The application is a convergent GTK messaging application using the GNUnet Messenger service. The goal is to provide private and secure communication between any group of devices. The interface is also designed in a way to scale down to mobile and small screen devices like phones or tablets.
+</p>
+<p>
+  The application provides the following features:
+</p>
+<ul>
+  <li>Creating direct chats and group chats</li>
+  <li>Managing your contacts and groups</li>
+  <li>Invite contacts to a group</li>
+  <li>Sending text messages</li>
+  <li>Sending voice recordings</li>
+  <li>Sharing files privately</li>
+  <li>Deleting messages with any custom delay</li>
+  <li>Renaming contacts</li>
+  <li>Exchanging contact details physically</li>
+  <li>Verifying contact identities</li>
+  <li>Switching between different accounts</li>
+</ul>
+<p>
+  The application utilizes the previously released library "libgnunetchat" in a convergent graphical user interface. More information about that can be found <a href="https://git.gnunet.org/messenger-gtk.git/tree/README.md">here</a>.
+</p>
+<p>
+  It is also possible to install and try the application as flatpak. The application is already available on <a href="https://flathub.org/apps/details/org.gnunet.Messenger">flathub.org</a>. Otherwise you will find the source code ready to compile below as well.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.7.0.tar.gz">messenger-gtk-0.7.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.7.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.7.0</h4>
+<ul>
+  <li>The version iteration will be inherited by cadet-gtk as logical successor.</li>
+  <li>It is possible to create direct chats and group chats via physical or virtual exchange.</li>
+  <li>Groups and contacts can be named, left, verified or deleted.</li>
+  <li>Existing contacts can be invited to any private or public group.</li>
+  <li>Chats allow sending text messages, voice recordings or files.</li>
+  <li>Messages can be deleted with a custom delete or automatically.</li>
+  <li>Switching between different accounts can be done during runtime.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/messenger-gtk.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>It is still difficult to get reliable chats between different devices. This might change with the upcoming changes on the GNUnet transport layer though.</li>
+  <li>It might happen that the FS service is not connected which might stop any file upload or stall it forever.</li>
+  <li>The webcam/camera to scan QR codes might not get picked up properly (for example it doesn't work yet with the Pinephone).</li>
+  <li>The application might crash at times. So consider it still being in development.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-06-0.17.0.html.j2 b/template/news/2022-06-0.17.0.html.j2
new file mode 100644
index 00000000..fea9e8f8
--- /dev/null
+++ b/template/news/2022-06-0.17.0.html.j2
@@ -0,0 +1,87 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>GNUnet 0.17.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.17.0.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This is a new major release. It breaks protocol compatibility with the 0.16.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.16.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.16.x peers will be able to communicate with Git
+  master or 0.17.x peers, but some services - in particular the DHT - will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.17.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.0.tar.gz">gnunet-0.17.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.17.0 (since 0.16.3)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+      <ul>
+        <li>FCFSD: Allow configuration of relative expiration time of added records.</li>
+        <li>Aligned with breaking changes in specification. <a href="https://lsd.gnunet.org/lsd0001">LSD0001</a></li>
+      </ul>
+  </li>
+  <li><tt>DHT</tt>:
+    <ul>
+      <li>Aligned and reordered message formats. <a href="https://lsd.gnunet.org/lsd0004">LSD0004</a></li>
+      <li>Moved block type definitions to <a href="https://gana.gnunet.org">GANA</a></li>
+      <li>The specification has been updated to reflect the changes. <a href="https://lsd.gnunet.org/lsd0004">LSD0004</a></li>
+    </ul>
+  </li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Fix scheduler bug with same-priority immediately-ready tasks possibly hogging the scheduler.</li>
+      <li>Fix mysql/mariadb detection.</li>
+    </ul>
+  </li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Tristan Schwieren, Florian Dold, Thien-Thi Nguyen, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-06-0.17.1.html.j2 b/template/news/2022-06-0.17.1.html.j2
new file mode 100644
index 00000000..fdf41608
--- /dev/null
+++ b/template/news/2022-06-0.17.1.html.j2
@@ -0,0 +1,30 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.1</h1>
+<p>
+This is a bugfix release for gnunet 0.17.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.17.0 (since 0.17.1)</h4>
+<ul>
+  <li><tt>DHT</tt>: Bugfix in HELLO message format. LSD0004 compliance.</li>
+  <li><tt>RECLAIM</tt>: OpenID Connect plugin now needs (optional) jose dependency.</li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-06-DHTSpec1.html.j2 b/template/news/2022-06-DHTSpec1.html.j2
new file mode 100644
index 00000000..9bebdf15
--- /dev/null
+++ b/template/news/2022-06-DHTSpec1.html.j2
@@ -0,0 +1,39 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>DHT Technical Specification Milestones 1-3/5</h1>
+<p>
+We are happy to announce the completion of the following milestones for the DHT  specification. The objective is to provide a detailed and comprehensive guide for implementors of the GNUnet DHT "R<sup>5</sup>N".
+ The milestones consist of documenting the base data structures and processes
+ of the protocol.
+ This includes the specification of the DHT message wire and serialization formats.<br>
+</p>
+<p>
+  Completed milestones overview:
+  <ol>
+    <li>Defined base data structures and processes that form the foundation of the protocol: Routing table, distance metrics, infrastructure messages, bootstrapping and base functions for block processing.</li>
+    <li>Defined the core data structures and processes that are specific to the R<sup>5</sup>N protocol: Block and peer filtering, routing table management and lookup algorithms.</li>
+    <li>The protocol was extended to support path signatures. This enables optional integrity protection of paths result messages have taken in a potentially rouge environment.</li>
+  </ol>
+</p>
+<p>
+  The current protocol is implemented as part of GNUnet 0.17.x and gnunet-go as
+  <a href="https://lists.gnu.org/archive/html/gnunet-developers/2022-06/msg00019.html">previously announced on the mailing list</a>.
+</p>
+<p>
+  <b>We invite any interested party to read the document and provide critical
+    review and feedback. This greatly helps us to improve the protocol
+    and help future implementations. Contact us at <a href="mailto:gnunet-developers@gnunet.org">the gnunet-developers mailing list</a></b>.
+  As part of the remaining milestones, the specification will be updated and
+  interoperability testing will be conducted.
+  Further, we aim to present the draft specification at IETF.
+</p>
+<ul>
+  <li><a href="https://lsd.gnunet.org/lsd0004/draft-schanzen-r5n.txt">Plain text version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0004/draft-schanzen-r5n.html">HTML version</a></li>
+  <li><a href="https://git.gnunet.org/lsd0004.git">Git sources</a></li>
+</ul>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/assure">NGI Assure fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-07-0.17.2.html.j2 b/template/news/2022-07-0.17.2.html.j2
new file mode 100644
index 00000000..a1236da4
--- /dev/null
+++ b/template/news/2022-07-0.17.2.html.j2
@@ -0,0 +1,31 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.2</h1>
+<p>
+This is a bugfix release for gnunet 0.17.1.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.2.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.17.1 (since 0.17.2)</h4>
+<ul>
+  <li><tt>DHT</tt>: Various bugfixes in the protocol.</li>
+  <li><tt>RECLAIM</tt>: OpenID Connect plugin improvements.</li>
+  <li><tt>ABE</tt>: Removed.</li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-08-0.17.3.html.j2 b/template/news/2022-08-0.17.3.html.j2
new file mode 100644
index 00000000..288c645e
--- /dev/null
+++ b/template/news/2022-08-0.17.3.html.j2
@@ -0,0 +1,49 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.3</h1>
+<p>
+This is a bugfix release for gnunet 0.17.2.
+In addition to the fixed in the source, the documentation websites including
+the handbook have been updated and consolidated: <a href="https://docs.gnunet.org">https://docs.gnunet.org</a>.
+</p>
+<p>
+Notably, the GNUnet project now publishes a GNS zone for its websites which can be used
+to test resolution on any installation.
+For example:
+</p>
+<p>
+  <code class="block">
+    $ gnunet-gns -t ANY -u www.gnunet.org
+  </code>
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.3.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.17.3 (since 0.17.2)</h4>
+<ul>
+  <li><tt>DHT</tt>: Various bugfixes in the protocol.</li>
+  <li><tt>TRANSPORT</tt>: Fix HTTPS tests. <a href="https://bugs.gnunet.org/view.php?id=7257">#7257</a></li>
+  <li><tt>DOCUMENTATION</tt>:
+    <ul>
+      <li>Migrate from texinfo to sphinx.</li>
+      <li>Dropped dependency on texinfo.</li>
+      <li>Added dependency on sphinx.</li>
+    </ul>
+  </li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bugtracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-08-0.17.4.html.j2 b/template/news/2022-08-0.17.4.html.j2
new file mode 100644
index 00000000..e3abfb59
--- /dev/null
+++ b/template/news/2022-08-0.17.4.html.j2
@@ -0,0 +1,22 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.4</h1>
+<p>
+This is a bugfix release for gnunet 0.17.3 because of a missing file in the
+tarball required to build the documentation.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.4.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.4.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.4.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.4.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-09-0.17.5.html.j2 b/template/news/2022-09-0.17.5.html.j2
new file mode 100644
index 00000000..171ce3a1
--- /dev/null
+++ b/template/news/2022-09-0.17.5.html.j2
@@ -0,0 +1,21 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.5</h1>
+<p>
+This is a bugfix release for gnunet 0.17.4..
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.5.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.5.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-09-0.17.6.html.j2 b/template/news/2022-09-0.17.6.html.j2
new file mode 100644
index 00000000..8d28059b
--- /dev/null
+++ b/template/news/2022-09-0.17.6.html.j2
@@ -0,0 +1,35 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.17.6</h1>
+<p>
+This is a bugfix release for gnunet 0.17.5.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.6.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.17.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.17.6.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.17.6 (since 0.17.5)</h4>
+<ul>
+  <li><tt>NAMESTORE</tt>:
+      <ul>
+        <li>Added transactional API. <a href="https://bugs.gnunet.org/view.php?id=7203">#7203</a></li>
+        <li>Removed heap storage storage plugin.</li>
+      </ul>
+  </li>
+  <li><tt>FS</tt>: Fix `-s` and `-o` options not working together in <tt>gnunet-search</tt></li>
+<li><tt>REST</tt>: Added (optional) authentication for all rest endpoints. <a href="https://bugs.gnunet.org/view.php?id=5669">#5669</a> </li>
+  <li><tt>DOC</tt>: Doxygen is now built only if available. Sphinx is built on bootstrap. <a href="https://bugs.gnunet.org/view.php?id=7324">#7324</a> </li>
+  <li><tt>UTIL</tt>: Remove outdated test. <a href="https://bugs.gnunet.org/view.php?id=7361">#7361</a></li>
+  <li><tt>BUILD</tt>: Remove gnurl as dependency and improve cURL detection. <a href="https://bugs.gnunet.org/view.php?id=5084">#5084</a></li>
+</ul>
+{% endblock body_content %}
diff --git a/template/news/2022-09-messenger-cli-0.1.0.html.j2 b/template/news/2022-09-messenger-cli-0.1.0.html.j2
new file mode 100644
index 00000000..f9829d6f
--- /dev/null
+++ b/template/news/2022-09-messenger-cli-0.1.0.html.j2
@@ -0,0 +1,56 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>messenger-cli 0.1.0 released</h1>
+<p>
+  We are pleased to announce the release of the messenger-cli application.
+  <br/>
+  The application is a counterpart for the terminal to the previous release of the GTK application using the GNUnet Messenger service. The goal is to provide private and secure communication between any group of devices. So server admins or users relying on a terminal focused window manager have now a proper option to utilize the service as well.
+</p>
+<p>
+  The application provides the following features:
+</p>
+<ul>
+  <li>Creating direct chats and group chats</li>
+  <li>Sending text messages</li>
+  <li>Sharing files privately</li>
+  <li>Deleting messages</li>
+  <li>Verifying contact identities</li>
+  <li>Switching between different accounts</li>
+</ul>
+<p>
+  The application utilizes the previously released library "libgnunetchat" in an user interface built with ncurses. It will adapt its different views depending on the terminal size to show most important information. The navigation is done via arrow-, ESCAPE, TAB, ENTER and DELETE keys. More information about that can be found <a href="https://git.gnunet.org/messenger-cli.git/tree/README.md">here</a>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.1.0.tar.gz">messenger-cli-0.1.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.1.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.1.0</h4>
+<ul>
+  <li>It is possible to create direct chats and group chats via lobbies, shared keys or invitations</li>
+  <li>Members of a chats can be observed</li>
+  <li>Chats allow sending text messages or files</li>
+  <li>Messages can be deleted in any chat locally</li>
+  <li>Switching between different accounts can be done during runtime</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/messenger-cli.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>It is still difficult to get reliable chats between different devices. This might change with the upcoming changes on the GNUnet transport layer though.</li>
+  <li>It might happen that the FS service is not connected which might stop any file upload or stall it forever.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-10-0.18.0.html.j2 b/template/news/2022-10-0.18.0.html.j2
new file mode 100644
index 00000000..1f281b0e
--- /dev/null
+++ b/template/news/2022-10-0.18.0.html.j2
@@ -0,0 +1,98 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>GNUnet 0.18.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.18.0.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This is a new major release. It breaks protocol compatibility with the 0.17.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.17.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.17.x peers will be able to communicate with Git
+  master or 0.18.x peers, but some services - in particular the DHT - will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.18.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.18.0.tar.gz">gnunet-0.18.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.18.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.18.0.tar.gz">gnunet-gtk-0.18.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.18.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.18.0 (since 0.17.6)</h4>
+<ul>
+  <li><tt>UTIL</tt>: Added <tt>enum GNUNET_ErrorCode</tt> for better error handling throughout the API.</li>
+  <li><tt>NAMESTORE</tt>:
+      <ul>
+        <li>Moved namecache updates out of namestore and into zonemaster. This fixes issues from version 0.17.6 with respect to premature namestore monitor update messages and zone propagation. [<a href="https://bugs.gnunet.org/view.php?id=7378">#7378</a>]</li>
+        <li>Added a new API for bulk imports: <tt>GNUNET_NAMESTORE_records_store2</tt>. The API can be combined with the transactional API in order to significantly improve namestore performance for lage zones. For postgres databases, storing records is around 20x faster than the old API. [<a href="https://bugs.gnunet.org/view.php?id=7379">#7379</a>]</li>
+        <li>New database setup utility <tt>gnunet-namestore-dbtool</tt>. Databases can be initialized and reset using this new CLI. Currently, database plugins still allow to initialize databases automatically as well by setting <tt>INIT_ON_CONNECT</tt> (Default: YES).  [<a href="https://bugs.gnunet.org/view.php?id=7204">#7204</a>]</li>
+        <li>There are new APIs for zone iterations and monitoring which support filtering of records using <tt>GNUNET_GNSRECORD_Filter</tt>. By default, maintenance records such as <tt>TOMBSTONE</tt>s are filtered. [<a href="https://bugs.gnunet.org/view.php?id=7193">#7193</a>]</li>
+        <li>New zonefile import utility <tt>gnunet-namestore-zonefile</tt> that for DNS zone files. [<a href="https://bugs.gnunet.org/view.php?id=7396">#7396</a>]</li>
+        <li>Make use of new <tt>enum GNUNET_ErrorCode</tt> in C and REST API. [<a href="https://bugs.gnunet.org/view.php?id=7399">#7399</a>]</li>
+        <li>Included handling of orphaned GNS records. Records are orphaned of Egos are (accidentally) deleted which makes operations on records difficult but at the same time existing records are still published. [<a href="https://bugs.gnunet.org/view.php?id=7401">#7401</a>, <a href="https://bugs.gnunet.org/view.php?id=7402">#7402</a>]</li>
+        <li>Updated the <a href="https://docs.gnunet.org/developers/subsystems/namestore/namestore.html">C API documentation</a> to reflect the above changes.</li>
+        <li>Updated the <a href="https://docs.gnunet.org/users/gns.html">user documentation</a> to reflect the above changes and included various tutorials on zone management.</li>
+        <li>Updated the <a href="https://docs.gnunet.org/developers/rest/namestore.html">REST API and its documentation</a> to reflect the above changes.</li>
+      </ul>
+  </li>
+  <li><tt>ZONEMASTER</tt>: Zonemaster now uses worker threads for record signing.</li>
+  <li><tt>DHT</tt>:
+    <ul>
+      <li>The specification has been updated to reflect the changes. <a href="https://lsd.gnunet.org/lsd0004">LSD0004</a></li>
+    </ul>
+  </li>
+  <li><tt>BUILD</tt>:
+    <ul>
+      <li>Fix mysql/mariadb detection (again). [<a href="https://bugs.gnunet.org/view.php?id=7356">#7356</a>]</li>
+    </ul>
+  </li>
+  <li><tt>PACKAGING</tt>: Revamped the <a href="https://git.gnunet.org/gnunet-rpm.git/">RPM package</a> available through <a href="https://copr.fedorainfracloud.org/coprs/schanzen/gnunet/">Fedora COPR</a> and <a href="https://bugzilla.redhat.com/show_bug.cgi?id=2094246">submitted it</a>.
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Bernd Fix, Christian Grothoff, Tristan Schwieren, madmurphy, Willow Liquorice, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+  We are greatful for funding from <a href="https://nlnet.nl/discovery/">NGI Zero DISCOVERY</a> that
+  has supported several developers over the last four years to work on the
+  <a href="../gns.html">GNU Name System</a> and related subsystems.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-10-libgnunetchat-0.1.1.html.j2 b/template/news/2022-10-libgnunetchat-0.1.1.html.j2
new file mode 100644
index 00000000..2fc901da
--- /dev/null
+++ b/template/news/2022-10-libgnunetchat-0.1.1.html.j2
@@ -0,0 +1,21 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>libgnunetchat 0.1.1 released</h1>
+<p>
+This is mostly a bugfix release for libgnunetchat 0.1.0. But it will also update the build process of libgnunetchat to use GNU Automake and it will ensure compatibility with latest changes in GNUnet 0.18.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.1.tar.gz">libgnunetchat-0.1.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.1.tar.gz.sig">libgnunetchat-0.1.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-11-0.18.1.html.j2 b/template/news/2022-11-0.18.1.html.j2
new file mode 100644
index 00000000..482a9ea4
--- /dev/null
+++ b/template/news/2022-11-0.18.1.html.j2
@@ -0,0 +1,32 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.18.1</h1>
+<p>
+This is a bugfix release for gnunet 0.18.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.18.1.tar.gz">gnunet-0.18.1.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.18.1.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.18.1.tar.gz">gnunet-gtk-0.18.1.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.18.1.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.18.1 (since 0.18.0)</h4>
+<ul>
+  <li><tt>IDENTITY</tt>:
+    <ul>
+      <li>Major internal API cleanup with respect to key serialization.</li>
+      <li>Removed deprecated default subsystem API.</li>
+    </ul>
+  </li>
+  <li><tt>TESTING</tt>: Fix broken tests.</li>
+  <li><tt>GTK</tt>: Update with recent changes to IDENTITY.</li>
+</ul>
+{% endblock body_content %}
diff --git a/template/news/2022-11-NGI-Entrust-GNS-TLDs.html.j2 b/template/news/2022-11-NGI-Entrust-GNS-TLDs.html.j2
new file mode 100644
index 00000000..39759705
--- /dev/null
+++ b/template/news/2022-11-NGI-Entrust-GNS-TLDs.html.j2
@@ -0,0 +1,42 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>NGI Zero Entrust: "GNS to DNS Migration and Zone Management"</h1>
+<p>
+  We are happy to announce that we have successfully acquired funding for further
+  GNS development and polishing!
+</p>
+<p>
+The GNU Name System specification is in its <a href="https://datatracker.ietf.org/doc/draft-schanzen-gns/">final stages</a>.
+Migration paths and large-scale testing as well as generating interest in running GNS zones and registrars is the next logical step.
+Hence, this project aims to
+<ol>
+  <li>Facilitate the management of GNS zones by administrators.</li>
+  <li>Provide users with means to resolve real-world names by (partially) mirroring the DNS root zone.</li>
+</ol>
+</p>
+<p>
+<b>Ad 1.:</b> To ease adoption, a framework for GNS registrars will be developed for zone management.
+The registrar framework will allow GNS zone administrators to provide
+a web-interface for subdomain registration by other users.
+The services may also be provided for a fee similar to how DNS domain registrars
+operate to cover running costs.
+The framework is envisioned to support integration of privacy-friendly payments with <a href="https://www.taler.net">GNU Taler</a>.
+</p>
+<p>
+<b>Ad 2.:</b>We are already hosting and shipping a zone for <tt>gnunet.org</tt> as part of our GNS implementation.
+To demonstrate how existing DNS registrars could migrate zones from DNS to GNS
+we plan to run multiple GNS zones ourselves which contain the zone information from real-world DNS top-level domains.
+This will also show how GNS can be used to secure the existing DNS namespace from
+censorship and outages when used in parallel.
+A selection of existing top-level domains for which <a href="https://jpmens.net/2021/05/18/dns-open-zone-data/">open data exists</a> will be hosted and served through GNS in order to facilitate the daily use of the name system.
+We are are planning to integrate at least three DNS zones and publish them
+through GNS for users to resolve in a default GNUnet installation.
+</p>
+<p>
+  Watch this space and the mailing list for updates!
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/entrust/">NGI Zero Entrust Programme</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-12-0.19.0.html.j2 b/template/news/2022-12-0.19.0.html.j2
new file mode 100644
index 00000000..b84370c0
--- /dev/null
+++ b/template/news/2022-12-0.19.0.html.j2
@@ -0,0 +1,90 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>GNUnet 0.19.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.19.0.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This is a new major release.
+  It breaks protocol compatibility with the 0.18.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.18.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.18.x peers will be able to communicate with Git
+  master or 0.19.x peers, but some services will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.19.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.0.tar.gz">gnunet-0.19.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.19.0.tar.gz">gnunet-gtk-0.19.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.19.0.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.19.0.tar.gz">gnunet-fuse-0.19.0.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.19.0.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.19.0 (since 0.18.2)</h4>
+<ul>
+  <li><tt>UTIL</tt>: Moved <tt>GNUNET_BIO_MetaData</tt> handling into <tt>FS</tt>.</li>
+  <li><tt>BUILD</tt>: <tt>platform.h</tt> removed as it should not be used by
+     third parties anyway.
+     <tt>gnunet_config.h</tt> is renamed to <tt>gnunet_private_config.h</tt>
+     and the new replacement <tt>gnunet_config.h</tt> is added to provide
+     build information for components linking against/using GNUnet.</li>
+  <li><tt>UTIL</tt>: Components part of <tt>gnunet_util_lib.h</tt> must now
+  be included through <tt>gnunet_util_lib.h</tt> and through that header
+  <b>only</b>.</li>
+  <li><tt>NAMESTORE</tt>:
+      <tt>gnunet-namestore</tt> can now parse a list of records into zones
+        from <tt>stdin</tt> in new <tt>recordline</tt> format.
+  </li>
+  <li><tt>GTK</tt>: Added an identity selector to the search to accomodate for
+    previously deprecated "default" identities for subsystems.</li>
+  <li>Other: Postgres plugins implementations modernized and previous regressions
+    fixed.</li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+This release was the work of many people. The following people contributed code and were thus easily identified:
+Christian Grothoff, Tristan Schwieren, madmurphy, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+<!--We are greatful for funding from <a href="https://nlnet.nl/discovery/">NGI Zero DISCOVERY</a> that
+has supported several developers over the last four years to work on the
+<a href="../gns.html">GNU Name System</a> and related subsystems.-->
+</p>
+{% endblock body_content %}
diff --git a/template/news/2022-12-0.19.1.html.j2 b/template/news/2022-12-0.19.1.html.j2
new file mode 100644
index 00000000..6e3b86a2
--- /dev/null
+++ b/template/news/2022-12-0.19.1.html.j2
@@ -0,0 +1,24 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.19.1</h1>
+<p>
+This is a bugfix release for gnunet 0.19.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.1.tar.gz">gnunet-0.19.1.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.1.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-01-0.19.2.html.j2 b/template/news/2023-01-0.19.2.html.j2
new file mode 100644
index 00000000..2e85c512
--- /dev/null
+++ b/template/news/2023-01-0.19.2.html.j2
@@ -0,0 +1,24 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>GNUnet 0.19.2</h1>
+<p>
+This is a bugfix release for gnunet 0.19.1.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.2.tar.gz">gnunet-0.19.2.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.19.2.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">bug tracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-02-0.19.3.html.j2 b/template/news/2023-02-0.19.3.html.j2
new file mode 100644
index 00000000..b62f17db
--- /dev/null
+++ b/template/news/2023-02-0.19.3.html.j2
@@ -0,0 +1,27 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+{% set newver = '0.19.3' %}
+{% set oldver = '0.19.2' %}
+<main id="maincontent">
+<h1>GNUnet {{newver}}</h1>
+<p>
+This is a bugfix release for gnunet {{oldver}}.
+Note that starting with this release, we will no longer ship a verbose ChangeLog file in the tarball. The git log serves this purpose now.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz">gnunet-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}">git log</a>, the <a href="https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}">NEWS</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?version_id=417">bug tracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-02-libgnunetchat-0.1.3.html.j2 b/template/news/2023-02-libgnunetchat-0.1.3.html.j2
new file mode 100644
index 00000000..f3c951eb
--- /dev/null
+++ b/template/news/2023-02-libgnunetchat-0.1.3.html.j2
@@ -0,0 +1,21 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>libgnunetchat 0.1.3 released</h1>
+<p>
+This is mostly a bugfix and compatibility release for libgnunetchat 0.1.2. But it will also change the build process of libgnunetchat to use Meson instead of GNU Automake and it will ensure compatibility with latest changes in GNUnet 0.19.0. The required version of GNUnet to build this library is 0.19.3 for compatibility reasons though.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.3.tar.xz">libgnunetchat-0.1.3.tar.xz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.1.3.tar.xz.sig">libgnunetchat-0.1.3.tar.xz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-02-messenger-gtk-0.8.0.html.j2 b/template/news/2023-02-messenger-gtk-0.8.0.html.j2
new file mode 100644
index 00000000..ef1c31b4
--- /dev/null
+++ b/template/news/2023-02-messenger-gtk-0.8.0.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>Messenger-GTK 0.8.0</h1>
+<p>
+  Following the new release of "libgnunetchat" there have been some changes regarding the applications utilizing it. So we are pleased to announce the new release of the Messenger-GTK application. This release will be compatible with libgnunetchat 0.1.3 and GNUnet 0.19.3 upwards.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.8.0.tar.xz">messenger-gtk-0.8.0.tar.xz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.8.0.tar.xz.sig">messenger-gtk-0.8.0.tar.xz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.8.0</h4>
+<ul>
+  <li>A simple media player has been added to the user interface to play received audio and video files without a third-party application.</li>
+  <li>Multiple crashes and breaking issues have been fixed.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/messenger-gtk.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>Chats still require a reliable connection between GNUnet peers. So this still depends on the upcoming NAT traversal to be used outside of local networks for most users (see <a href="https://bugs.gnunet.org/view.php?id=5710">#5710</a>).</li>
+  <li>File sharing via the FS service should work in a GNUnet single-user setup but a multi-user setup breaks it (see <a href="https://bugs.gnunet.org/view.php?id=7355">#7355</a>)</li>
+  <li>Mobile devices might come with multiple sensors per camera which doesn't get recogniced by the GStreamer pipeline. As soon as libcamera supports those devices, there will be changes to utilize that fixing this issue.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>.
+</p>
+<h2>messenger-cli 0.1.1</h2>
+<p>
+  There's also a new release of the terminal application using the GNUnet Messenger service. But since that's only a release to provide compatibility with changes in its dependencies it is only a minor release without adding new features.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.1.1.tar.xz">messenger-cli-0.1.1.tar.xz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.1.1.tar.xz.sig">messenger-cli-0.1.1.tar.xz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-04-0.19.4.html.j2 b/template/news/2023-04-0.19.4.html.j2
new file mode 100644
index 00000000..41b39572
--- /dev/null
+++ b/template/news/2023-04-0.19.4.html.j2
@@ -0,0 +1,28 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+{% set newver = '0.19.4' %}
+{% set oldver = '0.19.3' %}
+<main id="maincontent">
+<h1>GNUnet {{newver}}</h1>
+<p>
+This is a bugfix release for gnunet {{oldver}}.
+Special thanks goes out to ulfvonbelow who provided an array of patches.
+This is not an April Fool's joke.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz">gnunet-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}">git log</a>, the <a href="https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}">NEWS</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?version_id=417">bug tracker</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-08-GSoC-QUIC.html.j2 b/template/news/2023-08-GSoC-QUIC.html.j2
new file mode 100644
index 00000000..e9d41fc8
--- /dev/null
+++ b/template/news/2023-08-GSoC-QUIC.html.j2
@@ -0,0 +1,36 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>GSoC Work Product: GNUnet over QUIC</h1>
+<p>
+ Hi, my name is Marshall and throughout the summer of 2023 I worked on developing a new communicator for the GNUnet transport service. I learned a lot about GNUnet through my development experience. Here are some details about the journey!
+</p>
+<h2>Goals of the Project.</h2>
+<p>
+  The goal of this project was to develop a new transport, QUIC, for the <a href="https://docs.gnunet.org/developers/transport-ng/transport-ng.html">Transport Next Generation (TNG) service</a>.  TNG is a successor to the previous transport plugins and will be running in the fall 2023 GNUnet release. At the time of writing, GNUnet currently supports transports over TCP, UDP, and UNIX sockets. 
+  I chose to implement a QUIC transport communicator due to the rising popularity and speed of this protocol. Because of this popularity, QUIC will be a great transport protocol for GNUnet traffic to sit on top of. QUIC is intended to be a faster alternative to TCP and tries to address some issues that TLS has.
+</p>
+<h2>What I completed.</h2>
+<p>
+One of the first steps was deciding on a library that can process QUIC packets and would be available to users running different operating systems.
+We chose to go with <a href="https://github.com/cloudflare/quiche">Cloudflare's Quiche library</a> because the C API seemed simpler than other available libraries. Installing cloudflare-quiche via the Homebrew package manager (MacOS) did not actually install the libraries properly for linking with other C programs so I made a pull request in the Homebrew repository and <a href="https://github.com/Homebrew/homebrew-core/commit/227fa616059fdb2157628535b85a801bbb5613f5">fixed the formula</a>.
+After this, I worked on handling the receiving functionality of the communicator. This involved reading from the socket then processing the QUIC packets using the Quiche library. Then I implemented the ability to send messages in a similar manner. One of the last steps involved connecting everything together with the transport service so that the communicator can receive information about peers and relay messages.
+Once I finished these tasks, the QUIC communicator got merged upstream and is currently an experimental feature. This is due to the packaging situation with Quiche as it is difficult for some users to install the library, and there still may be bugs lingering in the QUIC communicator. More testing and refinement is needed to offer a truly robust and reliable communicator.
+Link to source code: <a href="https://git.gnunet.org/gnunet.git/tree/src/transport/gnunet-communicator-quic.c">QUIC communicator</a>.
+</p>
+<h2>The current state.</h2>
+<p>
+The QUIC communicator currently functions and passes basic communicator tests. That being said, there are some latency issues that need to be addressed. Since the communicator suite is designed to run alongside the new TNG service, it is currently not usable since TNG is still under development (as mentioned previously). Mentioned below are some other things that have yet to be implemented in the QUIC communicator, but will be fixed in the future.
+</p>
+<h2>Future Work.</h2>
+<p>
+We still need to develop a more permanent solution to the certificate generation so that the Quiche API functions properly. This <a href="https://git.gnunet.org/gnunet.git/tree/src/transport/gnunet-transport-certificate-creation.in">certificate generation</a> has been done in previous implementations (for example the HTTPS plugin). Currently, we are using static, example certificates. Adding timers to each QUIC connection so that a timeout will trigger a connection to close also needs to be implemented. Finally, we should look into lowering the latency by finding points where the communicator is too slow and optimizing it.
+</p>
+<h2>Challenges I Encountered.</h2>
+<p>
+One of the challenges was reverse engineering the Quiche C API because it has such limited documentation. I learned how to make use of the API by looking at the very simple example client and server examples that are provided in the Quiche repository. There is documentation for the Rust API which seems to operate pretty similarly, so this was helpful too at times. I overcame this challenge with the help and guidance of my mentor Martin Schanzenbach.
+</p>
+<h2>Final notes.</h2>
+Overall, my experience with GNUnet was fantastic. My mentors were friendly and consistently available when I needed help, and I thank them for that. I'm thankful for the GNUnet community for being welcoming and understanding toward new open source developers like myself. I had a lot of fun learning how GNUnet works while developing my project. I am looking forward to contributing to GNUnet in the future!
+{% endblock body_content %}
diff --git a/template/news/2023-09-0.20.0.html.j2 b/template/news/2023-09-0.20.0.html.j2
new file mode 100644
index 00000000..726cc78e
--- /dev/null
+++ b/template/news/2023-09-0.20.0.html.j2
@@ -0,0 +1,70 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+{% set newver = '0.20.0' %}
+{% set oldver = '0.19.3' %}
+<main id="maincontent">
+  <h1>GNUnet {{newver}} released</h1>
+<p>
+  We are pleased to announce the release of GNUnet {{newver}}.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This is a new major release.
+  It breaks protocol compatibility with the 0.19.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.19.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.19.x peers will be able to communicate with Git
+  master or 0.20.x peers, but some services will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the {{newver}} release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz">gnunet-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-{{newver}}.tar.gz">gnunet-gtk-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-{{newver}}.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-{{newver}}.tar.gz">gnunet-fuse-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-{{newver}}.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://www.gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Changes</h4>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}">git log</a>, the <a href="https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}">NEWS</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?version_id=417">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+This release was the work of many people. The following people contributed code and were thus easily identified:
+Christian Grothoff, t3sserakt, TheJackiMonster, Marshall Stone, Özgür Kesim and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-11-RFC9498.html.j2 b/template/news/2023-11-RFC9498.html.j2
new file mode 100644
index 00000000..1b00efc9
--- /dev/null
+++ b/template/news/2023-11-RFC9498.html.j2
@@ -0,0 +1,48 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>RFC 9498: The GNU Name System</h1>
+<p>
+  We are happy to announce that our <i>The GNU Name System</i> (GNS) specification is now published as
+  <a href="https://www.rfc-editor.org/rfc/rfc9498.html">RFC 9498</a>.
+</p>
+<p>
+  GNS addresses long-standing <a href="https://www.wired.com/2014/03/quantum/">security</a> and
+  <a href="https://roarmag.org/essays/nsa-leak-domain-name-system/">privacy</a> issues in the ubiquitous
+  <a href="https://www.rfc-editor.org/rfc/rfc882">Domain Name System (DNS)</a>.
+  Previous attempts to secure DNS (<a href="https://www.rfc-editor.org/rfc/rfc9364">DNSSEC</a>) fail to address <a href="https://www.rfc-editor.org/rfc/rfc8324">critical security issues</a>
+  such as end-to-end security, query privacy, censorship, and centralization of root zone governance.
+  After 40 years of patching, it is time for a new beginning.
+</p>
+<p>
+  The GNU Name System is our contribution towards a decentralized and
+  censorship-resistant domain name resolution system that provides a
+  privacy-enhancing alternative to the Domain Name System (DNS).
+</p>
+<p>
+  As part of our work on RFC 9498, we have also contributed to the specification
+  of the <a href="https://www.rfc-editor.org/rfc/rfc9476.html">.alt top-level
+  domain</a> to be used by alternative name resolution systems and have
+  established <a href="https://gana.gnunet.org/dot-alt/dot_alt.html">the GANA registry for ".alt"</a>.
+</p>
+<p>
+  GNS is implemented according to RFC 9598 in GNUnet 0.20.0. It is also implemented
+  as part of <a href="https://git.gnunet.org/gnunet-go.git/">GNUnet-Go</a>.
+</p>
+<p>
+  We thank all reviewers for their comments.
+  In particular, we thank D. J. Bernstein, S. Bortzmeyer, A. Farrel, E. Lear, and R. Salz for their insightful and detailed technical reviews.
+  We thank J. Yao and J. Klensin for the internationalization reviews.
+  We thank Dr. J. Appelbaum for suggesting the name "GNU Name System" and Dr. Richard Stallman for approving its use.
+  We thank T. Lange and M. Wachs for their earlier contributions to the design and implementation of GNS. 
+  We thank J. Yao and J. Klensin for the internationalization reviews.
+  We thank <a href="https://nlnet.nl">NLnet</a> and <a href="https://nlnet.nl/project/GNS/">NGI DISCOVERY</a> for funding work on the GNU Name System.
+</p>
+<p>
+  The work does not stop here: We encourage further implementations of RFC 9498
+  to learn more both in terms of technical documentation and actual deployment
+  experiences.
+  Further, we are currently working on the specification of the
+  <a href="https://lsd.gnunet.org/lsd0004">R<sup>5</sup>N DHT</a> and <a href="https://lsd.gnunet.org/lsd0003">BFT Set Reconciliation</a> which are underlying
+  building blocks of GNS in GNUnet and not covered by RFC 9498.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2023-12-NGI-Entrust-GNS-TLDs-Update.html.j2 b/template/news/2023-12-NGI-Entrust-GNS-TLDs-Update.html.j2
new file mode 100644
index 00000000..98e01420
--- /dev/null
+++ b/template/news/2023-12-NGI-Entrust-GNS-TLDs-Update.html.j2
@@ -0,0 +1,32 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>Update for NGI Zero Entrust: GNS to DNS Migration and Zone Management</h1>
+<p>
+  We are happy to announce that we have successfully completed two Milestones:
+  <ul>
+    <li>Milestone 2a: A GNS Registrar Backend.</li>
+    <li>Milestone 2b: A GNS Registrar Frontend.</li>
+  </ul>
+</p>
+<p>
+The resulting code can be found <a href="https://git.gnunet.org/gnunet-gns-registrar.git/">in the usual place</a>.
+There are no tarballs available for the time being.
+The component is built with simplicity and privacy in mind: There are <b>no</b> accounts required; we also refrained from using JavaScript for the front end (for now).
+This component effectively replaces the "first-come, first-served" GNS name registration service previously shipped as part of GNUnet.
+Hence the service at <a href="https://fcfs.gnunet.org">https://fcfs.gnunet.org</a> has been replaced.
+The registrar integrates with <a href="https://www.taler.net">GNU Taler</a>, allowing you to test both functionalities at the same time!
+Don't worry, you do not have to use actual money, as you can use the demo currency from the <a href="https://demo.taler.net">Taler demonstrator</a> to register names for a relatively small portion of the play money you receive when you sign up there.
+</p>
+<p>
+We encourage you to try it out now and register you own zone key.
+We plan to ship this zone in the default configuration of the upcoming GNUnet 0.21 release under the domain ".pin.gns.alt".
+Note that current releases are incompatible with GNUnet, and this also applies to the node connected to our registrar deployment.
+</p>
+<p>
+  Watch this space and the mailing list for updates!
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/entrust/">NGI Zero Entrust Programme</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-02-NGI-Webinar-GNS.html.j2 b/template/news/2024-02-NGI-Webinar-GNS.html.j2
new file mode 100644
index 00000000..7bb55931
--- /dev/null
+++ b/template/news/2024-02-NGI-Webinar-GNS.html.j2
@@ -0,0 +1,16 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <h1>NGI Webinar: The GNU Name System and the road to publishing an RFC</h1>
+<p>
+We have been invited by <a href="https://nlnet.nl">NLnet</a> to present the
+GNU Name System and our efforts to create and publish <a href="https://www.rfc-editor.org/rfc/rfc9498.html">RFC 9498</a>.
+</p>
+<p>
+You can find the recording and slides on the <a href="https://nlnet.nl/events/20240222/index.html">NLnet webinar page</a>.
+It includes a live demo of our <a href="https://fcfs.gnunet.org">GNS registrar</a> with integrated <a href="https://taler.net">GNU Taler</a> payments.
+</p>
+<p>
+  The work on GNS was generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their NGI Search and Discovery and <a href="https://nlnet.nl/entrust/">NGI Zero Entrust Programme</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-03-0.21.0.html.j2 b/template/news/2024-03-0.21.0.html.j2
new file mode 100644
index 00000000..8c8d900a
--- /dev/null
+++ b/template/news/2024-03-0.21.0.html.j2
@@ -0,0 +1,77 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+{% set newver = '0.21.0' %}
+{% set oldver = '0.20.0' %}
+<main id="maincontent">
+  <h1>GNUnet {{newver}} released</h1>
+<p>
+  We are pleased to announce the release of GNUnet {{newver}}.
+  <br/>
+  GNUnet is an alternative network stack for building secure, decentralized and
+  privacy-preserving distributed applications.
+  Our goal is to replace the old insecure Internet protocol stack.
+  Starting from an application for secure publication of files, it has grown to
+  include all kinds of basic protocol components and applications towards the
+  creation of a GNU internet.
+</p>
+<p>
+  This release marks a noteworthy milestone in that it includes a completely
+  new <a href="https://docs.gnunet.org/v0.21.0/users/subsystems.html#transport-ng-next-generation-transport-management">transport layer</a>.
+  It lays the groundwork for fixing some major design issues and may also
+  already alleviate a variety of issues seen in previous releases related to
+  connectivity.
+  This change also deprecates our testbed and ATS subsystem.
+</p>
+<p>
+  This is a new major release.
+  It breaks protocol compatibility with the 0.20.x versions.
+  Please be aware that Git master is thus henceforth (and has been for a
+  while) <b>INCOMPATIBLE</b> with
+  the 0.20.x GNUnet network, and interactions between old and new peers
+  will result in issues.
+  In terms of usability, users should be aware that there are still
+  <b>a number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the {{newver}} release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz">gnunet-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig">signature</a>)</li>
+  <li><a href="https://buildbot.gnunet.org/releases/gnunet-{{newver}}-meson.tar.gz">gnunet-{{newver}}-meson.tar.gz</a> (<a href="https://buildbot.gnunet.org/releases/gnunet-{{newver}}-meson.tar.gz.sig">signature</a>) <i>NEW: Test tarball made using the meson build system.</i></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-{{newver}}.tar.gz">gnunet-gtk-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-{{newver}}.tar.gz.sig">signature</a>)</li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-{{newver}}.tar.gz">gnunet-fuse-{{newver}}.tar.gz</a> (<a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-{{newver}}.tar.gz.sig">signature</a>)</li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://www.gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Changes</h4>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}">git log</a>, the <a href="https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}">NEWS</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?version_id=417">bug tracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+</ul>
+<p>
+In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+This release was the work of many people. The following people contributed code and were thus easily identified:
+Christian Grothoff, t3sserakt, TheJackiMonster, Pedram Fardzadeh, dvn, Sebastian Nadler and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-03-0.21.1.html.j2 b/template/news/2024-03-0.21.1.html.j2
new file mode 100644
index 00000000..432ee63c
--- /dev/null
+++ b/template/news/2024-03-0.21.1.html.j2
@@ -0,0 +1,29 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+{% set newver = '0.21.1' %}
+{% set oldver = '0.21.0' %}
+<main id="maincontent">
+<h1>GNUnet {{newver}}</h1>
+<p>
+This is a bugfix release for gnunet {{oldver}}.
+It primarily addresses some connectivity issues introduced with our new transport subsystem.
+</p>
+<p>
+<h4>Links</h4>
+<ul>
+  <li>Source: <a href="https://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz">https://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz</a> (<a href="https://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig">https://ftpmirror.gnu.org/gnunet/gnunet-{{newver}}.tar.gz.sig</a>)</li>
+  <li>Source (meson): <a href="https://buildbot.gnunet.org/releases/gnunet-{{newver}}-meson.tar.gz">https://buildbot.gnunet.org/gnunet-{{newver}}-meson.tar.gz</a> (<a href="https://buildbot.gnunet.org/gnunet-{{newver}}-meson.tar.gz.sig">https://buildbot.gnunet.org/gnunet-{{newver}}-meson.tar.gz.sig</a>)</li>
+  <li>Detailed list of changes: <a href="https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}">https://git.gnunet.org/gnunet.git/log/?h=v{{newver}}</a></li>
+  <li>NEWS: <a href="https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}">https://git.gnunet.org/gnunet.git/tree/NEWS?h=v{{newver}}</a></li>
+  <li>The list of closed issues in the bug tracker: <a href="https://bugs.gnunet.org/changelog_page.php?version_id=437">https://bugs.gnunet.org/changelog_page.php?version_id=437</a></li>
+</ul>
+</p>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="https://ftp.gnu.org/gnu/gnunet/">https://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-03-libgnunetchat-0.3.0.html.j2 b/template/news/2024-03-libgnunetchat-0.3.0.html.j2
new file mode 100644
index 00000000..796e1ff6
--- /dev/null
+++ b/template/news/2024-03-libgnunetchat-0.3.0.html.j2
@@ -0,0 +1,43 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>libgnunetchat 0.3.0 released</h1>
+<p>
+  We are pleased to announce the release of libgnunetchat 0.3.0.
+  <br/>
+  This is a major new release bringing compatibility with the major changes in the Messenger service from latest GNUnet release 0.21.0 adding new message kinds, adjusting message processing and key management. This release will also require your GNUnet to be at least 0.21.0 because of that.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.3.0.tar.gz">libgnunetchat-0.3.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.3.0.tar.gz.sig">libgnunetchat-0.3.0.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.3.0</h4>
+<ul>
+  <li>This release requires the GNUnet Messenger Service 0.3!</li>
+  <li>It allows ticket management for tickets sent from contacts.</li>
+  <li>Deletions or other updates of messages result in separate event calls.</li>
+  <li>It is possible to tag messages or contacts.</li>
+  <li>Invitations can be rejected via tag messages.</li>
+  <li>Contacts can be blocked or unblocked which results in filtering messages.</li>
+  <li>Processing of messages is ensured by enforcing logical order of callbacks while querying old messages.</li>
+  <li>Private messages are readable to its sender.</li>
+  <li>Messages provide information about its recipient.</li>
+  <li>Logouts get processed on application level on exit.</li>
+  <li>Delays message callbacks depending on message kind (deletion with custom delay).</li>
+  <li>New debug tools are available to visualize the message graph.</li>
+  <li>Add test case for message receivement.</li>
+  <li>Multiple issues are fixed.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/libgnunetchat.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-03-libgnunetchat-0.3.1.html.j2 b/template/news/2024-03-libgnunetchat-0.3.1.html.j2
new file mode 100644
index 00000000..a0c1d743
--- /dev/null
+++ b/template/news/2024-03-libgnunetchat-0.3.1.html.j2
@@ -0,0 +1,21 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>libgnunetchat 0.3.1 released</h1>
+<p>
+  This is mostly a bugfix release for libgnunetchat 0.3.0 to reduce build issues.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.3.1.tar.gz">libgnunetchat-0.3.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/libgnunetchat-0.3.1.tar.gz.sig">libgnunetchat-0.3.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2024-03-messenger-gtk-0.9.0.html.j2 b/template/news/2024-03-messenger-gtk-0.9.0.html.j2
new file mode 100644
index 00000000..9e1add98
--- /dev/null
+++ b/template/news/2024-03-messenger-gtk-0.9.0.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<h1>Messenger-GTK 0.9.0</h1>
+<p>
+  Following the new release of "libgnunetchat" there have been some changes regarding the applications utilizing it. So we are pleased to announce the new release of the Messenger-GTK application. This release will be compatible with libgnunetchat 0.3.0 and GNUnet 0.21.0 upwards.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.9.0.tar.gz">messenger-gtk-0.9.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-gtk-0.9.0.tar.gz.sig">messenger-gtk-0.9.0.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.9.0</h4>
+<ul>
+  <li>Contacts can be blocked and unblocked to filter chat messages.</li>
+  <li>Requests for permission to use a camera, autostart the application and running it in background.</li>
+  <li>Camera sensors can be selected to exchange contact information.</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/messenger-gtk.git/tree/ChangeLog">ChangeLog</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>Chats still require a reliable connection between GNUnet peers. So this still depends on the upcoming NAT traversal to be used outside of local networks for most users (see <a href="https://bugs.gnunet.org/view.php?id=5710">#5710</a>).</li>
+  <li>File sharing via the FS service should work in a GNUnet single-user setup but a multi-user setup breaks it (see <a href="https://bugs.gnunet.org/view.php?id=7355">#7355</a>)</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a>.
+</p>
+<h2>messenger-cli 0.2.0</h2>
+<p>
+  There's also a new release of the terminal application using the GNUnet Messenger service. This release will ensure compatibility with changes in libgnunetchat 0.3.0 and GNUnet 0.21.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.2.0.tar.gz">messenger-cli-0.2.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/messenger-cli-0.2.0.tar.gz.sig">messenger-cli-0.2.0.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/index.html.j2 b/template/news/index.html.j2
new file mode 100644
index 00000000..8bfd973b
--- /dev/null
+++ b/template/news/index.html.j2
@@ -0,0 +1,58 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+  <div class="container-fluid">
+    <div class="container">
+      <article>
+        <div class="row">
+          <div class="container text-center">
+            <h1>{{ _("News") }}<a name="news"></a></h1>
+            <section>
+              <p>
+                {% trans %}
+                News posts about changes related to
+                GNUnet such as releases and events
+                {% endtrans %}
+                &#8211;
+                <a href="{{ url_localized('rss.xml') }}">{{ _("subscribe to our RSS feed") }}</a>
+              </p>
+            </section>
+          </div>
+        </div>
+        <div class="row">
+          {% for year, yitem in newsdata|selectattr('date.year', 'gt', 2023)|groupby('date.year')|reverse %}
+          <b>{{ year }}</b>
+          <ul class="timeline">
+          {% for item in yitem %}
+          <li>
+              <section class="item-preview">
+               <header>
+                  <h3>{{ item['title']|e }}</h3>
+                  <p class="item-date">
+                    {{ item['date'] }}
+                  </p>
+                </header>
+                <p class="item-abstract">
+                <!--{{ get_abstract('news/' + item['page'], 500) }} <br/>-->
+                  [<a href="{{ url_localized('news/' + item['page']) }}" title="{{ item['date']}}">{{ _("read more") }}</a>]
+                </p>
+              </section>
+            </li>
+          {% endfor %}
+          </ul>
+          {% endfor %}
+        </div>
+        <h2>
+          {% trans %}
+          News archives:
+          {% endtrans %}
+        </h2>
+        <ul>
+        {% for year, yitem in newsdata|selectattr('date.year', 'lt', 2024)|groupby('date.year')|reverse %}
+          <li><a href="{{ 'oldnews-' + year|string + '.html' }}">{{ year }} ({{yitem|length}})</a></li>
+        {% endfor %}
+        </ul>
+      </article>
+    </div>
+  </div>
+{% endblock body_content %}
diff --git a/template/news/oldnews-2011.html.j2 b/template/news/oldnews-2011.html.j2
new file mode 100644
index 00000000..39e76a48
--- /dev/null
+++ b/template/news/oldnews-2011.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2011) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2013.html.j2 b/template/news/oldnews-2013.html.j2
new file mode 100644
index 00000000..d725f006
--- /dev/null
+++ b/template/news/oldnews-2013.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2013) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2018.html.j2 b/template/news/oldnews-2018.html.j2
new file mode 100644
index 00000000..3056892c
--- /dev/null
+++ b/template/news/oldnews-2018.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2018) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2019.html.j2 b/template/news/oldnews-2019.html.j2
new file mode 100644
index 00000000..23691b6c
--- /dev/null
+++ b/template/news/oldnews-2019.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2019) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2020.html.j2 b/template/news/oldnews-2020.html.j2
new file mode 100644
index 00000000..87030010
--- /dev/null
+++ b/template/news/oldnews-2020.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2020) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2021.html.j2 b/template/news/oldnews-2021.html.j2
new file mode 100644
index 00000000..df4e89d0
--- /dev/null
+++ b/template/news/oldnews-2021.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2021) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2022.html.j2 b/template/news/oldnews-2022.html.j2
new file mode 100644
index 00000000..c01ca3f5
--- /dev/null
+++ b/template/news/oldnews-2022.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2022) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2023.html.j2 b/template/news/oldnews-2023.html.j2
new file mode 100644
index 00000000..1a634262
--- /dev/null
+++ b/template/news/oldnews-2023.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2023) }}
+{% endblock body_content %}
diff --git a/template/probnat/api.html.j2 b/template/probnat/api.html.j2
new file mode 100644
index 00000000..64267f69
--- /dev/null
+++ b/template/probnat/api.html.j2
@@ -0,0 +1,54 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("API Documentation") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Sync Protocol</h2>
+      <section>
+        
+        <p>
+          {% trans %}
+          To use the probabilistic NAT traversal library, the peers to be connected must first be synchronized. For that, each peer has to use two API calls.<br/><br/>
+          enum GNUNET_GenericReturnValue<br/>
+          GNUNET_is_burst_ready (struct GNUNET_TIME_Relative rtt_avarage,<br/>
+                                 &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; struct GNUNET_BurstSync *burst_sync,<br/>
+                                 &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; GNUNET_SCHEDULER_TaskCallback task,<br/>
+                                 &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; struct GNUNET_StartBurstCls *task_cls)<br/><br/>
+          and<br/><br/>
+          struct GNUNET_BurstSync *<br/>
+          GNUNET_get_burst_sync_msg (struct GNUNET_TIME_Relative rtt_avarage,<br/>
+                                     &emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&emsp;&ensp; enum GNUNET_GenericReturnValue sync_ready)<br/><br/>
+          The second is to create the synchronisation message which the caller has to send to the other peer.
+          Within GNUnet the Distance Vector DV protocol is used for sending the synchronisation message. Applications which do not want to use the complete GNUnet stack have to use transportion by other means.<br/><br/>
+          The API call needs two parameters. The avarage round trip time rtt_avarage has to be provided by the callers application. In GNUnet this information is constantly calculated from messages delivered by DV. Again, applications not using the GNUnet stack have to assemble this information by themself. The round trip time has to be calculated as the time a message  needs to arrive at another peer plus the time a response to this message needs to travel back. The messages used to measure this time needs to be send via the same transportion mechanism like the burst synchromisation method. The value used in the API should be an average over several RTTs. rtt_average is measured in microseconds. <br/><br/>
+          The second parameter is returned by the first API call and must be temporarily stored to use it in the second. This is the burst synchromisation method, which encapsulates the RTT calculated by the sending peer, and if that peer is ready to sync.<br/><br/>
+          The first API call also needs the avarage RTT and the synchronisation message received from another peer. The callback is called, if both peers are ready to synchronize. Therefore the callback should start the burst mode which will finally do the hole punch for NAT traversal. One can find an example in the GNUnet code src/service/transport/gnunet-service-transport.c in the function handle_flow_control. <br/><br/>
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/probnat/index.html.j2 b/template/probnat/index.html.j2
new file mode 100644
index 00000000..39700c83
--- /dev/null
+++ b/template/probnat/index.html.j2
@@ -0,0 +1,240 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Probabilistic NAT Traversal") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="#idea">{{ _("Project motivation") }}</a>
+      <a class="nav-link" href="#milestones">{{ _("Milestones") }}</a>
+      <a class="nav-link" href="#milestone1">{{ _("Milestone 1") }}</a>
+      <a class="nav-link" href="#milestone2">{{ _("Milestone 2") }}</a>
+      <a class="nav-link" href="#milestone3">{{ _("Milestone 3") }}</a>
+      <a class="nav-link" href="#milestone4">{{ _("Milestone 4") }}</a>
+      <a class="nav-link" href="#milestone5">{{ _("Milestone 5") }}</a>
+      <a class="nav-link" href="#milestone6">{{ _("Milestone 6") }}</a>
+      <a class="nav-link" href="#milestone6">{{ _("Milestone 7") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <section>
+        <p>
+        {% trans %}
+          This project was funded through the NGI Assure Fund, a fund established by <a href="https://nlnet.nl/project/ProbabilisticNAT">NLnet</a>.</br>
+        {% endtrans %}
+        </p>
+      </section>
+      <h2><a name="idea" class="subnav-anchor"></a>{{ _("Project motivation") }}</h2></br>
+      <section>
+        <h4>The Problem</h4></br>
+        <p>
+          {% trans %}
+          For establishing a peer to peer (p2p) network among regular internet users, unhindered connectivity is anything but self-evident. Today consumer devices are often not directly reachable via the internet but quite often are behind a so called NAT delivering only indirect internet connectivity.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <section>
+        <h4>NAT Traversal Methods</h4></br>
+        <p>
+          {% trans %}
+          There are several methods to reach peers who are behind a NAT, but there are as many reasons those existing methods might fail. Manual configuration for example, as it is possible for example with home routers, often does not work for mobile devices like mobile phones. A further category of methods is subsumed under the term NAT hole punching. This exploits a behavior of the gateway that keeps the port of an outgoing packet open for a potential response. To make this port known to another peer a third peer is needed who is not behind a NAT. Using this method for a privacy preserving network like GNUnet, this could facilitate eclipse attacks (isolating a peer) which then can be used for deanonymization attacks and cencorship. Also any additional infrastructure needed to provide some kind of functionality has to be maintained by someone, becoming a target and/or point of failure. Therefore this method is not suitable. More sophisticated methods like "Autonomous NAT Traversal (pwnat)" using ICMP fake message, which do not need a third party for the initiation of the connection, are not successful in all circumstances, because this method depend on the behavior of the NAT firewall. All methods have in common that the external IP address of the peer behind the NAT must be known.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <section>
+        <h4>Alternative Solution</h4></br>
+        <p>
+          {% trans %}
+          Two peers trying to connect to each other will send out a burst of connection attempts to the other peer on different ports. The sheer vast amount of connections attempts from both side will lead to a high probability that two connection attempts from both peers onto the same port will be at the same time leading to a successful connection between those peers. If two natted peers are using the method to start a burst of connection attempts, this method still needs the global IP of the other peer and a “start signal” to coordinate. In the NGI Assure project <a href="../l2o">L2O</a> we are establishing a backchannel with neighbourhood routing over an ad-hoc distance vector protocol to solve the problem of not directly connected peers. The peers serving as hops to a distant peer which are a direct neighbour of the start or end peer on that path do know the global IP address of the start or end peer. If those two peers like to use the burst method for hole punching the global IP address is known. Via the distance vector protocol we are also able to communicate the "start signal".
+          {% endtrans %}
+        </p></br>
+      </section>
+      <section>
+        <h4>Usage</h4></br>
+        <p>
+          {% trans %}
+          We we have encapsulated the functionality in a library. The library can be used under the following requirements:
+          <ul>
+                <li>The caller of the API has to know the external IP address of the other peer.</li>
+                <li>The peers trying to communicate with each other need an indirect way to exchange messages in order to synchronize with each other.</li>
+          </ul>
+          These two requirements are not covered by the library. For more details have a look <a href="api.html">here</a>.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h2><a name="milestones" class="subnav-anchor"></a>{{ _("Milestones") }}</h2></br>
+      <p>The next milestone to be reached is milestone 1.</p></br>
+      <h3><a name="milestone1" class="subnav-anchor"></a>{{ _("Milestone 1 Test Infrastructure") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+        Extending the testing framework, which was already designed and implemented for the L2O
+project. <a href="mile1.html">Details</a>
+        <ul>    
+    <li>Enhance the testing framework with a new kind of component (NAT component).</li>
+    <li>Implement logic to keep ports open used during network translation.</li>
+    <li>Extend the test framework configuration to configure the new components.</li>
+    </ul></br>
+            {% endtrans %}
+        </p>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          Test case which tests the new testing functionality. Adding documentation.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone2" class="subnav-anchor"></a>{{ _("Milestone 2 Synchronization") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+            This task is to implement the protocol that is doing the signaling for synchronizing two peers
+which do like to connect to each other. <a href="mile2.html">Details</a>
+            <ul>        
+    <li>Two peers which got connected via DV signaling each other being behind a NAT.</li>
+    <li>Learning the external IP address+port from already connected peers, exchange with the
+peers that want to connect.</li>
+      <li>Set a common start time. One peer is selected to be leading (comparing peer ids like it is
+done in CADET)</li>
+    </ul>
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          Deliverable of this milestone is integrating the protocol implementation into the GNUnet
+stack, a test case which tests that two peers successfully exchange the messages of the
+implemented protocol until the condition is reached that both nodes are ready for the burst
+mode. Additionally there will be a protocol documentation.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone3" class="subnav-anchor"></a>{{ _("Milestone 3 Burst Protocol") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+           Burst to establish connectivity (IP_RAW, SYN send for TCP; normal for UDP). A burst of
+synchronized (same ports on each peer) connection attempts on all available ports will lead to a
+high probability for a successful connection.The connection in the TCP case is not final, because
+the TCP connection is only done in the user space.
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4>
+        <p>
+          {% trans %}
+          The protocol implementation will be integrated into the GNUnet stack, one Test case will
+test two peers are finaly connected (UDP case), another test case for TCP tests if both
+peers end up at the same port and the protocol will be documented.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone4" class="subnav-anchor"></a>{{ _("Milestone 4 TCP Repair") }}</h3></br>
+      <section>
+        <p>
+          {% trans %}
+            For the TCP case the connection was established sending packages from user space using raw
+sockets. To let the kernel know about the TCP connection we will use the “repair mode” of the
+setsockopt() system call.
+            {% endtrans %}
+        </p></br>
+        <h4>Deliverable</h4></br>
+        <p>
+          {% trans %}
+          Integration into the GNUnet stack and a test case testing two peers are finaly (kernel TCP
+socket) connected.
+          {% endtrans %}
+        </p></br>
+      </section>
+      <h3><a name="milestone5" class="subnav-anchor"></a>{{ _("Milestone 5 Privilege Minimization") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            Privilege minimization, using SUID/SGID helpers with required capabilities. We need privileged
+access to system resources for some parts of the protocol, e.g. the TCP repair mode. This task
+will implement helper executables which are doing this privileged access, to be used by other
+components not having special privileges. (see § 2.2.1 Access Control, The GNUnet System,
+https://grothoff.org/christian/habil.pdf)
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+          Helper executables and cli applications using the helpers. Integration into the GNUnet
+stack. Man pages for the cli applications. First release of all the implementation.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone6" class="subnav-anchor"></a>{{ _("Milestone 6 Android Test Infrastructure") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            In this milestone the test framework will be enhanced to run a headless android studio emulator on a namespace node. With this emulator an android device running on that node shall be emulated. Two devices running on different nodes should reach each other via the test framework network. For doing the network connection an app should run on each device. This app should do the networking with a small c library. With this c library we like to test if networking and file access is possible with a c library running using the NDK of Android.
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                The deliverable of this milestone is twofold: the scripts for automation and the automated tests themselves, and a report on the outcome of these tests. If the test case starting an Android app on two nodes doing network communication between those two apps and each app accessing its own filesystem will not work as expected, the task includes an overview of potential approaches for achieving the desired outcomes in other ways.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone6" class="subnav-anchor"></a>{{ _("Milestone 7 GNUnet event loop on Android") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            The c library should also start the GNUnet event loop. Therefore the library will be enhanced by a minimal part of the GNUnet stack to start the event loop. The testing code will be enhanced to use the event loop.
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                The deliverable of this milestone is twofold: the scripts for automation and the automated tests themselves, and a report on the outcome of these tests. If the test case testing the same functionality as in milestone 6, but using the GNUnet event loop, will not work as expected, the task includes an overview of potential approaches for achieving the desired outcomes in other ways.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      <h3><a name="milestone6" class="subnav-anchor"></a>{{ _("Milestone 8 Enhance GNUnet stack on Android") }}</h3><br/>
+      <section>
+        <p>
+          {% trans %}
+            The working test cases of milestone 6 and 7 are prerequisites to tackle this milestone! The library will be enhanced to incorporate the parts of the GNUnet stack necessary to run the test case implemented in the milestones 1 -4.
+            {% endtrans %}
+        </p><br/>
+        <h4>Deliverable</h4><br/>
+        <p>
+          {% trans %}
+                Test case testing the same functionality as in milestone 1 - 4 running on Android.
+          {% endtrans %}
+        </p><br/>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/probnat/mile1.html.j2 b/template/probnat/mile1.html.j2
new file mode 100644
index 00000000..a06f1d6d
--- /dev/null
+++ b/template/probnat/mile1.html.j2
@@ -0,0 +1,84 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Probabilistic NAT Traversal") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 1</h2>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("See revision <a href=\"https://git.gnunet.org/gnunet.git/commit/?h=dev/t3ss/probnatt&id=4b2303a35baa05a966543f036b43bb0cfaf22ab5\">4b2303a</a> on branch dev/t3ss/probnatt") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/transport/nat_router.sh</td><td width="60%" style="vertical-align: top;">Test framework router component to fake kernel behavior to keep a port of an outgoing connection open.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/netjail/nat_node_test.sh</td><td width="60%" style="vertical-align: top;">Test script to just send test messages to another node to open up a port.</td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/netjail/getmsg.sh</td><td width="60%" style="vertical-align: top;">Test script to receive test messages from nat_node_test.sh.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">test_transport_plugin_cmd_nat_mapping.c</td><td width="60%" style="vertical-align: top;">Testcase to start the script which sends test messages to open up ports.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">test_transport_nat_mapping_topo.conf</td><td width="60%" style="vertical-align: top;">Configuration for the test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">test_transport_nat_mapping.sh</td><td width="60%" style="vertical-align: top;">Script to start the test case.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/Makefile.am</td><td width="60%" style="vertical-align: top;">Added nat_node_test.sh and getmsg.sh.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/netjail/netjail_start.sh</td><td width="60%" style="vertical-align: top;">Added node nummber parameter to node start script, and make the script run in background.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/netjail/netjail_stop.sh</td><td width="60%" style="vertical-align: top;">Added node nummber parameter to node stop script.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/testing/testing_api_cmd_exec_bash_script.c</td><td width="60%" style="vertical-align: top;">Bugfixing the script that was initially implemented to do explorative testing of transport integrsation, and which is now also used to start the script which sends test messages.</td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/transport/Makefile.am</td><td width="60%" style="vertical-align: top;">Added test_transport_plugin_cmd_nat_mapping.c</td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+      
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
diff --git a/template/probnat/mile2.html.j2 b/template/probnat/mile2.html.j2
new file mode 100644
index 00000000..2d76796a
--- /dev/null
+++ b/template/probnat/mile2.html.j2
@@ -0,0 +1,105 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<main id="maincontent">
+<article class="container">
+  <header>
+    <h1>{{ _("NGI Assure project: Probabilistic NAT Traversal") }}</h1>
+  </header>
+  <div class="row">
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
+      <a class="nav-link" href="index.html#idea">{{ _("Project main page") }}</a>
+      </nav>
+    </div>
+    <div class="col">
+      <h2>Implementation details milestone 2</h2>
+      <section>
+        <h4><a name="netjail" class="subnav-anchor"></a>{{ _("See revision <a href=\"https://git.gnunet.org/gnunet.git/commit/?h=dev/t3ss/probnatt&id=d0c59f236c93e43a21f9ef0e14e54d5f8bb952bd\">d0c59f2</a>, <a href=\"https://git.gnunet.org/gnunet.git/commit/?h=dev/t3ss/probnatt&id=16b5da18df2d725bbcaa2e6efa05c793492ab445\">16b5da1</a>, <a href=\"https://git.gnunet.org/gnunet.git/commit/?h=dev/t3ss/probnatt&id=c1ef824f95612bea94a28563151efa99e18f47f6\">c1ef824</a> and <a href=\"https://git.gnunet.org/gnunet.git/commit/?h=dev/t3ss/probnatt&id=8de6f974d0fe210e03e891b365613e0bc4a2ceea\">8de6f97</a> on branch dev/t3ss/probnatt") }}</h4>
+        <p>
+          {% trans %}
+          <table width="100%">
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/testing-ng/emu_run.sh</td><td width="60%" style="vertical-align: top;">Script to run several cli commands to start and configure the virtual Android devices.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">scripts/Makefile.am</td><td width="60%" style="vertical-align: top;">Added emu_run.sh script to makefile.</td>
+                </tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/core/test_core_plugin_cmd_run_emu.c</td><td width="60%" style="vertical-align: top;">Test case to run a setup with two natted Android devices in separate subnetworks and one global reachable node.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/core/Makefile.am</td><td width="60%" style="vertical-align: top;">Adding test case to makefile.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/core/test_core_run_emu_topo.conf</td><td width="60%" style="vertical-align: top;">Configuration for the test case.</td>
+                <tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/transport/gnunet-service-transport.c</td><td width="60%" style="vertical-align: top;">Added request to ask arm service for services configured to start and checking if they have started. Added check in log file to se if communicators already connected with transport service.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">include/gnunet_transport_testing_ng_lib.h</td><td width="60%" style="vertical-align: top;">Changes in header file for check of running services and connected communicaors.</td>
+                </tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/transport/gnunet-service-transport.c</td><td width="60%" style="vertical-align: top;">Added functionality to synchronize two peers by comparing the measured RTT of both peers. This code was moved to the util library. For use of that library have a look <a href="api.html">here</a></td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/service/core/Makefile.am</td><td width="60%" style="vertical-align: top;">Adding test case to makefile.</td>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">test_core_just_run_topo.conf</td><td width="60%" style="vertical-align: top;">Change the configuration file to just run peers to manually test to have a setup with two natted peers in separate subnetworks and one global reachable peer.</td>
+                <tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/include/gnunet_protocols.h</td><td width="60%" style="vertical-align: top;">Added the burst sync message to the header file.</td>
+                <tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/include/gnunet_util_lib.h</td><td width="60%" style="vertical-align: top;">Added the new API to the util library.</td>
+                <tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+                <tr>
+                        <td width="40%" style="vertical-align: top;">src/lib/util/Makefile.am</td><td width="60%" style="vertical-align: top;">Added the new API to the Makefile.</td>
+                <tr>
+                <tr>
+                        <td></td><td> </td>
+                </tr>
+          </table>
+          {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</article>
+{% endblock body_content %}
+\ No newline at end of file
diff --git a/template/reclaim/faq.html.j2 b/template/reclaim/faq.html.j2
new file mode 100644
index 00000000..b49b8f6c
--- /dev/null
+++ b/template/reclaim/faq.html.j2
@@ -0,0 +1,26 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / FAQ
+</div>
+<h2 class="text-center">{{ _("Frequently asked questions") }}</h2>
+<br/>
+<div class="container">
+  <ul class="fa-ul">
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How is re:claimID different from</b> <i>&lt;insert other identity provider service here&gt; ?</i></li>
+    <li><i class="fa-li fas fa-comment"></i> Unlike most other identity provider services, re:claimID is not operated by a single service provider or even a federated consortium of service providers. Instead, it is a fully decentralised service operated implicitly by its users. Consequently, large-scale data monetisation, mass-surveillance and other (ab)use of personal data is inherently mitigated.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How much does re:claimID cost?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID is Free Software. We argue that in order for an identity system to be a credible solution for self-sovereign citizens to exercise their right to digital self determination, open and free software as well as services are indispensible.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does re:claimID work?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID uses the GNU Name System as identity and attribute directory service. In order to allow the user to enforce access control decisions, we use a cryptographic access control layer. However, the user is not required to manage any cryptographic keys or manage zones in a namespace. This is done under the hood by re:claimID.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does a website know the attribute data share via re:claimID is correct?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> Short answer: It doesn't.
+      Long answer: Identities are initially self-asserted by the user. re:claimID could, however, also be used to share third party attested attributes (e.g. X.509 certificates). Further, have integrated <a href="https://github.com/Fraunhofer-AISEC/libpabc">Privacy-ABCs</a> for <a href="{{ url_localized('news/2021-05-DISSENS.html') }}">this use case</a>.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>Who is behind re:claimID?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID was initially developed at <a href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> and is part of GNUnet.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>I found a bug!</b></li>
+    <li><i class="fa-li fas fa-comment"></i> We aim to continuously develop and improve re:claimID. Help us by <a href="https://bugs.gnunet.org">reporting any issues you encounter</a>.</li>
+  </ul>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/idps.html.j2 b/template/reclaim/idps.html.j2
new file mode 100644
index 00000000..5101b0d7
--- /dev/null
+++ b/template/reclaim/idps.html.j2
@@ -0,0 +1,30 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / IdPs
+</div>
+<h2 class="text-center">{{ _("For IdPs") }}</h2>
+<br/>
+<div class="container">
+  <h2><b>Step 1:</b> OpenID Service</h2>
+  As an identity provider and credential issuer, you need to setup an OpenID Connect server. There are many servers out there. For a list of servers, check out the <a href="https://openid.net/developers/certified/">OpenID website</a>.
+  One important caveat is that the server should allow you to issue user information inside the signed "ID Token".
+  The configuration regarding what user information goes into the token is of course completely under your discretion.
+  <h2 class="mt-5"><b>Step 2:</b> Configuring the reclaimID client</h2>
+  reclaimID uses special client values which must be registered at the OpenID server. The values are:
+  <ul>
+    <li><b>Client ID</b>: reclaimid</li>
+    <li><b>Client secret</b>: none (public client)</li>
+    <li><b>Redirect URI</b>: https://ui.reclaim</li>
+    <li><b>Grant type</b>: Authorization code</li>
+    <li><b>PKCE</b>: enabled (Optional but highly recommended)</li>
+  </ul>
+  <h2 class="mt-5"><b>Step 3:</b> Configuring a webfinger</h2>
+  You must support the webfinger-based <a href="https://openid.net/specs/openid-connect-discovery-1_0.html">OpenID Connect service discovery</a>.
+  Whenever the user configures an email address for an identity, reclaimID will try to discover the issuing identity provider through the OIDC Discovery protocol. This includes a <a href="https://openid.net/specs/openid-connect-discovery-1_0.html#EmailSyntax">request to the authority part of the email address</a>.
+  The response should point reclaimID to the actual OpenID Connect service <a href="https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata">serving the issuer medatata</a>. reclaimID will try to request all scopes which are listed in the metadata, but does not expect all of them to be granted.
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/index.html.j2 b/template/reclaim/index.html.j2
new file mode 100644
index 00000000..c52b9ad6
--- /dev/null
+++ b/template/reclaim/index.html.j2
@@ -0,0 +1,102 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="container">
+  <div class="row">
+    <div class="container text-center">
+      <img style="width:50%" src="{{ url_static('images/reclaim_logo.png') }}"  alt="reclaimID" />
+      <br/>
+      <p class="mt-4">{{ _("Self-sovereign, Decentralised Identity Management and Personal Data Sharing") }}</p>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Self-sovereign") }}</h2>
+          <p>
+          {% trans %}
+          You manage your identities and attributes locally on your computer. No need to trust a third party service with your data.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+      <div class="col-lg-3 homepageicon">
+        <span class="fas fa-fist-raised"></span>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2 homepageicon">
+        <span class="fas fa-project-diagram"></span>
+      </div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Decentralized") }}</h2>
+          <p>
+          {% trans %}
+          You can share your identity attributes securely over a decentralized name system. This allows your friends to access your shared data without the need of a trusted third party.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Standard-compliant") }}</h2>
+          <p>
+          {% trans %}
+          You can use OpenID Connect to integrate reclaim in your web sites.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+      <div class="col-lg-3 homepageicon">
+        <span class="fab fa-openid"></span>
+      </div>
+    </div>
+  </div>
+</div>
+<hr/>
+<div class="container-fluid">
+  <div class="container">
+    <div class="row">
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/tech.html') }}"><i class="fas fa-cubes"></i><br/>{{ _("Technology") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/motivation.html') }}"><i class="fas fa-fire"></i><br/>{{ _("Motivation") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/faq.html') }}"><i class="fas fa-question"></i><br/>{{ _("FAQ") }}</a>
+      </div>
+    </div>
+    <div class="row">
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/users.html') }}"><i class="fas fa-user"></i><br/>{{ _("For users") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/websites.html') }}"><i class="fas fa-globe"></i><br/>{{ _("For websites") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/idps.html') }}"><i class="fas fa-users"></i><br/>{{ _("For IdPs") }}</a>
+      </div>
+    </div>
+  </div>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/motivation.html.j2 b/template/reclaim/motivation.html.j2
new file mode 100644
index 00000000..880c504e
--- /dev/null
+++ b/template/reclaim/motivation.html.j2
@@ -0,0 +1,34 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Motivation
+</div>
+<h2 class="text-center">{{ _("Motivation") }}</h2>
+<br/>
+<div class="container">
+<p>
+Today, users are often required to share personal data, like email addresses, to use services on the web. As part of normal service operation, such as notifications or billing, services require access to -- ideally fresh and correct -- user data.
+Sharing attributes in the Web today is often done via centralized service providers to reduce data redundancy and to give services access to current, up-to-date information even if the user is currently offline.
+Abuse of this power is theoretically limited by local laws and regulations.
+But, the past has shown that even well-meaning identity providers struggle to keep user data safe as they become major targets for hackers and nation state actors while striving for monetizing anonymized statistics from these data.
+We advocate for a new, decentralized way for users to manage their identities for the following reasons:
+</p>
+<ul class="fa-ul">
+  <li><i class="fa-li fas fa-caret-right"></i> The current state of omniscient identity providers is a significant threat to the users' privacy.</li>
+  <li><i class="fa-li fas fa-caret-right"></i> Users must completely trust the service provider with respect to protecting the integrity and confidentiality of their identity in their interest.</li>
+  <li><i class="fa-li fas fa-caret-right"></i> The service provider itself is facing substantial liability risks given the responsibility of securely managing potentially sensitive personal data of millions of users.</li>
+</ul>
+<p>re:claimID is built as a service on top of the peer-to-peer framework <a href="https://gnunet.org">GNUnet</a>.<br/>
+It emerged from research conducted by the research group "Secure
+Applications and Services" at the <a href="https://www.aisec.fraunhofer.de/de/fields-of-expertise/projekte/reclaim.html">Fraunhofer AISEC</a> research institute.<br/>
+A scientific, peer-reviewed paper on the theoretical foundations of re:claimID
+was published at <a href="https://ieeexplore.ieee.org/document/8456003">TrustCom 2018</a>
+(<a href="https://arxiv.org/abs/1805.06253v1">Arxiv</a>).<br/> re:claimID is
+primarily developed in the
+<a href="https://git.gnunet.org/gnunet.git/tree/src/reclaim">GNUnet source tree</a>.
+Accompanying tools and sources can be found in the
+<a href="https://git.gnunet.org/">Git repositories</a>.
+</p>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/tech.html.j2 b/template/reclaim/tech.html.j2
new file mode 100644
index 00000000..4223cf5b
--- /dev/null
+++ b/template/reclaim/tech.html.j2
@@ -0,0 +1,115 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Technology
+</div>
+<h2 class="text-center">{{ _("Overview") }}</h2>
+<div style="text-align:center">
+  <img style="width:50%" src="{{ url_static('images/reclaim/reclaim_eq.png') }}"/>
+</div>
+<br/>
+<div class="container">
+  <div class="row">
+    <div class="col-lg-6">
+      <h3>
+        {{ _("Decentralised identity directory") }}
+      </h3>
+      <p>
+      {% trans %}
+      The decentralised GNU Name System (GNS) gives users full and exclusive authority over their attributes by sharing them over user-owned namespaces.
+      {% endtrans %}
+      </p>
+    </div>
+    <div class="col-lg-6">
+      <div>
+        <h3>
+          {{ _("Cryptographic access control") }}
+        </h3>
+      </div>
+      <p>
+      {% trans %}
+Users regularly publish fresh, up-to-date attributes which can be retrieved and
+read only by authorized relying parties parties without direct user interaction -- even if the user is offline!
+      {% endtrans %}
+      </p>
+    </div>
+  </div>
+</div>
+<hr/>
+<h2 class="text-center">{{ _("Principles") }}</h2>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-1"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Identity and attribute management") }}</h2>
+        <p>
+        {% trans %}
+      Users regularly publish fresh, up-to-date attributes which can be retrieved by requesting parties without direct user interaction -- even if the user is offline!
+      Access to attributes is controlled through an ecryption based access
+      control layer.
+        {% endtrans %}
+        </p>
+        </section>
+      </div>
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-2.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-2.png') }}"/></a>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-3.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-3.png') }}"/></a>
+      </div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Authorization") }}</h2>
+        <p>
+        {% trans %}
+        To access attributes, requesting parties request authorization from the
+        user thrugh the use of OpenID Connect.
+        If access is granted, the relying party is given the necessary decryption
+        key material.
+        The user may at any time revoke this access or modify the authorization decision.
+        {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-1"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Attribute retrieval") }}</h2>
+        <p>
+        {% trans %}
+      Relying parties retrieve encrypted identity data from the decentralised
+      directory.
+      It is able to decrypt all those attributes that the user has authorized
+      it to access using the respective key.
+        {% endtrans %}
+        </p>
+        </section>
+      </div>
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-4.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-4.png') }}"/></a>
+      </div>
+    </div>
+  </div>
+</div>
+<hr/>
+<h2 style="text-align:center" class="mt-2">Videos and Talks</h2>
+<ul class="fa-ul">
+  <li><i class="fa-li fas fa-caret-right"></i> <a href="https://youtu.be/PlSX-o36Wus?t=5371">IETF Meeting #104; Privacy Enhancements and Assessments Research Group - March 2019</a> (<a href="https://git.gnunet.org/presentations.git/plain/IETF104/slides-104-pearg-reclaim-00.pdf">Slides</a>)</li>
+  <li><i class="fa-li fas fa-caret-right"></i> <a href="https://media.ccc.de/v/ds19-10383-re_claimid">Datenspuren 2019 - September 2019 (German)</a> (<a href="https://git.gnunet.org/presentations.git/plain/datenspuren2019/datenspuren2019.pdf">Slides</a>, English)</li>
+</ul>
+{% endblock body_content %}
diff --git a/template/reclaim/users.html.j2 b/template/reclaim/users.html.j2
new file mode 100644
index 00000000..cac0a997
--- /dev/null
+++ b/template/reclaim/users.html.j2
@@ -0,0 +1,40 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Users
+</div>
+<h2 class="text-center">{{ _("For users") }}</h2>
+<br/>
+<div class="container">
+  <h2><b>Step 1:</b> Installation</h2>
+  <p>
+    Please use the <a href="{{ url_localized('install.html') }}">GNUnet installation guides</a>.
+  </p>
+  <h2 class="mt-5"><b>Step 2:</b> Browser plugin</h2>
+  <p>You also need to install a browser plugin:</p>
+  <div class="centering">
+    <a class="btn btn-primary" target="_blank" rel="noopener noreferrer"
+                                               href="https://addons.mozilla.org/addon/reclaimid/"><i class="fab fa-firefox"></i> Mozilla Firefox</a>
+    <a class="btn btn-primary" target="_blank" rel="noopener noreferrer"
+                                               href="https://chrome.google.com/webstore/detail/reclaimid/jiogompmdejcnacmlnjhnaicgkefcfll"><i class="fab fa-chrome"></i> Chrome / Chromium</a>
+  </div>
+  <br/>
+  <h2 class="mt-5"><b>Step 3:</b> Creating your first identity</h2>
+  <p>Almost there. Now try adding a new identity at <a href="https://ui.reclaim">your local re:claimID instance</a> and add some attributes to it.
+  <br/>
+  <!--<h2 class="mt-5">Websites supporting re:claimID</h2>
+  <p>To test a login with one of your re:claimID identities, you can go to one of the websites supporting it:</p>
+  <ul>
+    <li><a href="https://demo.reclaim-identity.io">Our demo messaging board</a> (<a href="https://gitlab.com/reclaimid/demo">Source</a>)</li>
+    <li><a href="https://eusec.clouditor.io">Clouditor EUSEC project page</a></li>
+  </ul>-->
+  <h2 class="mt-5">Troubleshooting</h2>
+  In case you encounter any problems, please check for <a href="https://bugs.gnunet.org">known issues and report bugs to help us improve re:claimID!</a>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/websites.html.j2 b/template/reclaim/websites.html.j2
new file mode 100644
index 00000000..9966ca1d
--- /dev/null
+++ b/template/reclaim/websites.html.j2
@@ -0,0 +1,44 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Websites
+</div>
+<h2 class="text-center">{{ _("For websites") }}</h2>
+<div class="container">
+  <h2><b>Step 1:</b> Installation</h2>
+  <p>
+    Please use the <a href="{{ url_localized('install.html') }}">GNUnet installation guides</a>.
+  </p>
+  <h2 class="mt-5"><b>Step 2:</b> Registering an OpenID Connect client</h2>
+  <p>The easiest way to manage OpenID Connect client is through our CLI tool:</p>
+  <code class="block">$ gem install reclaim-oidc</code>
+  <p>To register an OpenID Connect client, execute:</p>
+  <code class="block">$ reclaim-oidc --add --client-name myclient --redirect-uri https://mywebsite.com/oidc_cb --description "My Client"</code>
+  <p>You can list all registered clients and your local OpenID Connect metadata required to initiate an authorization code flow by executing:</p>
+  <code class="block">$ reclaim-oidc --list </code>
+  <p>The response will look like this</p>
+  <code class="block">OpenID Connect Provider Information:<br/>
+  ------------------------------------<br/>
+  Authorize Endpoint: http://localhost:7776/openid/authorize<br/>
+  Token Endpoint: http://localhost:7776/openid/token<br/>
+  JSON-Web-Token Algorithm: HS512<br/>
+  JSON-Web-Token key: secret<br/>
+  Example Authorization Redirect:<br/>
+  https://api.reclaim/openid/authorize?client_id=&lt;client_id&gt;&amp;redirect_uri=&lt;redirect_uri&gt;&amp;response_type=code&amp;scope=email%20full_name&amp;nonce=1234<br/>
+  <br/>
+  Registered Clients:<br/>
+  -------------------<br/>
+  name: myclient<br/>
+  client_id: &lt;client_id&gt;<br/>
+  client_secret: &lt;client_secret&gt;<br/>
+  description: My Client<br/>
+  redirect_uri: https://mywebsite.com/oidc_cb<br/>
+  ...
+  </code>
+  <div class="alert alert-info"><b>NOTE</b>: The client secrets and JWT token signing keys can be configured. However, due to the fact that re:claimID endpoint are running on your local machine, they are not critical.</div>
+  <h2 class="mt-5"><b>Step 3:</b> Website integration</h2>
+  <p>You can use the information above to integrate re:claimID as a generic <a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect Identity Provider</a> into the web application of your choice. The integration steps for this part depend on the application you use. Hence, please refer to your respective documentation or the OpenID Connect specifications.
+  </p>
+</div>
+{% endblock body_content %}
diff --git a/template/roadmap.html.j2 b/template/roadmap.html.j2
index 22c01a41..09d0b7a7 100644
--- a/template/roadmap.html.j2
+++ b/template/roadmap.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <div class="container">
  <div class="row">
    <div class="container text-center">
@@ -10,49 +11,41 @@
      The roadmap is subject to change and its primary purpose it to indicate the current work in progress and future work as well as the path to a stable release. Goals which are currently in active development are marked in <b>bold</b>.
    </p>
    <ul class="timeline">
-      <li>
+      <!--<li>
        <section class="item-preview">
          <header>
            <h3>Short term</h3>
            <p class="item-date">
-            &lt;0.15
+            &le;0.17
            </p>
            <p class="item-abstract">
-            <ul class="fa-ul">
-              <li><span class="fa-li"><i class="far fa-check-square"></i></span><a href="https://gana.gnunet.org">Setup and use names and numbers registration (GANA) for GNUnet
-              subsystems.</a></li>
-              <li><span class="fa-li"><i class="far fa-check-square"></i></span><a href="https://lsd.gnunet.org/lsd0001/">GNU Name System technical specification.</a></li>
-             </ul>
            </p>
          </header>
          </p>
        </section>
-      </li>
+      </li>-->
      <li>
        <section class="item-preview">
          <header>
            <h3>Medium term</h3>
            <p class="item-date">
-            &ge;0.15
+            &lt;1.0
            </p>
            <p class="item-abstract">
            <ul class="fa-ul">
-              <li><span class="fa-li"><i class="far fa-square"></i></span><b>TNG</b>: Transport rewrite. [<a href="https://bugs.gnunet.org/search.php?tag_string=tng">Open issues</a>]
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>TRANSPORT-NG (TNG): Transport layer redesign.</b> [<a href="https://bugs.gnunet.org/search.php?tag_string=tng">Open issues</a>]
                <ul class="fa-ul">
-                  <li><span class="fa-li"><i class="far fa-square"></i></span><b>TNG service</b></li>
+                  <li><span class="fa-li"><i class="far fa-check-square"></i></span>TNG service</li>
-                  <li><span class="fa-li"><i class="far fa-square"></i></span><b>TCP communicator</b></li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>QUIC communicator</b></li>
-                  <li><span class="fa-li"><i class="far fa-square"></i></span><b>UDP communicator</b></li>
+                  <li><span class="fa-li"><i class="far fa-check-square"></i></span>TCP communicator</li>
-                  <li><span class="fa-li"><i class="far fa-square"></i></span><b>UNIX Domain Socket communicator</b></li>
+                  <li><span class="fa-li"><i class="far fa-check-square"></i></span>UDP communicator</li>
-                  <li><span class="fa-li"><i class="far fa-square"></i></span>NAT</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>UNIX Domain Socket communicator</b></li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>NAT</b></li>
                </ul>
              </li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span>CORE/CADET: Performance and correctness improvements.</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>CORE-NG (CONG): Performance and correctness improvements. [<a href="https://bugs.gnunet.org/view.php?id=8596">Open issues</a>]</b></li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span>DHT: Improvements including signed paths and stability improvements. Technical specification.</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>DHT: Technical specification. [<a href="https://lsd.gnunet.org/lsd0004">Draft</a>]</b></li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span>SET improvements to code quality and correctness.</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>Large-scale GNS TLD mirror deployment.</b> [<a href="https://bugs.gnunet.org/view_all_bug_page.php?filter=65f5e2e289d96">Open issues</a>]</li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span>CONVERSATION improvements to performance, latency hiding and usability.</li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span>RECLAIM: Technical specification.</li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span><b>Stable and usable documentation.</b></li>
-              <li><span class="fa-li"><i class="far fa-square"></i></span><b>GNUnet packages available and up-to-date in distributions.</b></li>
             </ul>
            </p>
          </header>
@@ -69,10 +62,14 @@
            <p class="item-abstract">
            <ul class="fa-ul">
              <li><span class="fa-li"><i class="far fa-square"></i></span>Stable release.</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>CADET: Performance and correctness improvements.</li>
              <li><span class="fa-li"><i class="far fa-square"></i></span>Onion routing with RPS</li>
              <li><span class="fa-li"><i class="far fa-square"></i></span>Mix network, pEp integration on top of mix network</li>
              <li><span class="fa-li"><i class="far fa-square"></i></span>Collaborative filtering / news distribution</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>CONVERSATION improvements to performance, latency hiding and usability.</li>
              <li><span class="fa-li"><i class="far fa-square"></i></span>Improved FS design, proper integration with GNS</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>Stable and usable documentation.</b></li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>GNUnet packages available and up-to-date in distributions.</b></li>
             </ul>
            </p>
          </header>
diff --git a/template/rss.xml.j2 b/template/rss.xml.j2
new file mode 100644
index 00000000..6ee0a279
--- /dev/null
+++ b/template/rss.xml.j2
@@ -0,0 +1,46 @@
+{#
+# Copyright (C) 2019, 2020 GNUnet e.V.
+#
+# This code is derived from code contributed to GNUnet eV
+# by nikita <nikita@n0.is>.
+#
+# Permission to use, copy, modify, and/or distribute this software for
+# any purpose with or without fee is hereby granted.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
+# WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
+# WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
+# AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
+# DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
+# PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+# TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+# PERFORMANCE OF THIS SOFTWARE.
+#
+# SPDX-License-Identifier: 0BSD
+#}
+<?xml version="1.0" encoding="UTF-8"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <atom:link href="{{ siteconf['baseurl'] }}{{ lang }}/rss.xml" rel="self" type="application/rss+xml" />
+    <title>{{ siteconf['rsstitle'] }}</title>
+    <language>{{ lang }}</language>
+    <description>{{ siteconf['rssdescr']|e }}</description>
+    <link>{{ siteconf['baseurl'] }}/</link>
+    <lastBuildDate>{{ now }}</lastBuildDate>
+    {% for newspostitem in newsposts %}
+      <item>
+        <guid>{{ siteconf['baseurl'] }}{{ lang }}{{ siteconf['newsloc'] }}{{ newspostitem['page'] }}</guid>
+        <link>{{ siteconf['baseurl'] }}{{ lang }}{{ siteconf['newsloc'] }}{{ newspostitem['page'] }}</link>
+        <pubDate>{{ conv_date_rfc822(newspostitem["date"]) }}</pubDate>
+        <title>{{ newspostitem['title']|e }}</title>
+        <description>
+          <![CDATA[
+             {% filter extract_body %}
+             {% include ('news/' + newspostitem['page'] + ".j2") %}
+             {% endfilter %}
+           ]]>
+        </description>
+      </item>
+    {% endfor %}
+  </channel>
+</rss>
diff --git a/template/use.html.j2 b/template/use.html.j2
index 8dc7abd5..2ad5b6ef 100644
--- a/template/use.html.j2
+++ b/template/use.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
 <article class="container">
  <header>
@@ -11,7 +12,7 @@
      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
      <a class="nav-link" href="#filesharing">{{ _("Filesharing") }}</a>
      <a class="nav-link" href="#cadet">{{ _("CADET") }}</a>
-      <a class="nav-link" href="#groupchat">{{ _("Minimal Groupchat") }}</a>
+      <a class="nav-link" href="#messenger">{{ _("Convenient Messenger") }}</a>
      <a class="nav-link" href="#gns_cli">{{ _("GNS with CLI") }}</a>
      <a class="nav-link" href="#gns_browser">{{ _("GNS with Browser") }}</a>
      <a class="nav-link" href="#vpn">{{ _("VPN") }}</a>
@@ -20,7 +21,7 @@
      </nav>
    </div>
-    <div class="col">
+    <div class="col" style="padding-left: 35px">
      <section>
        <p>
         This document is just a brief introduction on what can be done with GNUnet. Find out much more in our <a ref="https://docs.gnunet.org/">documentation</a>, e.g. in the section <a href="https://docs.gnunet.org/handbook/gnunet.html#toc-Using-GNUnet-1">"using GNUnet"</a> in the handbook.
@@ -213,72 +214,52 @@
        </p>
      </section>
      <section>
-        <h3><a name="groupchat" class="subnav-anchor"></a>{{ _("Chatting with a (simple) client") }}</h3>
+        <h3><a name="messenger" class="subnav-anchor"></a>{{ _("Chatting with a convenient client") }}</h3>
-        <div class="alert" style="background-color: #419edb;">
+        <p>
-             <div class="alert-content">
+          To make chatting a tiny bit easier and prettier, we need to install additional software.
-                  Notice: The groupchat code is not working with the actual GNUnet release atm!
+        </p>
-             </div>
+        <p>
-        </div>
+          You can select one of the options listed <a href="applications.html">here</a> under applications 
-         <p>
+          using the <a href="https://docs.gnunet.org/handbook/gnunet.html#MESSENGER-Subsystem">Messenger service</a>. 
-          To make chatting a tiny bit easier and prettier, we need to install and compile additional software.
+          Those are generally compatible with each other using the same underlying 
-          If you join the chat mentioned below and no one is there, feel free to ping on
+          <a href="https://git.gnunet.org/libgnunetchat.git/">library</a> but tell apart in their user interface and design.
-          IRC/freenode #gnunet and ask if someone can join in to test with you! (But we are
+        </p>
-          trying to be there as often as possible).
+        <p>
-     </p>
+          In other words: You can choose by your own preference how to chat.
-     <p>
+        </p>
-          First we have to install the Nim programming language. Please refer to their <a href="https://nim-lang.org/install.html">project site</a> for further details. The preferred method is using you distributions package manager, e.g. for Debian it would look like this: 
+        <p>
-      </p>
+          After you have picked an application (for example <a href="https://git.gnunet.org/messenger-gtk.git/">Messenger-GTK</a> 
-      <code>
+          or <a href="https://git.gnunet.org/messenger-cli.git/">messenger-cli</a>), follow the instructions for build and installation.
-        $ sudo apt install nim<br>
+          Notice that depending on the picked application, you might need additional dependencies besides the library for the chatting
-        $ nim --version<br>
+          functionality.
-        Nim Compiler Version 1.2.2 [Linux: amd64]<br>
+        </p>
-        Compiled at 2020-06-16<br>
+        <p>
-        Copyright (c) 2006-2020 by Andreas Rumpf<br>
+          Once you installed the application and started it, a dialog should open to ask you for an account to use or whether you want 
-        <br>
+          to create a new one. An account is pretty much an identity which can also be used for <a href="#gns_cli">GNS</a> capabilities.
-        active boot switches: -d:release -d:nativeStackTrace<br>
+          Accounts don't require any information besides a chosen identifier or nick.
-      </code>
+        </p>
-      <p>
+        <p>
-       If the displayed version is <b>1.2.2 or newer</b>, we have a compatible version and can continue downloading and compiling the groupchat. If the version is older (like on Ubuntu 18.04) we can install Nim using a tool called <i>choosenim</i>:
+          Next step is to enter a chat room via your application. The easiest step is choosing a public chat room which is similar to 
-      </p>
+          communicate via <a href="#cadet">CADET</a> through a shared port. Look for a function to add a new room or "platform".
-      <code>
+          You should be able to enter any sort of text as key for the room and confirm.
-          $ curl https://nim-lang.org/choosenim/init.sh -sSf | sh
+        </p>
-      </code>
+        <p>
-      <p>
+          A chat room should open using the entered key as identifier and any other person you share the key with should be able to join
-      Then we follow the onscreen instructions. More information can be found in the <a href="https://nim-lang.org/install.html">official documentation</a>.
+          this room as well using one of the compatible applications as linked above. From here you can simply write text in a proper field
-      </p>
+          and send it as a message to communicate.
-      <p>In the onscreen instructions you'll be ask to add a line to your bashrc - once you've done that, re-read your bash environment to make the change active: 
+        </p>
-      </p>
+        <p>
-      <code>
+          In case of any more advanced functionality it is recommended to look for a guide or more detailed information on the source of the
-        $ source ~/.bashrc
+          used application since implementations can vary, especially the design of user interface.
-      </code>
+        </p>
-      
+        <p>
-      <p>
+          Also you can always use the simplified command line tool `gnunet-messenger` provided by GNUnet itself to open or join a chat with
-          After we have installed (and maybe upgraded) Nim we download and compile the GNUnet groupchat application:
+          its key in a similar way as described above. See the more detailed information in the 
-         </p>
+          <a href="https://docs.gnunet.org/handbook/gnunet.html#Using-the-GNUnet-Messenger">handbook</a> to use it.
-         <p>
+        </p>
-         <code>
-              $ git clone https://git.gnunet.org/groupchat.git<br>
-              $ cd groupchat<br>
-              $ make<br>
-         </code>
-         <p>
-         <p>
-            We can now try to enter a chat server running on another GNUnet node using the command:
-         </p>
-         <p>
-         <code>
-               $ LD_LIBRARY_PATH=/path/to/gnunetlibs ./groupchat --config=/path/to/gnunet.conf --server=88RXABKJNMT426FY81N2DXN0M2X37SW5Q1NR005YPDZ1Q7A22CHG --port=t3ss --nick=YOURNICK<br>
-         </code>
-         <p>
-              The peer key and port name given in this example should work as they are almost always online and running groupchat on port "t3ss".
-         <p>
      </section>
      <section>
        <h3><a name="gns_cli" class="subnav-anchor"></a>{{ _("Name resolution using GNS on the command line") }}</h3>
        <p>The GNU Name Service (GNS) is a fully decentralized alternative to the Domain Name System (DNS). Where GNS does not suffer the same major <a href="https://en.wikipedia.org/wiki/Domain_Name_System#Security_issues">security flaws as DNS</a>.
diff --git a/template/video.html.j2 b/template/video.html.j2
index fe1316b8..f1af3a32 100644
--- a/template/video.html.j2
+++ b/template/video.html.j2
@@ -1,5 +1,6 @@
 {% extends "common/base.j2" %}
 {% block body_content %}
+<main id="maincontent">
  <!--
      FIXME
      - some links are missing