[GNUnet-SVN] [www] 06/11: fix links for subnav

[gnunet]

This is an automated email from the git hooks/post-receive script.

xrs pushed a commit to branch master
in repository www.

commit 835f146b20daeae7c9da2f438486f881c302e47f
Author: xrs <address@hidden>
AuthorDate: Mon Jul 1 20:53:11 2019 +0200

    fix links for subnav
---
 static/styles.sass    | 11 ++++++-----
 template/gsoc.html.j2 |  6 +++---
 template/use.html.j2  | 14 +++++++-------
 3 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/static/styles.sass b/static/styles.sass
index 8fecbf0..8309ebf 100644
--- a/static/styles.sass
+++ b/static/styles.sass
@@ -284,12 +284,13 @@ header
   margin-top: 30px
   margin-bottom: 50px
 
+// Some docs are too long, thus there is a need for a subnav.
+// Use "subnav" class for the submenu.
+// Use "subnav-anchor" class for the a-tags right before a section title.
 .subnav
   a.nav-link
     &:link, &:visited
       color: #419edb !important
-
-h1,h2,h3,h4,h5,h6
-  a 
-    position: relative
-    top: -80px
+a.subnav-anchor
+  position: relative
+  top: -80px
diff --git a/template/gsoc.html.j2 b/template/gsoc.html.j2
index ad8c865..1f5d4f0 100644
--- a/template/gsoc.html.j2
+++ b/template/gsoc.html.j2
@@ -27,7 +27,7 @@
     </div>
     <div class="col">
 
-  <h2>{{ _("Current projects (2019)") }}<a name="current"></a></h2>
+  <h2><a name="current" class="subnav-anchor"></a>{{ _("Current projects 
(2019)") }}</h2>
   <section>
     <h4>Android Port</h4>
     <p>
@@ -177,7 +177,7 @@
     </p>
   </section>
   <!-- Past projects: Previously proposed, but left unfinished. Inspiration 
for students. -->
-  <h2>{{ _("Past projects") }}<a name="past"></a></h2>
+  <h2><a name="past" class="subnav-anchor"></a>{{ _("Past projects") }}</h2>
   <section>
     <h4>Rust APIs for GNUnet services</h4>
     <p>
@@ -565,7 +565,7 @@
       {% endtrans %}
     </p>
   </section>
-  <h2>{{ _("Finished projects") }}<a name="finished"></a></h2>
+  <h2><a name="finished" class="subnav-anchor"></a>{{ _("Finished projects") 
}}</h2>
   <!-- Commentary: Finished projects, descriptions and Links to write-ups 
about them. -->
   <h3>2018</h3>
   <section>
diff --git a/template/use.html.j2 b/template/use.html.j2
index 472d0f8..e420a39 100644
--- a/template/use.html.j2
+++ b/template/use.html.j2
@@ -61,7 +61,7 @@
 
 
       <section>
-        <h3><a name="filesharing"></a>{{ _("Filesharing") }}</h3>
+        <h3><a name="filesharing" class="subnav-anchor"></a>{{ 
_("Filesharing") }}</h3>
 
         <p>
           Let's publish a file in the GNUnet filesharing network. We use the 
keywords
@@ -102,7 +102,7 @@
 
 
       <section>
-        <h3><a name="cadet"></a>{{ _("CADET (and Chat)") }}</h3>
+        <h3><a name="cadet" class="subnav-anchor"></a>{{ _("CADET (and Chat)") 
}}</h3>
 
         <p>
           We can use the `gnunet-cadet` command line tool to open a port and 
from
@@ -136,7 +136,7 @@
       </section>
 
       <section>
-        <h3><a name="groupchat"></a>{{ _("Chatting with a (simple) client") 
}}</h3>
+        <h3><a name="groupchat" class="subnav-anchor"></a>{{ _("Chatting with 
a (simple) client") }}</h3>
          <p>
               To chat a tiny bit prettier, we need to install and compile 
additional software.
               If you join the chat mentioned below and no one is there, feel 
free to ping on
@@ -178,7 +178,7 @@
 
 
       <section>
-        <h3><a name="gns_cli"></a>{{ _("Name resolution using GNS on the 
command line") }}</h3>
+        <h3><a name="gns_cli" class="subnav-anchor"></a>{{ _("Name resolution 
using GNS on the command line") }}</h3>
 
         <p>GNS is the GNU name service, a fully decentralized alternatice to 
DNS. We'll publish an IP address in a GNS record try to resolve it on the 
command line. First we need an identity which is the
           equivalent to a zone in DNS. We'll call it "myself" and create it 
using the
@@ -250,7 +250,7 @@
 
 
       <section id='gns_proxy'>
-        <h3><a name="gns_browser"></a>{{ _("Name resolution using GNS with a 
browser") }}</h3>
+        <h3><a name="gns_browser" class="subnav-anchor"></a>{{ _("Name 
resolution using GNS with a browser") }}</h3>
 
         <p>
           In the previous use case "Name resolution using GNS on the command 
line" we got an idea
@@ -327,7 +327,7 @@
         </p>
       </section>
       <section>
-        <h3><a name="vpn"></a>{{ _("VPN") }}</h3>
+        <h3><a name="vpn" class="subnav-anchor"></a>{{ _("VPN") }}</h3>
         <p>
               VPN can be used to share your Internet connection (yes, this may 
be dangerous, just as running a Tor exit node) or to provide access to services 
on your host (this should be less dangerous, as long as those services are 
secure).
         </p>
@@ -388,7 +388,7 @@
         </p>
       </section>
       <section>
-        <h3><a name="conversation"></a>{{ _("Conversation") }}</h3>
+        <h3><a name="conversation" class="subnav-anchor"></a>{{ 
_("Conversation") }}</h3>
         <p>
           TBD, see <a 
href="https://docs.gnunet.org/#First-steps-_002d-Using-GNUnet-Conversation";>chapter
 "Using GNUnet Conversation" in the handbook.</a>
         </p>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.