Rewrite and hopefully improve upon a big chunk of the site

5 files changed, 185 insertions, 162 deletions

diff --git a/site/projects/dlmenu.inc b/site/projects/dlmenu.inc
index 618d3ad..1025c61 100644
--- a/site/projects/dlmenu.inc
+++ b/site/projects/dlmenu.inc
@@ -1,4 +1,4 @@
 # -*- mode: org -*-
-@<div class="dlmenu">
-[[src][Browse Source]] || [[tar_gz][Download tar.gz]] || [[zip][Download zip]]
-@</div>
+- [[src][Browse Source]]
+- [[tar_gz][Download tar.gz]]
+- [[zip][Download zip]]
diff --git a/site/projects/eye-on-manga.org b/site/projects/eye-on-manga.org
index e7c52de..6bb7b98 100644
--- a/site/projects/eye-on-manga.org
+++ b/site/projects/eye-on-manga.org
@@ -1,12 +1,20 @@
 #+TITLE: eye-on-manga
 #+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
 #+LINK_UP: ../index.html
-#+LINK_HOME: ../index.html
+#+LINK_HOME: http://ryuslash.org
 #+LINK: src    https://github.com/ryuslash/eye-on-manga
 #+LINK: tar_gz https://github.com/ryuslash/eye-on-manga/tarball/master
 #+LINK: zip    https://github.com/ryuslash/eye-on-manga/zipball/master
+#+STARTUP: showall
+
+#+begin_html
+  <script src="/keyjs.js" type="text/javascript"></script>
+  <script type="text/javascript">
+    keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
+                       "h": [ "keyjs_goto", "http://ryuslash.org" ] });
+  </script>
+#+end_html
 
-#+INCLUDE: "../header.org" :lines "1-4"
 #+INCLUDE: "dlmenu.inc"
 
 * About
@@ -14,20 +22,6 @@
   ~eye-on-manga~ is a manga collection management application for the
   Nokia N900.
 
-** Why
-
-   I was always either standing in the shop, or at the
-   F.A.C.T.S. event, looking at and for manga, and I'd completely
-   forget which ones I needed to get and which ones I'd already read.
-
-** How
-
-   ~eye-on-manga~ is a simple application for the N900, it keeps a
-   list of manga in a SQLite database and makes it possible to edit
-   this data through a UI. You can tell it how many volumes a manga
-   should have and then it makes it easy to select which ones you've
-   aquired and which ones you've read.
-
 ** Features
 
    - Create a list of manga.
@@ -35,4 +29,19 @@
    - Edit wrongfully entered entries.
    - Easily mark a volume as acquired or read.
 
-#+INCLUDE: "../header.org" :lines "5-8"
+** Requirements
+
+   - A Nokia N900 with fairly recent packages should be fine.
+
+* Usage
+
+  When you start it up you will see a list of your manga, showing the
+  name, # acquired and # total. To add a new manga entry open the menu
+  by pressing on the application's title and click "New Manga". You
+  will then be prompted for the name and total number of books for
+  this manga.
+
+  If you press on one of the manga's names you will see its detail
+  view. Here you can change the information previously entered and
+  select the manga you'v acquired (left column) and the manga you've
+  read (right column).
diff --git a/site/projects/git-auto-commit-mode.org b/site/projects/git-auto-commit-mode.org
index 3542217..c7b0b99 100644
--- a/site/projects/git-auto-commit-mode.org
+++ b/site/projects/git-auto-commit-mode.org
@@ -1,90 +1,100 @@
 #+TITLE: git-auto-commit-mode
 #+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
 #+LINK_UP: ../index.html
-#+LINK_HOME: ../index.html
+#+LINK_HOME: http://ryuslash.org
 #+LINK: src    https://github.com/ryuslash/git-auto-commit-mode
 #+LINK: tar_gz https://github.com/ryuslash/git-auto-commit-mode/tarball/master
 #+LINK: zip    https://github.com/ryuslash/git-auto-commit-mode/zipball/master
+#+STARTUP: showall
+
+#+begin_html
+  <script src="/keyjs.js" type="text/javascript"></script>
+  <script type="text/javascript">
+    keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
+                       "h": [ "keyjs_goto", "http://ryuslash.org" ] });
+  </script>
+#+end_html
 
-#+INCLUDE: "../header.org" :lines "1-4"
 #+INCLUDE: "dlmenu.inc"
 
 * About
 
