'finish up practicalities'

Carreau · Carreau · commit 7cf319e1f40b · 2017-04-17T11:28:04.000-07:00
diff --git a/_includes/css/main.css b/_includes/css/main.css
@@ -25,6 +25,16 @@ html { box-sizing: border-box; }
   #{{id}} .sectiondivider { color: {{ bg }}; }
 {% endfor %}
 
+{% for node in site.practicalities %}
+  {% capture id %}{{ node.id | remove:'/' | downcase }}{% endcapture %}
+  {% capture bg %}{% if site.colors[node.bg] %}{{ site.colors[node.bg] }}{% else %}{{ node.bg }}{% endif %}{% endcapture %}
+  {% capture fg %}{% if site.colors[node.color] %}{{ site.colors[node.color] }}{% else %}{{ node.color }}{% endif %}{% endcapture %}
+  nav .p-{{id}} { border-color: {{ bg }}; }
+  #{{id}} { background-color: {{ bg }} !important; color: {{ fg }}; }
+  #{{id}} a { color: {{ fg }}; }
+  #{{id}} .sectiondivider { color: {{ bg }}; }
+{% endfor %}
+
 
 /* ----- code, syntax highlighting, etc ----- */
 
diff --git a/_practicalities/intro.md b/_practicalities/intro.md
@@ -1,16 +1,22 @@
 ---
+bg: '#4da45e'
+color: white
+title: practicalities
+fa-icon: pencil
+id: bar
 ---
 
-Add note here to explain that this does _not_ prevent _nor_ discourage library
-author to release 2 version of their software one Python 3 only and the other
-python 2.
+We do not discourage authors to release software on Python 2. While this guide
+is mostly written with the assumption that software are going to stop Python 2
+support, it does perfectly apply to a package that wish to not support Python 3,
+or is stopping support for any minor version. 
 
 
 This page gather information and links to resources allowing to release a
 library that stop supporting an older version of Python without causing too
 much disruption for users who haven't upgraded to this new version.
 
-Wether you are a user, or a developer, being aware of the issue listed here, at
+Whether you are a user, or a developer, being aware of the issue listed here, at
 least the main points should ease lots of the pain.
 
 # Too long, did not read:
@@ -20,6 +26,7 @@ least the main points should ease lots of the pain.
  - As maintainer use `setup(..., python_requires='>=3.4')` new option.
  - do use `pip install [-e] .` and do **not** invoke `setup.py` directly.
  - **Fail** early at **install time** if on Python 2.
+ - We are giving a talk at PyCon 2017 (likely recorded), add link here. 
 
 ## The problem
 
diff --git a/_sections/80-update-my-project.md b/_sections/80-update-my-project.md
@@ -15,9 +15,10 @@ encountered both by developers and users during this process.
 We are thus collecting a list of things to be aware of for when transitioning that
 are less obvious. For example : as a developer, how to make sure that
 your package manager like pip does not upgrade your libraries to incompatible
-versions on Python 2. Check [our
-repository](https://github.com/python3statement/python3statement.github.io) for
-more information.
+versions on Python 2. See the [Practicality Page](/practicalities/) for
+informations and Check [our
+repository](https://github.com/python3statement/python3statement.github.io) to
+contribute.
 
 
 
diff --git a/practicalities/index.html b/practicalities/index.html
@@ -19,9 +19,17 @@
 <body>
   <div id="main">
     
+    <nav><ul>
+      {% for node in site.sections %}
+        {% capture id %}{{ node.id | remove:'/' | downcase }}{% endcapture %}
+        <li class="p-{{id}}"><a href="../#{{id}}">{{node.title}}</a></li>
+      {% endfor %}
+    </ul></nav>
+  
 
     {% for page in site.practicalities %}
-        <div class="section">
+        {% capture id %}{{ page.id | remove:'/' | downcase }}{% endcapture %}
+        <div id="{{id}}" class="section p-{{id}}">
 
         <div class="container {{ page.style }}">
           {{ page.content }}
