Skip to content
Newer
Older
100644 507 lines (372 sloc) 18 KB
45a9c7f @jgm Reformatted README using standard markdown.
authored
1 Gitit
2 =====
89725fd @jgm Initial commit.
authored
3
f8ab67e @jgm Reformatting (line lengths) of README.
authored
4 Gitit is a wiki program written in Haskell. It uses [Happstack][]
5 for the web server and [pandoc][] for markup processing. Pages and
6 uploaded files are stored in a [git][] or [darcs][] repository and may
7 be modified either by using the VCS's command-line tools or through the
8 wiki's web interface. By default, pandoc's extended version of markdown
0f4f9c6 @jgm Indicate in README that LaTeX or HTML formats can be used.
authored
9 is used as a markup language, but reStructuredText, LaTeX, or HTML
10 can also be used. Pages can be exported in a number of different
11 formats, including LaTeX, RTF, OpenOffice ODT, and MediaWiki markup.
12 Gitit can be configured to display TeX math (using [jsMath][]) and
13 highlighted source code (using [highlighting-kate][]).
89725fd @jgm Initial commit.
authored
14
f22d5c4 @jgm Changed default config to use-cache: no.
authored
15 [git]: http://git.or.cz
d9c8cd8 @jgm Modified description slightly, mentioning darcs as well as git.
authored
16 [darcs]: http://darcs.net
89725fd @jgm Initial commit.
authored
17 [pandoc]: http://johnmacfarlane.net/pandoc
fd9eed5 @jgm Changed mentions of HAppS to Happstack.
authored
18 [Happstack]: http://happstack.com
f8cd051 @jgm Updated README.
authored
19 [jsMath]: http://www.math.union.edu/~dpvc/jsMath/
f22d5c4 @jgm Changed default config to use-cache: no.
authored
20 [highlighting-kate]: http://johnmacfarlane.net/highlighting-kate/
89725fd @jgm Initial commit.
authored
21
45a9c7f @jgm Reformatted README using standard markdown.
authored
22 Getting started
23 ===============
89725fd @jgm Initial commit.
authored
24
45a9c7f @jgm Reformatted README using standard markdown.
authored
25 Compiling and installing gitit
26 ------------------------------
89725fd @jgm Initial commit.
authored
27
45a9c7f @jgm Reformatted README using standard markdown.
authored
28 You'll need the [GHC][] compiler and the [cabal-install][] tool. GHC can
98adca8 @jgm Note the GHC 6.10 requirement in README.
authored
29 be downloaded [here][]. Note that, starting with release 0.5, GHC 6.10
30 or higher is required. For [cabal-install][] on *nix, follow the [quick
45a9c7f @jgm Reformatted README using standard markdown.
authored
31 install][] instructions.
89725fd @jgm Initial commit.
authored
32
33 [GHC]: http://www.haskell.org/ghc/
34 [here]: http://www.haskell.org/ghc/
35 [cabal-install]: http://hackage.haskell.org/trac/hackage/wiki/CabalInstall
36 [quick install]: http://hackage.haskell.org/trac/hackage/wiki/CabalInstall#Quick Installation on Unix
37
97e0043 Improved README.
John MacFarlane authored
38 Once you've got cabal-install, installing gitit is trivial:
89725fd @jgm Initial commit.
authored
39
a7c11fe @jgm Simplified installation instructions.
authored
40 cabal update
89725fd @jgm Initial commit.
authored
41 cabal install gitit
42
a7c11fe @jgm Simplified installation instructions.
authored
43 These commands will install the latest released version of gitit.
89725fd @jgm Initial commit.
authored
44 To install a version of gitit checked out from the repository,
45 change to the gitit directory and type:
46
47 cabal install
48
49 The `cabal` tool will automatically install all of the required haskell
50 libraries. If all goes well, by the end of this process, the latest
51 release of gitit will be installed in your local `.cabal` directory. You
52 can check this by trying:
53
54 gitit --version
55
56 If that doesn't work, check to see that `gitit` is in your local
57 cabal-install executable directory (usually `~/.cabal/bin`). And make
58 sure `~/.cabal/bin` is in your system path.
59
97e0043 Improved README.
John MacFarlane authored
60 Optional syntax highlighting support
61 ------------------------------------
62
63 If pandoc was compiled with optional syntax highlighting support,
64 this will be available in gitit too. This feature is recommended
65 if you plan to display source code on your wiki.
66
67 Highlighting support requires the [pcre][] library, so make sure that
68 is installed before continuing.
69
70 [pcre]: http://www.pcre.org/
71
72 To install gitit with highlighting support, first ensure that pandoc
73 is compiled with highlighting support, then install gitit as above:
74
75 cabal install pandoc -fhighlighting --reinstall
76 cabal install gitit
77
45a9c7f @jgm Reformatted README using standard markdown.
authored
78 Running gitit
79 -------------
89725fd @jgm Initial commit.
authored
80
97e0043 Improved README.
John MacFarlane authored
81 To run gitit, you'll need [git][] in your system path. (Or
82 [darcs][], if you're using darcs to store the wiki data.)
89725fd @jgm Initial commit.
authored
83
97e0043 Improved README.
John MacFarlane authored
84 Gitit assumes that the page files (stored in the git repository) are
85 encoded as UTF-8. Even page names may be UTF-8 if the file system
86 supports this. So you should make sure that you are using a UTF-8 locale
87 when running gitit. (To check this, type `locale`.)
73db5a1 @jgm Noted need for UTF-8 locale in README.
authored
88
f8ab67e @jgm Reformatting (line lengths) of README.
authored
89 Switch to the directory where you want to run gitit. This should be a
f1f023a @jgm Use nested templates in templates/ directory rather than template.html.
authored
90 directory where you have write access, since three directories, `static`,
91 `templates`, and `wikidata`, and two files, `gitit-users` and `gitit.log`,
92 will be created here. To start gitit, just type:
89725fd @jgm Initial commit.
authored
93
94 gitit
95
96 If all goes well, gitit will do the following:
97
98 1. Create a git repository, `wikidata`, and add a default front page.
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
99 2. Create a `static` directory containing files to be treated as
100 static files by gitit.
f1f023a @jgm Use nested templates in templates/ directory rather than template.html.
authored
101 3. Create a `templates` directory containing HStringTemplate templates
f498fc6 @jgm Use HStringTemplate template for pages.
authored
102 for wiki pages.
103 4. Start a web server on port 5001.
89725fd @jgm Initial commit.
authored
104
f8ab67e @jgm Reformatting (line lengths) of README.
authored
105 Check that it worked: open a web browser and go to
106 <http://localhost:5001>.
97e0043 Improved README.
John MacFarlane authored
107
7fa7383 @jgm Updated README with information about metadata block.
authored
108 Using gitit
109 ===========
110
97e0043 Improved README.
John MacFarlane authored
111 Wiki links and formatting
112 -------------------------
113
114 For instructions on editing pages and creating links, see the "Help" page.
115
f8ab67e @jgm Reformatting (line lengths) of README.
authored
116 Gitit interprets links with empty URLs as wikilinks. Thus, in markdown
117 pages, `[Front Page]()` creates an internal wikilink to the page `Front
118 Page`. In reStructuredText pages, `` `Front Page <>`_ `` has the same
119 effect.
89725fd @jgm Initial commit.
authored
120
c332b94 @jgm Documentation changes for new index link format.
authored
121 If you want to link to a directory listing for a subdirectory, use a
122 trailing slash: `[foo/bar/]()` creates a link to the directory for
123 `foo/bar`.
124
7fa7383 @jgm Updated README with information about metadata block.
authored
125 Page metadata
126 -------------
127
128 Pages may optionally begin with a metadata block. Here is an example:
129
38209d9 @jgm Updated README with new metadata format.
authored
130 ---
131 format: latex+lhs
132 categories: haskell math
133 toc: no
134 title: Haskell and
7fa7383 @jgm Updated README with information about metadata block.
authored
135 Category Theory
38209d9 @jgm Updated README with new metadata format.
authored
136 ...
7fa7383 @jgm Updated README with information about metadata block.
authored
137
138 \section{Why Category Theory?}
139
d89590a @jgm Don't require blank line after metadata block.
authored
140 The metadata block consists of a list of key-value pairs, each on a
141 separate line. If needed, the value can be continued on one or more
142 additional line, which must begin with a space. (This is illustrated by
143 the "title" example above.) The metadata block must begin with a line
144 `---` and end with a line `...` optionally followed by one or more blank
145 lines. (The metadata block is a valid YAML document, though not all YAML
146 documents will be valid metadata blocks.)
7fa7383 @jgm Updated README with information about metadata block.
authored
147
148 Currently the following keys are supported:
149
150 format
151 : Overrides the default page type as specified in the configuration file.
152 Possible values are `markdown`, `rst`, `latex`, `html`, `markdown+lhs`,
153 `rst+lhs`, `latex+lhs`. (Capitalization is ignored, so you can also
154 use `LaTeX`, `HTML`, etc.) The `+lhs` variants indicate that the page
155 is to be interpreted as literate Haskell. If this field is missing,
156 the default page type will be used.
157
158 categories
159 : A space or comma separated list of categories to which the page belongs.
160
161 toc
162 : Overrides default setting for table-of-contents in the configuration file.
163 Values can be `yes`, `no`, `true`, or `false` (capitalization is ignored).
164
165 title
166 : By default the displayed page title is the page name. This metadata element
167 overrides that default.
168
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
169 Highlighted source code
170 -----------------------
171
172 If gitit was compiled against a version of pandoc that has highlighting
173 support (see above), you can get highlighted source code by using
174 [delimited code blocks][]:
175
176 ~~~ {.haskell .numberLines}
177 qsort [] = []
178 qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
179 qsort (filter (>= x) xs)
180 ~~~
181
182 To see what languages are available:
183
184 pandoc -v
185
186 [delimited code blocks]: http://johnmacfarlane.net/pandoc/README.html#delimited-code-blocks
187
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
188 Configuring and customizing gitit
189 =================================
488e6bb README: Added instructions for proxying with apache.
John MacFarlane authored
190
45a9c7f @jgm Reformatted README using standard markdown.
authored
191 Configuration options
192 ---------------------
89725fd @jgm Initial commit.
authored
193
194 You can set some configuration options when starting gitit, using the
ce07825 @jgm Added data/default.conf, which defines default config file values.
authored
195 option `-f [filename]`. To get a copy of the default configuration file,
196 which you can customize, just type:
197
198 gitit --print-default-config > default.conf
199
200 The default configuration file is documented with comments throughout.
2859d1b @jgm Document --print-default-config.
authored
201
45a9c7f @jgm Reformatted README using standard markdown.
authored
202 The `static` directory
203 ----------------------
89725fd @jgm Initial commit.
authored
204
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
205 On receiving a request, gitit always looks first in the `static`
206 directory (or in whatever directory is specified for `static-dir` in
207 the configuration file). If a file corresponding to the request is
208 found there, it is served immediately. If the file is not found in
209 `static`, gitit next looks in the `static` subdirectory of gitit's data
210 file (`$CABALDIR/share/gitit-x.y.z/data`). This is where default css,
211 images, and javascripts are stored. If the file is not found there
212 either, gitit treats the request as a request for a wiki page or wiki
213 command.
214
215 So, you can throw anything you want to be served statically (for
216 example, a `robots.txt` file or `favicon.ico`) in the `static`
217 directory. You can override any of gitit's default css, javascript, or
218 image files by putting a file with the same relative path in `static`.
89725fd @jgm Initial commit.
authored
219
77d20a3 @jgm README changes: running with darcs, updated some refs to config options.
authored
220 Note: if you set `static-dir` to be a subdirectory of `repository-path`,
89e0a04 @jgm Added note about possibility of putting static inside repository.
authored
221 and then add the files in the static directory to your repository, you
222 can ensure that others who clone your wiki repository get these files
223 as well. It will not be possible to modify these files using the web
224 interface, but they will be modifiable via git.
225
77d20a3 @jgm README changes: running with darcs, updated some refs to config options.
authored
226 Using darcs instead of git
227 --------------------------
228
229 By default, gitit will store wiki pages in a git repository in the
230 `wikidata` directory. If you'd prefer to use darcs instead of git,
231 you need to add the following field to the configuration file:
232
233 repository-type: Darcs
234
235 This program may be called "darcsit" instead of "gitit" when a darcs
236 backend is used.
237
99d1199 @jgm Added comments on filestore/maxcount to darcs sec of README.
authored
238 Note: we recommend that you use gitit/darcsit with darcs version
239 2.3.0 or greater. If you must use an older version of darcs, then
240 you need to compile the filestore library without the (default)
241 maxcount flag, before (re)installing gitit:
242
243 cabal install --reinstall filestore -f-maxcount
244 cabal install --reinstall gitit
245
246 Otherwise you will get an error when you attempt to access your
247 repository.
248
45a9c7f @jgm Reformatted README using standard markdown.
authored
249 Changing the theme
250 ------------------
89725fd @jgm Initial commit.
authored
251
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
252 To change the look of the wiki, you can modify `custom.css` in
253 `static/css`.
97e0043 Improved README.
John MacFarlane authored
254
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
255 To change the look of printed pages, copy gitit's default `print.css`
256 to `static/css` and modify it.
97e0043 Improved README.
John MacFarlane authored
257
f498fc6 @jgm Use HStringTemplate template for pages.
authored
258 The logo picture can be changed by copying a new PNG file to
97e0043 Improved README.
John MacFarlane authored
259 `static/img/logo.png`.
260
d77f566 @jgm Updated README.markdown for changes to static and templates.
authored
261 To change the footer, modify `templates/footer.st`.
262
263 For more radical changes, you can override any of the default
264 templates in `$CABALDIR/share/gitit-x.y.z/templates` by copying
265 the file into `templates` and modifying it. The `page.st` template is
266 the master template; it includes the others. Interpolated variables are
267 surrounded by `$`s, so `literal $` must be backslash-escaped.
89725fd @jgm Initial commit.
authored
268
45a9c7f @jgm Reformatted README using standard markdown.
authored
269 Adding support for math
270 -----------------------
89725fd @jgm Initial commit.
authored
271
f8ab67e @jgm Reformatting (line lengths) of README.
authored
272 Gitit is designed to work with [jsMath][] to display LaTeX math in
273 HTML. Download `jsMath` and `jsMath Image Fonts` from the [jsMath
274 download page][]. You'll have two `.zip` archives. Unzip them both
275 in the `static/js` directory (a new subdirectory, `jsMath`, will be
276 created). You can test to see if math is working properly by clicking
277 "help" on the top navigation bar and looking for the math example (the
278 quadratic formula). Note that if you copied the `jsMath` directory into
279 `static` *after* starting gitit, you will have to restart gitit for the
280 change to be noticed. Gitit checks for the existence of the jsMath files
281 when it starts, and will not include links to them unless they exist.
89725fd @jgm Initial commit.
authored
282
7fa7383 @jgm Updated README with information about metadata block.
authored
283 To write math on a markdown-formatted wiki page, just enclose it
284 in dollar signs, as in LaTeX:
89725fd @jgm Initial commit.
authored
285
286 Here is a formula: $\frac{1}{\sqrt{c^2}}$
287
288 You can write display math by enclosing it in double dollar signs:
289
290 $$\frac{1}{\sqrt{c^2}}$$
291
292 [jsMath download page]: http://sourceforge.net/project/showfiles.php?group_id=172663
293
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
294 Plugins
295 =======
89725fd @jgm Initial commit.
authored
296
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
297 Plugins are small Haskell programs that transform a wiki page after it
298 has been converted from Markdown or RST. See the example plugins in the
299 `plugins` directory. To enable a plugin, include the path to the plugin
300 (or its module name) in the `plugins` field of the configuration file.
301 (If the plugin name starts with `Network.Gitit.Plugin.`, gitit will assume that
302 the plugin is an installed module and will not look for a source file.)
89725fd @jgm Initial commit.
authored
303
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
304 Plugin support is enabled by default. However, plugin support makes
305 the gitit executable considerably larger and more memory-hungry.
306 If you don't need plugins, you may want to compile gitit without plugin
307 support. To do this, unset the `plugins` Cabal flag:
89725fd @jgm Initial commit.
authored
308
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
309 cabal install --reinstall gitit -f-plugins
89725fd @jgm Initial commit.
authored
310
e9ac5c2 @jgm Make plugins flag enabled by default.
authored
311 Note also that if you compile gitit for executable profiling, attempts
312 to load plugins will result in "internal error: PAP object entered!"
89725fd @jgm Initial commit.
authored
313
77d20a3 @jgm README changes: running with darcs, updated some refs to config options.
authored
314 Accessing the wiki via git or darcs
315 ===================================
89725fd @jgm Initial commit.
authored
316
77d20a3 @jgm README changes: running with darcs, updated some refs to config options.
authored
317 All the pages and uploaded files are stored in a git or darcs
318 repository. By default, this lives in the `wikidata` directory (though
319 this can be changed through configuration options). So you can interact
320 with the wiki using git command line tools:
89725fd @jgm Initial commit.
authored
321
322 git clone ssh://my.server.edu/path/of/wiki/wikidata
323 cd wikidata
324 vim Front\ Page.page # edit the page
325 git commit -m "Added message about wiki etiquette" Front\ Page.page
326 git push
327
328 If you now look at the Front Page on the wiki, you should see your changes
329 reflected there. Note that the pages all have the extension `.page`.
330
f22d5c4 @jgm Changed default config to use-cache: no.
authored
331 Caching
332 =======
333
334 By default, gitit does not cache content. If your wiki receives a lot of
335 traffic or contains pages that are slow to render, you may want to activate
336 caching. To do this, set the configuration option `use-cache` to `yes`.
337 By default, rendered pages and highlighted source files will be cached
338 in the `cache` directory. (Another directory can be specified by setting
339 the `cache-dir` configuration option.)
340
341 Cached pages are updated when pages are modified using the web
342 interface. They are not updated when pages are modified directly through
343 git or darcs. However, the cache can be refreshed manually by pressing
344 Ctrl-R when viewing a page, or by sending an HTTP GET or POST request to
345 `/_expire/path/to/page`, where `path/to/page` is the name of the page to
346 be expired.
347
348 Users who frequently update pages using git or darcs may wish to add a
349 hook to the repository that makes the appropriate HTTP request to expire
350 pages when they are updated. To facilitate such hooks, the gitit cabal
351 package includes an executable `expireGititCache`. Assuming you are
352 running gitit at port 5001 on localhost, and the environment variable
353 `CHANGED_FILES` contains a list of the files that have changed, you can
354 expire their cached versions using
355
356 expireGititCache http://localhost:5001 $CHANGED_FILES
357
358 Or you can specify the files directly:
359
360 expireGititCache http://localhost:5001 "Front Page.page" foo/bar/baz.c
361
362 This program will return a success status (0) if the page has been
363 successfully expired (or if it was never cached in the first place),
364 and a failure status (> 0) otherwise.
365
366 The cache is persistent through restarts of gitit. To expire all cached
367 pages, simply remove the `cache` directory.
368
488e6bb README: Added instructions for proxying with apache.
John MacFarlane authored
369 Using gitit with apache
370 =======================
371
372 Most users who run a public-facing gitit will want gitit to appear
373 at a nice URL like `http://wiki.mysite.com` or
374 `http://mysite.com/wiki` rather than `http://mysite.com:5001`.
375 This can be achieved using apache's `mod_proxy`.
376
377 Proxying to `http://wiki.mysite.com`
378 ------------------------------------
379
380 Set up your DNS so that `http://wiki.mysite.com` maps to
381 your server's IP address. Make sure that the `mod_proxy` module is
382 loaded, and set up a virtual host with the following configuration:
383
384 <VirtualHost *>
385 ServerName wiki.mysite.com
386 DocumentRoot /var/www/
387 RewriteEngine On
388 ProxyPreserveHost On
389 ProxyRequests Off
390
391 <Proxy *>
392 Order deny,allow
393 Allow from all
394 </Proxy>
395
396 ProxyPassReverse / http://127.0.0.1:5001
397 RewriteRule ^(.*) http://127.0.0.1:5001$1 [P]
398
399 ErrorLog /var/log/apache2/error.log
400 LogLevel warn
401
402 CustomLog /var/log/apache2/access.log combined
403 ServerSignature On
404
405 </VirtualHost>
406
407 Reload your apache configuration and you should be all set.
408
409 Proxying to `http://mysite.com/wiki`
410 ------------------------------------
411
412 Make sure the `mod_proxy`, `mod_headers`, `mod_proxy_http`,
413 and `mod_proxy_html` modules are loaded. `mod_proxy_html`
414 is an external module, which can be obtained [here]
415 (http://apache.webthing.com/mod_proxy_html/). It rewrites URLs that
416 occur in web pages. Here we will use it to rewrite gitit's links so that
417 they all begin with `/wiki/`.
418
f8ab67e @jgm Reformatting (line lengths) of README.
authored
419 First, tell gitit not to compress pages, since `mod_proxy_html` needs
420 uncompressed pages to parse. You can do this by setting the gitit
421 configuration option
488e6bb README: Added instructions for proxying with apache.
John MacFarlane authored
422
77d20a3 @jgm README changes: running with darcs, updated some refs to config options.
authored
423 compress-responses: no
424
425 Second, modify the link in the `reset-password-message` in the
426 configuration file: instead of
427
428 http://$hostname$:$port$$resetlink$
429
430 set it to
431
432 http://$hostname$/wiki$resetlink$
488e6bb README: Added instructions for proxying with apache.
John MacFarlane authored
433
434 Restart gitit.
435
436 Now add the following lines to the apache configuration file for the
437 `mysite.com` server:
438
439 # These commands will proxy /wiki/ to port 5001
440
441 ProxyRequests Off
442
443 <Proxy *>
444 Order deny,allow
445 Allow from all
446 </Proxy>
447
448 ProxyPass /wiki/ http://127.0.0.1:5001/
449
450 <Location /wiki/>
451 SetOutputFilter proxy-html
452 ProxyPassReverse /
453 ProxyHTMLURLMap / /wiki/
454 RequestHeader unset Accept-Encoding
455 </Location>
456
457 Reload your apache configuration and you should be set.
458
459 For further information on the use of `mod_proxy_http` to rewrite URLs,
460 see the [`mod_proxy_html` guide].
461
462 [`mod_proxy_html` guide]: http://apache.webthing.com/mod_proxy_html/guide.html
463
e86d3dc @jgm Added note on using gitit as a library to README.
authored
464 Using gitit as a library
465 ========================
466
467 By importing the module `Network.Gitit`, you can include a gitit wiki
468 (or several of them) in another happstack application. There are some
469 simple examples in the haddock documentation for `Network.Gitit`.
470
45a9c7f @jgm Reformatted README using standard markdown.
authored
471 Reporting bugs
472 ==============
89725fd @jgm Initial commit.
authored
473
a49ba22 @jgm Added link to bug tracker on googlecode.
authored
474 Bugs may be reported (and feature requests filed) at
475 <http://code.google.com/p/gitit/issues/list>.
89725fd @jgm Initial commit.
authored
476
41595ee @jgm Added notice of mailing list to README.
authored
477 There is a mailing list for users and developers at
478 <http://groups.google.com/group/gitit-discuss>.
479
45a9c7f @jgm Reformatted README using standard markdown.
authored
480 Acknowledgements
481 ================
89725fd @jgm Initial commit.
authored
482
bb8abc3 @jgm Improved acknowledgements, bringing list of contributors up to date.
authored
483 A number of people have contributed patches:
484
8500b29 @jgm More contributors.
authored
485 - Gwern Branwen helped to optimize gitit and wrote the
f22d5c4 @jgm Changed default config to use-cache: no.
authored
486 InterwikiPlugin. He also helped with the Feed module.
bb8abc3 @jgm Improved acknowledgements, bringing list of contributors up to date.
authored
487 - Simon Michael contributed the patch adding RST support.
488 - Henry Laxen added support for password resets and helped with
489 the apache proxy instructions.
490 - Anton van Straaten made the process of page generation
491 more modular by adding Gitit.ContentTransformer.
058ce02 @jgm Acknowledge Robin Green's patch in README.
authored
492 - Robin Green helped improve the plugin API and interface, and
493 fixed a security problem with the reset password code.
edeca79 More acknowledgements.
John MacFarlane authored
494 - Thomas Hartman helped improve the index page, making directory
495 browsing persistent.
bb8abc3 @jgm Improved acknowledgements, bringing list of contributors up to date.
authored
496 - Justin Bogner improved the appearance of the preview button.
8500b29 @jgm More contributors.
authored
497 - Kohei Ozaki contributed the ImgTexPlugin.
cf6e15e @jgm Added acknowledgement for mightybyte.
authored
498 - mightybyte suggested making gitit available as a library,
499 and contributed a patch to ifLoggedIn that was needed to
500 make gitit usable with a custom authentication scheme.
bb8abc3 @jgm Improved acknowledgements, bringing list of contributors up to date.
authored
501
502 Gitit's default visual layout is shamelessly borrowed from Wikipedia.
5c5c337 @jgm Updated README.
authored
503 The stylesheets are influenced by Wikipedia's stylesheets and by the
504 bluetrip CSS framework (see BLUETRIP-LICENSE). Some of the icons in
505 `img/icons` come from bluetrip as well.
506
Something went wrong with that request. Please try again.