summaryrefslogtreecommitdiff
path: root/web/philosophy.markdown
diff options
context:
space:
mode:
authorJasper Van der Jeugt <jaspervdj@gmail.com>2011-06-13 18:26:04 +0200
committerJasper Van der Jeugt <jaspervdj@gmail.com>2011-06-13 18:26:04 +0200
commitefab53729d95cc69a8205bb691db9c12e9e06096 (patch)
tree30def121f2d7907ffa8e7ebbdca7b213fc8b3016 /web/philosophy.markdown
parentea694663e1e2ed2781001996c0a2cc2c2e5fdbbb (diff)
downloadhakyll-efab53729d95cc69a8205bb691db9c12e9e06096.tar.gz
Update website a bit
Diffstat (limited to 'web/philosophy.markdown')
-rw-r--r--web/philosophy.markdown8
1 files changed, 4 insertions, 4 deletions
diff --git a/web/philosophy.markdown b/web/philosophy.markdown
index 07a20c3..056472b 100644
--- a/web/philosophy.markdown
+++ b/web/philosophy.markdown
@@ -2,25 +2,25 @@
title: Philosophy
---
-## Small-to-medium sites
+# Small-to-medium sites
Hakyll was written to be used for small-to-medium sites. You can do some
advanced things with it, but don't use it to build a big online shop.
-## Hakyll.hs
+# Hakyll.hs
It should be possible to put all configuration in one file, so data and
configuration can be strictly separated. In addition, we think this file should
never exceed a 100 lines of code.
-## High-level
+# High-level
Hakyll tries to provide as many high-level functions as possible for common
tasks, while the lower-level functions should also be accessible. If you think
you're writing something that can be used for many sites, please send a patch,
or your `hakyll.hs`, and we will see what we can do.
-## Well-documented
+# Well-documented
A key to being easy-to-use is documentation. That's why we try to provide as
many working examples as possible. If you ever create a site using hakyll,