Issue 3366 - Add tab for press releases to eyeo.com/press

includes/press/releases.tmpl

+{% set releases_en = [
+  ("October 30, 2015", "First Free Ad Blocker on the Apple App Store Arrives; The Adblock Autumn:  Adblock Plus for iOS 2-nd from ABP this Month", "2015-09-30-ABP_for_iOSApp-WEB.pdf"),

[Thomas Greiner, 2015/12/14 12:56:58]

Actually, I meant that the editor (in this case Ben) should only need to enter
"2015-09-30" and that a Python filter sorts and formats those dates accordingly.

Thereby we avoid spelling mistakes, ordering issues and inconsistent date
formats. That would also make it easier for us to make it translatable whenever
we decide to add those capabilities to eyeo.com.

Sidenote: The document title says "2015-09-30" which is "September 30, 2015".
Again, that's one of the benefits of leaving this to Python.

[saroyanm, 2015/12/14 16:30:06]

I've created a ticket to tackle that issue later because of tight schedule:
https://issues.adblockplus.org/ticket/3410 

+  ("October 29, 2015", "Adblock Plus To Invite An Independent Board to Manage 'Acceptable Ads' Program", "2015-09-29-AA_independent_board-WEB.pdf"),
+  ("October 15, 2015", "Sweet 4­‐Peat for Users: Adblock Plus Victorious In Court Against Axel Springer", "2015-09-15-Cologne-lawsuitWIN-WEB.pdf"),
+  ("September 08, 2015", "Adblock Plus beats Apple to the punch; Ships Adblock Browser ahead of iOS 9", "2015-09-08-AdblockBrowserforiOSLaunch(POST)-WEB.pdf"),
+  ("September 08, 2015", "Adblock Plus Escapes Exile; Returns to Google Play Store", "2015-09-08-Adblock BrowserforAndroid(POST)-WEB.pdf"),
+  ("July 08, 2015", "University Tests Adblock Plus on Enterprise Network; Finds 40% Traffic Reduction", "2015-07-08-ABP-SFUStudyWEB.pdf"),
+  ("May 19, 2015", "Adblock Plus Builds First Mobile Browser From the Ground Up; Leaves Ad Industry With Nowhere to Hide", "2015-05-19-AdblockBrowserAndroidBeta-WEB.pdf"),
+  ("January 27, 2015", "Adblock Plus for Internet Explorer Officially Out of Beta", "2015-01-27-Maxthon-US-WEB.pdf"),
+  ("April 04, 2014", "Research Study Finds ‘Loud’ Website Ads Do Not Work", "2014-04-29-Eyetracking-WEB.pdf"),
+  ("October 10, 2013", "Adblock Plus Available for Safari; Mac Owners Rejoice", "2013-10-10-29-ABP-on-Safari-WEB.pdf"),
+] %}
+
+{% set releases_de = [
+  ("September 30, 2015", "Unabhängiges Gremium entscheidet bald über 'Acceptable Ads' bei Adblock Plus", "2015-09-30-AAIndependentBoard_DE.pdf"),
+  ("September 29, 2015", "4:0 für das Selbstbestimmungsrecht des Nutzers! Adblock Plus gewinnt Klage gegen Axel Springer vor Kölner Landgericht", "2015-09-29-CologneLawsuit-DE.pdf"),
+  ("September 10, 2015", "Adblock Browser aus dem Exil entlassen - endlich zurück im Google Play Store!", "2015-09-10-Adblock_Browser_für_Android-DE.pdf"),
+  ("September 08, 2015", "Adblock Plus schneller dran als Apple - Adblock Browser kommt noch vor iOS 9!", "2015-09-08-Adblock_Browser_für_iOS_Launch-DE.pdf"),
+  ("September 08, 2015", "Adblock Browser aus dem Exil entlassen - endlich zurück im Google Play Store!", "2015-09-08-Adblock_Browser_für_Android-DE.pdf"),
+  ("July 03, 2015", "Universität testet Adblock Plus auf Unternehmensnetzwerk und reduziert den Datenverbrauch damit um 40%", "2015-07-03-SFU_Press_Release-DE.pdf"),
+  ("May 19, 2015", "Werbeblocker 'Adblock Plus' launcht eigenen Android-Browser", "2015-05-19-AdblockBrowserpressrelease-DE.pdf"),
+  ("February 02, 2015", "Maxthon und AdblockPlus schließen strategische Partnerschaft zum Launch des ersten Browsers, der Werbung standardmäßig blockiert", "2015-02-09-MaxthonPressRelease-DE.pdf"),
+  ("April 04, 2014", "Erstaunliche neue Studie zur Werbewirkung: Dezente Anzeigen funktionieren besser", "2014-04-29-Eyetrackingtranslatedplusblog.pdf"),
+  ("June 06, 2013", "Neue Studie zu Werbung im Netz: Kinder von Online­Anzeigen oftmals überfordert", "2013-06-20_KinderOnline-Werbung-DE.pdf"),
+] %}
+
+<p>
+  <a href="#english">English</a>
+</p>
+<p>
+  <a href="#german">German</a>
+</p>
+
+<h3 id="english">English</h3>

[Thomas Greiner, 2015/12/14 12:56:58]

What about creating a macro for that instead of repeating the same block per
language?

e.g.
{% macro list_releases(list_lang, list_name) %}
<h3 id="{{list_lang}}">{{list_name}}</h3>
<ul>
{% for lang, date, title, file in releases %}
{% if lang == list_lang %}
  <li>
    <div>{{date}}</div>
    <a href="/press/releases/{{list_lang}}/{{file}}">{{title}}</a>
  </li>
{% endif %}
{% endfor %}
</ul>
{% endmacro %}

{{list_releases("en", "English")}}

{{list_releases("de", "German")}}

[saroyanm, 2015/12/14 16:30:06]

I think in that case also create dynamically the reference part. Done.

+<ul>
+  {% for date, title, file in releases_en %}
+    <li>
+      <div>{{date}}</div><a href="/press/releases/en/{{file}}">{{title}}</a>

[Thomas Greiner, 2015/12/14 12:56:58]

Detail: Anything against putting each tag here in its own line? That'd make it
look a bit cleaner.

[saroyanm, 2015/12/14 16:30:07]

Done.

+    </li>
+  {% endfor %}
+</ul>
+
+<h3 id="german">German</h3>
+<ul>
+{% for date, title, file in releases_de %}
+  <li>
+    <div>{{date}}</div><a href="/press/releases/de/{{file}}">{{title}}</a>
+  </li>
+{% endfor %}
+</ul>