-  ~git-auto-commit-mode~ is a minor mode for GNU Emacs[fn::
-  http://gnu.org/software/emacs/] that, when enabled, adds and commits
-  a file after every save.
-
-** Why
+  ~git-auto-commit-mode~ is a minor mode for GNU
+  Emacs[fn::http://gnu.org/software/emacs/] that, when enabled, tries
+  to commit changes to a file after every save.  It can also try to
+  push to the default upstream.
 
-   I thought of it when I was editing my configuration files. Most of
-   my changes in my configuration files are fairly simple and I would
-   like them immediately committed, I don't want to have to sift
-   through all the changes at a later point to figure out what I want
-   to commit when.
-
-** How
+** Features
 
-   ~git-auto-commit-mode~ blindly calls
+   - Automatically commit changes to a file after each save.
 
-   #+BEGIN_SRC bash
-   git add FILE
-   git commit -m "RELATIVE-FILE-PATH"
-   #+END_SRC
+     - The commit message will contain the file name relative to the
+       repository root.
 
-   setting up the git repository correctly is the responsibility of
-   the user.
+   - Optionally, automatically push commits to the default upstream.
 
-** Features
+** Requirements
 
-   ~git-auto-commit-mode~ only really has one feature:
+   These should be mostly obvious.
 
-   - Automatically commit file to current git repository after saving.
+   - [[http://gnu.org/software/emacs][GNU Emacs]]
+   - [[http://git-scm.com][git]]
 
 * Usage
 
   To be able to use it you need to put it somewhere in your
   ~load-path~ and load it, for example:
 
-  #+NAME: .emacs.d
-  #+BEGIN_SRC emacs-lisp
-  (add-to-list 'load-path "~/path/to/git-auto-commit-mode.el")
-  (autoload 'git-auto-commit-mode "git-auto-commit-mode")
-  #+END_SRC
+  #+begin_src emacs-lisp
+    (add-to-list 'load-path "~/path/to/git-auto-commit-mode.el")
+    (auto load 'git-auto-commit-mode "git-auto-commit-mode")
+  #+end_src
+
+** Automatically commit
+
+   There are a few ways this could be used:
+
+*** As file-local variable
 
-  There are a few ways this could be used:
+    This is the way I use it and I wanted to use it.  Any file that you
+    would like to have automatically committed upon saving gets this
+    prop-line:
 
-** As file-local variable
+    #+BEGIN_SRC emacs-lisp
+      ;; -*- eval: (git-auto-commit-mode 1) -*-
+    #+END_SRC
 
-   This is the way I use it and I wanted to use it. Any file that you
-   would like to have automatically committed upon saving gets this
-   prop-line:
+    Or, if you're in anything older than emacs 24:
 
-   #+BEGIN_SRC emacs-lisp
-   ;; -*- eval: (git-auto-commit-mode 1) -*-
-   #+END_SRC
+    #+BEGIN_SRC emacs-lisp
+      ;; -*- mode: git-auto-commit -*-
+    #+END_SRC
 
-   Or, if you're in anything older than emacs 24:
+*** As a directory-local variable
 
-   #+BEGIN_SRC emacs-lisp
-   ;; -*- mode: git-auto-commit -*-
-   #+END_SRC
+    Put the following in a ~.dir-locals.el~ file in any directory where
+    you want to enable ~git-auto-commit-mode~ for *all* files:
 
-** As a directory-local variable
+    #+BEGIN_SRC emacs-lisp
+      ((nil . ((git-auto-commit-mode . t))))
+    #+END_SRC
 
-   Put the following in a ~.dir-locals.el~ file in any directory where
-   you want to enable ~git-auto-commit-mode~ for *all* files:
+*** As a hook
 
-   #+BEGIN_SRC emacs-lisp
-   ((nil . ((git-auto-commit-mode . t))))
-   #+END_SRC
+    I doubt this will ever really be useful, but it is possible:
 
-** As a hook
+    #+BEGIN_SRC emacs-lisp
+      (add-hook 'some-hook 'git-auto-commit-mode)
+    #+END_SRC
 
-   I doubt this will ever really be useful, but it is possible:
+** Automatically push
 
-   #+BEGIN_SRC emacs-lisp
-   (add-hook 'some-hook 'git-auto-commit-mode)
-   #+END_SRC
+   If you wish to push your changes each time the file is saved you
+   should set =gac-automatically-push-p= to =t=.  This is a buffer local
+   variable, so you will have to put it in your dir-local or
+   file-local variables.  Alternatively, if you're sure you can also
+   set the default value to =t=, like so:
 
-#+INCLUDE: "../header.org" :lines "5-8"
+   #+begin_src emacs-lisp
+     (setq-default gac-automatically-push-p t)
+   #+end_src
diff --git a/site/projects/org-blog.org b/site/projects/org-blog.org
index 251e877..989593b 100644
--- a/site/projects/org-blog.org
+++ b/site/projects/org-blog.org
@@ -1,11 +1,19 @@
 #+TITLE: git-auto-commit-mode
 #+LINK_UP: ../index.html
-#+LINK_HOME: ../index.html
+#+LINK_HOME: http://ryuslash.org
 #+LINK: src    https://github.com/ryuslash/org-blog
 #+LINK: tar_gz https://github.com/ryuslash/org-blog/tarball/master
 #+LINK: zip    https://github.com/ryuslash/org-blog/zipball/master
+#+STARTUP: showall
+
+#+begin_html
+  <script src="/keyjs.KS" type="text/javascript"></script>
+  <script type="text/javascript">
+    keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
+                       "h": [ "keyjs_goto", "http://ryuslash.org" ] });
+  </script>
+#+end_html
 
-#+INCLUDE: "../header.org" :lines "1-4"
 #+INCLUDE: "dlmenu.inc"
 
 * About
@@ -16,68 +24,80 @@
   viable/acceptable pure-org solution for me, so I'm trying to revive
   it.
 
-** Why
-
-   As stated, it seemed to be out-of-date and packages like [[http://renard.github.com/o-blog/][o-blog]] and
-   [[http://www.emacswiki.org/emacs/Blorg][blorg]] didn't work for me, and many others require some external
-   tool to work.
-
-* Setup
-
-  Since I've adapted it to work as a normal publishing function for
-  org, setting it up is a lot like any other publishing project as
-  well:
-
-  #+BEGIN_SRC emacs-lisp
-  (setq org-publish-project-alist
-      '(("myblog"
-         :base-directory "~/location/to/org/files/"
-         :publishing-directory "/place/to/export/to/"
-         :base-extension "org"
-         :publishing-function org-publish-org-to-blog
-         :blog-title "some title"
-         :blog-description "some description"
-         :blog-export-rss t
-         :index-title "oni blog"
-         :recursive nil
-         :table-of-contents nil)))
-   #+END_SRC
+** Features
+
+   - Pure ~org-mode~, all you need is some setup and you can use it like
+     any other exporting function.
+   - Separate drafts from posts.
+   - Generate an index of posts.
+   - Rudimentary RSS support.
+
+** Requirements
+
+   - GNU Emacs
+     - ~org-mode~
+
+* Usage
 
-  Most of these options are very normal project settings and can be
-  read about in the documentation for the variable
-  ~org-publish-project-alist~. The ~blog-title~, ~blog-description~,
-  ~blog-export-rss~ and ~index-title~, however, are used by
-  ~org-blog~.
+** Setup
 
-  - ~blog-title~
+   Since I've adapted it to work as a normal publishing function for
+   org, setting it up is a lot like any other publishing project:
 
-    This setting is used when exporting RSS. It sets the ~title~ in
-    the XML output.
+   #+BEGIN_SRC emacs-lisp
+     (setq org-publish-project-alist
+         '(("my-blog"
+            :base-directory "~/location/to/org/files/"
+            :publishing-directory "/place/to/export/to/"
+            :base-extension "org"
+            :publishing-function org-publish-org-to-blog
+            :blog-title "some title"
+            :blog-description "some description"
+            :blog-export-rss t
+            :index-title "oni blog"
+            :recursive nil
+            :table-of-contents nil)))
+    #+END_SRC
 
-  - ~blog-description~
+   Most of these options are very normal project settings and can be
+   read about in the documentation for the variable
+   ~org-publish-project-alist~. The ~blog-title~, ~blog-description~,
+   ~blog-export-rss~ and ~index-title~, however, are used by ~org-blog~.
 
-    This setting is also used when exporting RSS. It sets the
-    ~description~ in the XML output.
+   - ~blog-title~ :: This setting is used when exporting RSS. It sets the
+                   ~title~ in the XML output.
 
-  - ~blog-export-rss~
+   - ~blog-description~ :: This setting is also used when exporting
+        RSS. It sets the ~description~ in the XML output.
+
+   - ~blog-export-rss~ :: Whether or not you would like an RSS feed to be
+        exported.
+
+   - ~index-title~ :: This is used as the title of the blog's index page.
+
+   Apart from these there are also 2 other settings that need your
+   attention:
+
+   #+BEGIN_SRC emacs-lisp
+     (setq org-blog-directory "~/path/to/blog/org/files/")
+     (setq org-blog-unfinished-directory "~/path/to/drafts/")
+   #+END_SRC
 
-    Whether or not you would like an RSS feed to be exported.
+   These don't have any relevance to the exporting and publishing
+   functions, but they're used by the ~org-blog-new-post~ and
+   ~org-blog-finish-post~ functions, which help with creating new posts.
 
-  - ~index-title~
+** Create new post
 
-    This is used as the title of the blog's index page.
+   To create a new post, just call =M-x org-blog-new-post= and start
+   writing.
 
-  Apart from these there are also 2 other settings that need your
-  attention:
+** Finish a post
 
-  #+BEGIN_SRC emacs-lisp
-  (setq org-blog-directory "~/path/to/blog/org/files/")
-  (setq org-blog-unfinished-directory "~/path/to/drafts/")
-  #+END_SRC
+   When you're done writing and would like to set it up to be
+   published, just call =M-x org-blog-finish-post=.
 
-  These don't have any relevance to the exporting and publishing
-  functions, but they're used by the ~org-blog-new-post~ and
-  ~org-blog-finish-post~ functions, which help with creating new
-  posts.
+** Publish
 
-#+INCLUDE: "../header.org" :lines "5-8"
+   To publish just use any of the ~org-publish-*~ functions as you would
+   any other org site.
diff --git a/site/projects/ryuslash.org b/site/projects/ryuslash.org
index ccc6475..cfce357 100644
--- a/site/projects/ryuslash.org
+++ b/site/projects/ryuslash.org
@@ -1,7 +1,7 @@
 #+TITLE: ryuslash.org
 #+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
 #+LINK_UP: ../index.html
-#+LINK_HOME: ../index.html
+#+LINK_HOME: http://ryuslash.org
 #+LINK: python     http://www.python.org
 #+LINK: django     http://djangoproject.com
 #+LINK: feedparser http://code.google.com/p/feedparser/
@@ -10,40 +10,26 @@
 #+LINK: src        https://github.com/ryuslash/ryuslash.org
 #+LINK: tar_gz     https://github.com/ryuslash/ryuslash.org/tarball/master
 #+LINK: zip        https://github.com/ryuslash/ryuslash.org/zipball/master
+#+STARTUP: showall
+
+#+begin_html
+  <script src="/keyjs.js" type="text/javascript"></script>
+  <script type="text/javascript">
+    keyjs_initialize({ "u": [ "keyjs_goto", "../index.html" ],
+                       "h": [ "keyjs_goto", "http://ryuslash.org" ] });
+  </script>
+#+end_html
 
-#+INCLUDE: "../header.org" :lines "1-4"
 #+INCLUDE: "dlmenu.inc"
 
 * About
-  :PROPERTIES:
-  :hosted_at: github
-  :END:
 
-  ~ryuslash.org~ is the project of the front page of [[http://ryuslash.org][my website]]. I
-  have noticed, though, that apart from the /design/ and the initial
-  data[fn:: The configured feeds], there is nothing really specific to
-  my about this project.
+  ~ryuslash.org~ is the project of the [[http://ryuslash.org][front page]] of my website. I have
+  noticed, though, that apart from the /design/ and the initial data,
+  there is nothing really specific to my about this project.
 
   Right now all it really does is show a bunch of feeds on a page.
 
-** Why
-
-   I've been trying out different kinds of ways to manage/run a
-   website/blog for a long time now, and I can't seem to keep using
-   just one thing. This annoys me.
-
-   With ~ryuslash.org~ I'm trying it in a different way, gather
-   everything I do elsewhere and present it in a single place. I
-   *must* be generating content /somewhere/, and if that's true, and
-   friends or other interested people might want to know about this,
-   then it's nice to have it all in one place.
-
-** How
-
-   ~ryuslash.org~ uses the [[python][Python]] web framework [[django][django]] and the [[python][Python]]
-   module [[feedparser][feedparser]]. It uses a management command ~loadfeeds~ to go
-   through all the configured feeds and check them for new items.
-
 ** Features
 
    - Define multiple RSS feeds to load news items from.
@@ -62,14 +48,12 @@
    - [[feedparser][Feedparser]] 5.1.1
    - [[markdown][Markdown]] 2.1.1
 
-* Installation
+* Usage
 
-  Must write...
+  It is a normal django application, so normal django deployment
+  methods should work.
 
-* Configuration
+** Configuration
 
-  The feeds that are loaded are defined in the database, through the
-  ~Feed~ model. Now when you want to run your own instance, it might
-  be preferable *not* to load my feeds, so you should remove (part of)
-  or change ~aggregator/fixtures/initial_data.json~, otherwise your
-  feeds will be overwritten by my feeds every time you migrate.
+   The feeds that are loaded are defined in ~local_settings.py~. An
+   example of how to do this is located in ~local_settings.py.example~.