blob: 1886ba16ed228039acb62850cf8431cc08f776cd (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
---
title: Using teasers in Hakyll
author: Ivan Veselov
type: article
---
## Introduction
Sometimes it is convenient to have an excerpt of a post displayed on
the index page along with a "Read more..." link to encourage your
readers to read the rest of the post.
You can do this in Hakyll by using "teasers" functionality.
## Marking teasers in posts
First, you have to put a tag in your post which separates the teaser
from the rest of the article. We use `<!--more-->` for this to mimic
the [WordPress convention](http://codex.wordpress.org/Customizing_the_Read_More):
``` markdown
---
title: My teasering post
---
In this post I'll try to explain how to use teasers.
<!--more-->
And here I am proceeding with the explanation.
```
This is an HTML comment, so it doesn't have any visual impact on the
post, it is there solely for semantic purposes.
## Referring to teasers in templates
Now, we want to refer to the teaser in the template. We can do this
pretty intuitively by using `$teaser$` key:
``` html
<li class="post_item">
$date$ - $title$
<p>Teaser: $teaser$</p>
<a href="$url$">Read more</a>
</li>
```
## Gluing together
The only thing left is to glue those things together. An important
question here is on what stage of the compilation we want to extract a
teaser. Usually, we want to use pandoc output, i.e. raw HTML without
any templates applied (since we do not want some surrounding
JavaScript or common text from the templates to be included in the
teaser). We can specify this by using snapshots: we save the snapshot
during compilation and load it to resolve `$teaser$` key later:
``` haskell
match "posts/*" $ do
route $ setExtension ".html"
compile $
pandocCompiler
-- save immediately after pandoc, but before the templates are applied
>>= saveSnapshot "content"
>>= loadAndApplyTemplate "templates/post.html" defaultContext
...
```
You can read more about snapshots in
[Snapshots tutorial](/tutorials/05-snapshots-feeds.html).
Then we use this snapshot while generating teasers using the
`teaserField` function:
``` haskell
loadAndApplyTemplate
"template/postitem.html"
(teaserField "teaser" "content" <> defaultContext)
item
```
Here, we've just added a new context which knows how to handle
`$teaser$` key to the default context (note that we passed the same
snapshot name `"content"` which we used while saving).
## Optional teasers
In case you don't add a `<!--more-->` comment, `$teaser$` will not be defined.
This means you can use something like:
```html
$if(teaser)$
$teaser$
$else$
$body$
$endif$
```
## Known issues
Since we use an HTML comment `<!--more-->` to separate the teaser,
sometimes `pandoc` can "eat" the comment while converting (for example
this happens with literate Haskell source). In order to overcome this
problem you may try to use something like this as a separator:
``` html
<div></div><!--more-->
```
|
