Initial commit

9 files changed, 425 insertions, 0 deletions

diff --git a/site/projects/bint.org b/site/projects/bint.org
new file mode 100644
index 0000000..e8c28af
--- /dev/null
+++ b/site/projects/bint.org
@@ -0,0 +1,18 @@
+* About
+** bint -- Bad Image Naming Tool
+   marijn_a:
+   dit is wat ik wil dat het doet
+
+   * ik selecteer een map met plaatjes erin.
+   * programma scant alle mappen in die map voor plaatjes
+   * nadat ie klar is, laat ie filepath zien en het 1ste plaatje
+   * vraagt om de naam van het plaatje
+   * ik type een naam in en druk enter
+   * volgende plaatje in beeld
+   * ik typ naam en enter
+   * etc
+
+   zie het als een image renamer
+   dus eerst heet het plaatje 35y6795634.jpg
+   dan type je in de balk: THE ALIENS INVADED!!
+   en dan renamed ie naar THE ALIENS INVADED!!.jpg
diff --git a/site/projects/clever-mode.org b/site/projects/clever-mode.org
new file mode 100644
index 0000000..f773ac2
--- /dev/null
+++ b/site/projects/clever-mode.org
@@ -0,0 +1,31 @@
+#+TITLE: clever-mode
+#+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+
+#+INCLUDE: "../header.org" :lines "1-4"
+
+* About
+
+  ~clever-mode~ is a GNU Emacs[fn:emacs:http://gnu.org/software/emacs/]
+  major mode for editing Smarty[fn:smarty:http://www.smarty.net] templates.
+
+** Why
+
+   The only modes for editing Smarty[fn:smarty] templates are either
+   outdated or need MuMaMo, and I seriously dislike MuMaMo.
+
+   Also, I have some Emacs[fn:emacs] projects now, but no major mode
+   yet, and I want to learn.
+
+** Features
+
+   ~clever-mode~ is based on HTML mode, although Smarty[fn:smarty] is
+   not limited to HTML, that is what it is used for most (at least by me).
+
+* Usage
+
+  Since it only has some syntax highlighting at the moment usage only
+  consists of getting it, installing it and enabling it.
+
+#+INCLUDE: "../header.org" :lines "5-8"
diff --git a/site/projects/dispass.el.org b/site/projects/dispass.el.org
new file mode 100644
index 0000000..b64a4ed
--- /dev/null
+++ b/site/projects/dispass.el.org
@@ -0,0 +1 @@
+#+TITLE: Dispass.el
diff --git a/site/projects/dlmenu.inc b/site/projects/dlmenu.inc
new file mode 100644
index 0000000..618d3ad
--- /dev/null
+++ b/site/projects/dlmenu.inc
@@ -0,0 +1,4 @@
+# -*- mode: org -*-
+@<div class="dlmenu">
+[[src][Browse Source]] || [[tar_gz][Download tar.gz]] || [[zip][Download zip]]
+@</div>
diff --git a/site/projects/eye-on-manga.org b/site/projects/eye-on-manga.org
new file mode 100644
index 0000000..e7c52de
--- /dev/null
+++ b/site/projects/eye-on-manga.org
@@ -0,0 +1,38 @@
+#+TITLE: eye-on-manga
+#+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+#+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
+
+#+INCLUDE: "../header.org" :lines "1-4"
+#+INCLUDE: "dlmenu.inc"
+
+* About
+
+  ~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.
+   - Keep track of which volumes have been acquired and read.
+   - Edit wrongfully entered entries.
+   - Easily mark a volume as acquired or read.
+
+#+INCLUDE: "../header.org" :lines "5-8"
diff --git a/site/projects/git-auto-commit-mode.org b/site/projects/git-auto-commit-mode.org
new file mode 100644
index 0000000..3542217
--- /dev/null
+++ b/site/projects/git-auto-commit-mode.org
@@ -0,0 +1,90 @@
+#+TITLE: git-auto-commit-mode
+#+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+#+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
+
+#+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
+
+   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
+
+   ~git-auto-commit-mode~ blindly calls
+
+   #+BEGIN_SRC bash
+   git add FILE
+   git commit -m "RELATIVE-FILE-PATH"
+   #+END_SRC
+
+   setting up the git repository correctly is the responsibility of
+   the user.
+
+** Features
+
+   ~git-auto-commit-mode~ only really has one feature:
+
+   - Automatically commit file to current git repository after saving.
+
+* 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
+
+  There are a few ways this could be used:
+
+** As file-local variable
+
+   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:
+
+   #+BEGIN_SRC emacs-lisp
+   ;; -*- eval: (git-auto-commit-mode 1) -*-
+   #+END_SRC
+
+   Or, if you're in anything older than emacs 24:
+
+   #+BEGIN_SRC emacs-lisp
+   ;; -*- mode: git-auto-commit -*-
+   #+END_SRC
+
+** As a directory-local variable
+
+   Put the following in a ~.dir-locals.el~ file in any directory where
+   you want to enable ~git-auto-commit-mode~ for *all* files:
+
+   #+BEGIN_SRC emacs-lisp
+   ((nil . ((git-auto-commit-mode . t))))
+   #+END_SRC
+
+** As a hook
+
+   I doubt this will ever really be useful, but it is possible:
+
+   #+BEGIN_SRC emacs-lisp
+   (add-hook 'some-hook 'git-auto-commit-mode)
+   #+END_SRC
+
+#+INCLUDE: "../header.org" :lines "5-8"
diff --git a/site/projects/org-blog.org b/site/projects/org-blog.org
new file mode 100644
index 0000000..251e877
--- /dev/null
+++ b/site/projects/org-blog.org
@@ -0,0 +1,83 @@
+#+TITLE: git-auto-commit-mode
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+#+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
+
+#+INCLUDE: "../header.org" :lines "1-4"
+#+INCLUDE: "dlmenu.inc"
+
+* About
+
+  ~org-blog~ is a blog exporter for ~org-mode~ written by David
+  O'Toole in 2006. ~org-mode~ has since then changed a bit and it
+  seemed that it no longer worked. It also seems to be the only
+  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
+
+  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~.
+
+  - ~blog-title~
+
+    This setting is used when exporting RSS. It sets the ~title~ in
+    the XML output.
+
+  - ~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
+
+  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.
+
+#+INCLUDE: "../header.org" :lines "5-8"
diff --git a/site/projects/org.org b/site/projects/org.org
new file mode 100644
index 0000000..c8b3adc
--- /dev/null
+++ b/site/projects/org.org
@@ -0,0 +1,85 @@
+#+TITLE: org
+#+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+#+OPTIONS: H:5
+
+* About
+
+  No I don't mean that I have anything to do with [[http://orgmode.org][org-mode]], but trying
+  to find a nice and effective structure to my org files is an ongoing
+  project for me.
+
+* Organizational
+
+** inbox.org
+
+   The ~inbox.org~ file is used as, surprise surprise, an
+   inbox. Whenever ~org-capture~ is used to create a new task,
+   appointment or note, it is placed in this file, from here it should
+   be distributed to one of the other org files.
+
+   - appointments
+
+     New appointments that should be placed in one of the other files
+     are first placed here.
+
+   - notes
+
+     New notes that should be placed in one of the other files are
+     first placed here.
+
+   - tasks
+
+     New tasks that should be placed in one of the other files are
+     first placed here.
+
+** personal.org
+
+   The ~personal.org~ file is used for private tasks, appointments and
+   notes. Not specifically actually private, just not belonging to any
+   of the other org files.
+
+   - appointments
+
+     Appointments of a personal nature, not specifically about any of
+     the other org files.
+
+   - birthdays
+
+     Birthdays of friends and family are noted here.
+
+   - bookmarks
+
+     Some very interesting links that I should keep an eye on.
+
+   - notes
+
+     Notes about personal things should be placed here.
+
+   - rss
+
+     I have a single RSS feed that I load with org, this is a feed
+     from [[http://www.myepisodes.com][MyEpisodes]] which tells me when new episodes of shows I
+     watch air.
+
+   - tasks
+
+     Tasks of a personal nature, not belonging to any of the other
+     files/categories.
+
+** contacts.org
+
+   Just keeps my contacts.
+
+** projects
+
+   Org files about projects I work on.
+
+*** any org files
+
+
+
+** work
+
+   Org files about work-related things.
diff --git a/site/projects/ryuslash.org b/site/projects/ryuslash.org
new file mode 100644
index 0000000..ccc6475
--- /dev/null
+++ b/site/projects/ryuslash.org
@@ -0,0 +1,75 @@
+#+TITLE: ryuslash.org
+#+STYLE: <link rel="stylesheet" type="text/css" href="../../stylesheet.css" />
+#+LINK_UP: ../index.html
+#+LINK_HOME: ../index.html
+#+LINK: python     http://www.python.org
+#+LINK: django     http://djangoproject.com
+#+LINK: feedparser http://code.google.com/p/feedparser/
+#+LINK: south      http://south.aeracode.org/
+#+LINK: markdown   http://packages.python.org/Markdown/
+#+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
+
+#+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.
+
+  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.
+   - Define relative paths for the xml and profile linked to a feed.
+   - Group feeds in categories.
+   - Add comments to any post that comes in.
+   - Generate feeds: One for all posts, one for all comments.
+
+** Requirements
+
+   ~ryuslash.org~ uses the following modules and applications:
+
+   - [[python][Python]] 2.6.x or 2.7.x
+   - [[django][Django]] 1.3
+   - [[south][South]] 0.7.4
+   - [[feedparser][Feedparser]] 5.1.1
+   - [[markdown][Markdown]] 2.1.1
+
+* Installation
+
+  Must write...
+
+* 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.