diff options
| -rw-r--r-- | examples/hakyll/tutorials/part01.markdown | 4 | ||||
| -rw-r--r-- | examples/hakyll/tutorials/part02.markdown | 8 |
2 files changed, 10 insertions, 2 deletions
diff --git a/examples/hakyll/tutorials/part01.markdown b/examples/hakyll/tutorials/part01.markdown index 0d69938..cf48f20 100644 --- a/examples/hakyll/tutorials/part01.markdown +++ b/examples/hakyll/tutorials/part01.markdown @@ -60,7 +60,7 @@ main = hakyll "http://example.com" $ do liftIO $ putStrLn "I'm in your computer, generating your site!" ~~~~~ -Note how we wrap everyting in the `hakyll` function. This is useful because +Note how we wrap everything in the `hakyll` function. This is useful because it will generate a very nice main function. We also pass the full site URL to the `hakyll` function. If you don't have an URL for your site yet, it doesn't really matter for now; just fill in anything then. The URL is only used for @@ -83,7 +83,7 @@ One way to write such a `Context`, is a page. Another important concept in Hakyll is pages. Pages are text files that can be written in markdown, html, rst... basically anything Pandoc supports. Furthermore, they can also contain some metadata. The metadata is placed in the -file header and surrouded by `---` lines. Each line should contain a +file header and surrounded by `---` lines. Each line should contain a `key: value` pair. Let's have a look at the `index.markdown` page. --- diff --git a/examples/hakyll/tutorials/part02.markdown b/examples/hakyll/tutorials/part02.markdown index 8fdbc78..f8681a7 100644 --- a/examples/hakyll/tutorials/part02.markdown +++ b/examples/hakyll/tutorials/part02.markdown @@ -76,8 +76,16 @@ our functions when it is really needed. In this particular case, `test` would only be executed if either `test.markdown` or `template.html` were recently changed. +## So what's renderChain then? + +Now, we have done pretty much the same as we did with the `renderChain` function +in the first part. That's right, the `renderChain` is more or less implemented +like this. So, you will probably use `renderChain` in most cases, but it's +handy if you know how it works. + ## The gist of it - Arrows really aren't complicated. - Compose them using `>>>`. - `HakyllAction` tracks dependencies for you. Use it. +- In most cases, you will just use `renderChain`. |