Template and tweaks -> meetings now display. TODO: properly render .rst

i2p2www/meetings/208.rst

@@ -20,7 +20,6 @@ Quick recap
 *Task appointing and disagreements:*
   Currently, people appoint themselves to a task by editing the team.html page (this requires monotone access, so there is at least a level of trust implied before being allowed to appoint yourself).
   However, what happens if people disagree?
-  
   The discussion pointed out that when disagreeing, a discussion should be held (for example on zzz.i2p). If that doesn't resolve the issue, a vote is a possibility, or the Project Manager (zzz) or repository maintainers (welterde, eche|on) can make a decision.
 
 *Status updates:*
@@ -33,7 +32,6 @@ Quick recap
   Filesharing in general and bittorrent more specifically can be either good or bad for I2P.
   On one hand, they could give I2P a bad reputation. On the other hand, they could boost I2P popularity.
   What to do?
-  
   Filesharing on I2P will not be promoted specifically. Instead, general usability should be looked at and improved.
   If people decide to use filesharing on I2P (or any other service, like e-mail or browsing), it should become easier as a result of improving the usability.
 

i2p2www/pages/global/lang.html

@@ -1,5 +1,6 @@
 {%- macro change_lang(lang) -%}
 {%- if request.endpoint == 'site_show' -%}{{ url_for('site_show', lang=lang, page=page) }}
+{%- elif request.endpoint == 'meetings_show' -%}{{ url_for('meetings_show', lang=lang, id=id) }}
 {%- elif request.endpoint -%}{{ url_for(request.endpoint, lang=lang) }}
 {%- else -%}{{ url_for('site_show', lang=lang) }}
 {%- endif -%}

i2p2www/pages/meetings/show.html

@@ -0,0 +1,8 @@
+{% extends "global/layout.html" %}
+{% block title %}Meeting {{ id }}{% endblock %}
+{% block content %}
+{{ header }}
+<pre>
+{{ log }}
+</pre>
+{% endblock %}