Rough code for initializing wikidata if it doesn't exist.

Note:  the markup help is screwed up because the HTML gets
stripped out. Redo with a grid table.

Also, we'll eventually need a wizard to create a config
directory.

Makefile

@@ -1,8 +1,11 @@
-.PHONY : all clean veryclean
+.PHONY : all clean veryclean install
 
 all:
 	cabal-dev configure && cabal-dev build
 
+install:
+	cabal-dev install
+
 prep:
 	cabal-dev install-deps
 

data/FrontPage.page

@@ -0,0 +1,12 @@
+# Welcome to Gitit!
+
+This is the front page of your new gitit wiki.  You can edit this
+page by clicking on the "edit" tab at the top of the screen.
+For instructions on how to make a link to another wiki page, see [the
+Help page](Help#wiki-links). To create a new wiki page, just create a
+link to it and follow the link.
+
+Help is always available through the "Help" link in the sidebar.
+More details on installing and configurating gitit are available
+in the [Gitit User’s Guide]().
+

data/Help.page

@@ -0,0 +1,125 @@
+# Navigating
+
+The most natural way of navigating is by clicking wiki links that
+connect one page with another. The "Front page" link in the navigation
+bar will always take you to the Front Page of the wiki. The "All pages"
+link will take you to a list of all pages on the wiki (organized into
+folders if directories are used). Alternatively, you can search using
+the search box. Note that the search is set to look for whole words, so
+if you are looking for "gremlins", type that and not "gremlin".
+The "go" box will take you directly to the page you type.
+
+# Creating and modifying pages
+
+## Registering for an account
+
+In order to modify pages, you'll need to be logged in.  To register
+for an account, just click the "register" button in the bar on top
+of the screen.  You'll be asked to choose a username and a password,
+which you can use to log in in the future by clicking the "login"
+button.  While you are logged in, these buttons are replaced by
+a "logout so-and-so" button, which you should click to log out
+when you are finished.
+
+Note that logins are persistent through session cookies, so if you
+don't log out, you'll still be logged in when you return to the
+wiki from the same browser in the future.
+
+## Editing a page
+
+To edit a page, just click the "edit" button at the bottom right corner
+of the page.
+
+You can click "Preview" at any time to see how your changes will look.
+Nothing is saved until you press "Save."
+
+Note that you must provide a description of your changes.  This is to
+make it easier for others to see how a wiki page has been changed.
+
+## Page metadata
+
+Pages may optionally begin with a metadata block.  Here is an example:
+
+    ---
+    format: latex+lhs
+    categories: haskell math
+    toc: no
+    title: Haskell and
+      Category Theory
+    ...
+
+    \section{Why Category Theory?}
+
+The metadata block consists of a list of key-value pairs, each on a
+separate line. If needed, the value can be continued on one or more
+additional line, which must begin with a space. (This is illustrated by
+the "title" example above.) The metadata block must begin with a line
+`---` and end with a line `...` optionally followed by one or more blank
+lines.
+
+Currently the following keys are supported:
+
+format
+:   Overrides the default page type as specified in the configuration file.
+    Possible values are `markdown`, `rst`, `latex`, `html`, `markdown+lhs`,
+    `rst+lhs`, `latex+lhs`.  (Capitalization is ignored, so you can also
+    use `LaTeX`, `HTML`, etc.)  The `+lhs` variants indicate that the page
+    is to be interpreted as literate Haskell.  If this field is missing,
+    the default page type will be used.
+
+categories
+:   A space or comma separated list of categories to which the page belongs.
+
+toc
+:   Overrides default setting for table-of-contents in the configuration file.
+    Values can be `yes`, `no`, `true`, or `false` (capitalization is ignored).
+
+title
+:   By default the displayed page title is the page name.  This metadata element
+    overrides that default.
+
+## Creating a new page
+
+To create a new page, just create a wiki link that links to it, and
+click the link.  If the page does not exist, you will be editing it
+immediately.
+
+## Reverting to an earlier version
+
+If you click the "history" button at the bottom of the page, you will
+get a record of previous versions of the page.  You can see the differences
+between two versions by dragging one onto the other; additions will be
+highlighted in yellow, and deletions will be crossed out with a horizontal
+line.  Clicking on the description of changes will take you to the page
+as it existed after those changes.  To revert the page to the revision
+you're currently looking at, just click the "revert" button at the bottom
+of the page, then "Save". 
+
+## Deleting a page
+
+The "delete" button at the bottom of the page will delete a page.  Note
+that deleted pages can be recovered, since a record of them will still be
+accessible via the "activity" button on the top of the page.
+
+# Uploading files
+
+To upload a file--a picture, a PDF, or some other resource--click the
+"upload" button in the navigation bar.  You will be prompted to select
+the file to upload.  As with edits, you will be asked to provide a
+description of the resource (or of the change, if you are overwriting
+an existing file).
+
+Often you may leave "Name on wiki" blank, since the existing name of the
+file will be used by default.  If that isn't desired, supply a name.
+Note that uploaded files *must* include a file extension (e.g. `.pdf`).
+
+If you are providing a new version of a file that already exists on the
+wiki, check the box "Overwrite existing file." Otherwise, leave it
+unchecked.
+
+To link to an uploaded file, just use its name in a regular wiki link.
+For example, if you uploaded a picture `fido.jpg`, you can insert the
+picture into a (markdown-formatted) page as follows: `![fido](fido.jpg)`.
+If you uploaded a PDF `projection.pdf`, you can insert a link to it
+using:  `[projection](projection.pdf)`.
+

data/markup.HTML

@@ -0,0 +1,32 @@
+# Markup
+
+The syntax for wiki pages is standard XHTML. All tags must be
+properly closed.
+
+## Wiki links
+
+Links to other wiki pages are formed this way:
+`<a href="">Page Name</a>`. (Gitit converts links with empty
+targets into wikilinks.)
+
+To link to a wiki page using something else as the link text:
+`<a href="Page+Name">something else</a>`.
+
+Note that page names may contain spaces and some special
+characters. They need not be CamelCase. CamelCase words are *not*
+automatically converted to wiki links.
+
+Wiki pages may be organized into directories. So, if you have
+several pages on wine, you may wish to organize them like so:
+
+    Wine/Pinot Noir
+    Wine/Burgundy
+    Wine/Cabernet Sauvignon
+
+Note that a wiki link `<a href="">Burgundy</a>` that occurs inside
+the `Wine` directory will link to `Wine/Burgundy`, and not to
+`Burgundy`. To link to a top-level page called `Burgundy`, you'd
+have to use `<a href="/Burgundy">Burgundy</a>`.
+
+To link to a directory listing for a subdirectory, use a trailing
+slash:  `<a href="">Wine/</a>` will link to a listing of the `Wine` subdirectory.

data/markup.LaTeX

@@ -0,0 +1,63 @@
+# Markup
+
+This wiki's pages are written in (a subset of) [LaTeX].
+
+  [LaTeX]: http://www.latex-project.org/
+
+The following commands and environments are recognized:
+
+-   `\emph{emphasis}`
+
+-   `\textbf{bold}`
+
+-   `verb!verbatim@@\#!`
+
+-   `\textsubscr{2}`
+
+-   `\sout{strikeout}`
+
+-   `\textsuperscript{2}`
+
+-   `$e = mc^2$`
+
+-   `$$e = mc^2$$`
+
+-   `\footnote{a footnote}`
+
+-   `\section{section}`, `\subsection{subsection}`, etc.
+
+-   `\begin{quote} . . . \end{quote}`
+
+-   `\begin{verbatim} . . . \end{verbatim}`
+
+-   `\begin{itemize} . . . \end{itemize}`
+
+-   `\begin{enumerate} . . . \end{enumerate}`
+
+## Wiki links
+
+Links to other wiki pages are formed this way: `\href{}{Page Name}`.
+(Gitit converts markdown links with empty targets into wikilinks.)
+
+To link to a wiki page using something else as the link text:
+`\href{Page Name}{Something else}`.
+
+Note that page names may contain spaces and some special
+characters. They need not be CamelCase. CamelCase words are *not*
+automatically converted to wiki links.
+
+Wiki pages may be organized into directories. So, if you have
+several pages on wine, you may wish to organize them like so:
+
+    Wine/Pinot Noir
+    Wine/Burgundy
+    Wine/Cabernet Sauvignon
+
+Note that a wiki link `\href{}{Burgundy}` that occurs inside the `Wine`
+directory will link to `Wine/Burgundy`, and not to `Burgundy`. To
+link to a top-level page called `Burgundy`, you'd have to use
+`\href{/Burgundy}{Burgundy}`.
+
+To link to a directory listing for a subdirectory, use a trailing
+slash:  `\href{}{Wine/}` will link to a listing of the `Wine` subdirectory.
+