@@ -10,38 +10,19 @@ author: Jasper Van der Jeugt
1010 Saw: `Main'
1111 Expected: `Hakyll'
1212
13−Is an error encountered on Mac OS when `hakyll.hs` is located on a
14−case-insensitive filesystem. A workaround is to rename it to something that
15−isn't the name of the module, for example, `site.hs`.
13+Is an error encountered on Mac OS when your configuration is named `hakyll.hs`
14+and located on a case-insensitive filesystem. A workaround is to rename it to
15+something that isn't the name of the module, for example, `site.hs`.
1616
17−## `pageCompiler`/Hakyll/Pandoc eats my HTML!
17+## pandocCompiler/Hakyll/Pandoc eats my HTML!
1818
1919Sometimes, it can seem that HTML pages are stripped of some arbitrary tags, e.g.
20−`<div>`'s. The issue here is that, when using the default `pageCompiler`, your
20+`<div>`'s. The issue here is that, when using the default `pandocCompiler`, your
2121page passes through Pandoc. Pandoc unfortunately strips away this information,
2222giving you the "wrong" HTML.
2323
24−The solution is not to use `pageCompiler` -- it is very common to write custom
25−page processing compiler. The definition of `pageCompiler` is, put simply:
26−
27−~~~~~{.haskell}
28−pageCompiler =
29− readPageCompiler >>>
30− addDefaultFields >>> -- Sets some things like $path$
31− arr applySelf >>> -- Used to fill in $var$s in the page
32− pageRenderPandoc -- Pass through pandoc
33−~~~~~
34−
35−You can add your own version in your `hakyll.hs` file:
36−
37−~~~~~{.haskell}
38−myPageCompiler =
39− readPageCompiler >>>
40− addDefaultFields >>> -- Sets some things like $path$
41− arr applySelf -- Used to fill in $var$s in the page
42−~~~~~
43−
44−And using this instead of `pageCompiler` should solve the issue.
24+The solution is not to use `pandocCompiler`, but something simpler like
25+`getResourceBody`. This way, your HTML is not touched.
4526
4627## Does Hakyll support syntax highlighting?
4728
@@ -54,12 +35,9 @@ Pandoc syntax CSS file][syntax-css].
5435
5536## When should I rebuild and when should I build?
5637
57−If you execute a `./hakyll build`, Hakyll will build your site incrementally.
58−This means it will be very fast, but it will not pick up _all_ changes.
59−
60−- In case you edited `hakyll.hs`, you first want to compile it again.
61−- It is generally recommended to do a `./hakyll rebuild` before you deploy your
62− site.
38+If you execute a `./site build`, Hakyll will build your site incrementally.
39+However, we can not detect if you edited `site.hs`. In this case, you first want
40+to compile it again `site.hs` again, and then do a `./site rebuild`.
6341
6442After rebuilding your site, all files will look as "modified" to the filesystem.
6543This means that when you upload your site, it will usually transfer all files --