remove obsolete blog controller

[i3/i3.github.io] / i3lock / index.html.mako

diff --git a/i3lock/index.html.mako b/i3lock/index.html.mako
index 1a4a265f8bf272140828d7f3df08719d8e323b83..e324ea36ad64c01bbfb68f9bfcb38783c76cf21a 100644 (file)
--- a/i3lock/index.html.mako
+++ b/i3lock/index.html.mako
@@ -4,7 +4,7 @@
 <%inherit file="_templates/i3.mako" />
 <div id="content">
 
-<h1>i3lock — improved screen locker</h1>
+<h1>i3lock</h1>
 
 <p>
   i3lock is a simple screen locker like slock. After starting it, you will see
@@ -36,6 +36,30 @@
 <h2>Releases</h2>
 
 <ul>
+  <li>
+    <a href="/i3lock/i3lock-2.5.tar.bz2">i3lock-2.5.tar.bz2</a> (2013-06-09,
+    <a href="/i3lock/i3lock-2.5.tar.bz2.asc">GPG signature</a>)
+  </li>
+  <li>
+    <a href="/i3lock/i3lock-2.4.1.tar.bz2">i3lock-2.4.1.tar.bz2</a> (2012-06-02,
+    <a href="/i3lock/i3lock-2.4.1.tar.bz2.asc">GPG signature</a>)
+  </li>
+  <li>
+    <a href="/i3lock/i3lock-2.4.tar.bz2">i3lock-2.4.tar.bz2</a> (2012-04-01,
+    <a href="/i3lock/i3lock-2.4.tar.bz2.asc">GPG signature</a>)
+  </li>
+  <li>
+    <a href="/i3lock/i3lock-2.3.1.tar.bz2">i3lock-2.3.1.tar.bz2</a> (2012-03-15,
+    <a href="/i3lock/i3lock-2.3.1.tar.bz2.asc">GPG signature</a>)
+  </li>
+  <li>
+    <a href="/i3lock/i3lock-2.3.tar.bz2">i3lock-2.3.tar.bz2</a> (2012-03-15,
+    <a href="/i3lock/i3lock-2.3.tar.bz2.asc">GPG signature</a>)
+  </li>
+  <li>
+    <a href="/i3lock/i3lock-2.2.tar.bz2">i3lock-2.2.tar.bz2</a> (2011-11-06,
+    <a href="/i3lock/i3lock-2.2.tar.bz2.asc">GPG signature</a>)
+  </li>
   <li>
     <a href="/i3lock/i3lock-2.1.tar.gz">i3lock-2.1.tar.gz</a> (2011-03-13,
     <a href="/i3lock/i3lock-2.1.tar.gz.asc">GPG signature</a>)
@@ -52,8 +76,8 @@
 <h2>Development</h2>
 
 <p>
-  i3lock is currently developed at <a href="http://code.stapelberg.de/git/i3lock" title="cgit">
-  http://code.stapelberg.de/git/i3lock</a>. Checkouts of the master branch are intended to
+  i3lock is currently developed at <a href="http://code.i3wm.org/i3lock" title="cgit">
+  http://code.i3wm.org/i3lock</a>. Checkouts of the master branch are intended to
   be stable and working all the time. Integration of new features happens in a separate branch.
 </p>