git.iko.soy/hakyll
on master help sign in
Cabal changes.
commit9b3babe142e36e96d2ffcbf2ec5b22346c54c3d9 authorJasper Van der Jeugt <jaspervdj@gmail.com> dateFri 4 Dec 2009, 13:20 (17 years ago) parentcd90c29
4 files changed+41−5
compare with master
unifiedsplit
LICENSE+31 README.markdown+5−5 Setup.hs+2 hakyll.cabal+3
LICENSEnew file+31
@@ -0,0 +1,31 @@
1+Copyright (c) 2009, Jasper Van der Jeugt
2+ 
3+All rights reserved.
4+ 
5+Redistribution and use in source and binary forms, with or without
6+modification, are permitted provided that the following conditions are
7+met:
8+ 
9+    * Redistributions of source code must retain the above copyright
10+      notice, this list of conditions and the following disclaimer.
11+ 
12+    * Redistributions in binary form must reproduce the above
13+      copyright notice, this list of conditions and the following
14+      disclaimer in the documentation and/or other materials provided
15+      with the distribution.
16+ 
17+    * Neither the name of Jasper Van der Jeugt nor the names of other
18+      contributors may be used to endorse or promote products derived
19+      from this software without specific prior written permission.
20+ 
21+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
22+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
23+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
24+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
25+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
26+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
27+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
28+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
29+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
30+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
31+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
README.markdown+5−5
@@ -37,9 +37,9 @@ recursively.
3737
3838## Pages
3939
40−Pages can be written in html or markdown (altough it would be a trivial task
41−to add anything pandoc supports, just ask me if you want anything to be added).
42−They can also contain metadata, which are always key-value mappings.
40+Pages can be written in html, markdown, LaTeX, and basically anything
41+pandoc supports. They can also contain metadata, which are always key-value
42+mappings.
4343
4444 ---
4545 author: Jasper Van der Jeugt
@@ -57,8 +57,8 @@ They can also contain metadata, which are always key-value mappings.
5757Metadata is always placed in the beginning of a file, and is delimited by a
5858`---` string. The metadata can only contain simple key-value pairs. We can
5959now read in this page using the `Text.Hakyll.Page.readPage` function. This
60−will return a `Page`, which is actually just a `Map String String`. In this
61−example, the map would consist of the following key-value pairs:
60+will return a `Page`, which is actually just a `Map String ByteString`. In
61+this example, the map would consist of the following key-value pairs:
6262
6363- `author`: `Jasper Van der Jeugt`
6464- `title`: `A sample markdown post`
Setup.hsnew file+2
@@ -0,0 +1,2 @@
1+import Distribution.Simple
2+main = defaultMain
hakyll.cabal+3
@@ -7,6 +7,9 @@ Description:
77 blogs.
88Author: Jasper Van der Jeugt
99Maintainer: jaspervdj@gmail.com
10+License: BSD3
11+License-File: LICENSE
12+Category: Text
1013Cabal-Version: >= 1.2
1114
1215build-type: Simple