3author: Jasper Van der Jeugt
9If you followed along with the previous tutorial, you should now have the
10example site up and running. By running `./site build`, you created two
13- `_site`, with your site as HTML files, ready to be deployed;
14- `_cache`, which Hakyll uses internally.
16`./site clean` removes these directories, and `./site rebuild` performs a
17`clean` and then a `build`.
19In general, it's only necessary to use `rebuild` when you made changes to your
20`site.hs`, and not when you just made changes to the contents of your website.
22At this point, feel free to change some files, `./site build` and see what
28You might've noticed that the markdown pages all start with a block:
36This is entirely optional, but useful for providing extra information
37("metadata") about items. All items can have metadata: since it's not really
38convenient to add such a header to an image, you can also do this using a
41For a file called `images/foo.png`, you can add an `images/foo.png.metadata`
44 title: An image of a cow
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list