1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
#lang pollen
◊; Copyright 2015 by Joel Dueck. All Rights Reserved.
◊(define-meta published "2015-09-01")
◊title{Pollen Targets}
I’ve been digging into Pollen. It’s early days yet, but it seems very promising. So I was surprised
and glad to see this happen today:
◊blockquote{◊link[1]{“New Pollen tutorial:} how to generate multiple outputs (e.g., HTML, plain text,
LaTeX, and PDF) from one source file.”
◊footer{Matthew Butterick (◊mono{@mbutterick}) in a now-deleted tweet}
◊url[1]{https://docs.racket-lang.org/pollen/fourth-tutorial.html}
}
|
|
|
<
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
|
#lang pollen
◊; Copyright 2015 by Joel Dueck. All Rights Reserved.
◊(define-meta published "2015-09-01")
◊title{Pollen Targets}
I’ve been digging into Pollen. It’s early days yet, but it seems very promising. So I was surprised
and glad to see this happen today:
◊blockquote{◊link[1]{“New Pollen tutorial:} how to generate multiple outputs (e.g., HTML, plain text,
LaTeX, and PDF) from one source file.”}
◊attrib{Matthew Butterick (◊mono{@mbutterick}) in a now-deleted tweet}
◊url[1]{https://docs.racket-lang.org/pollen/fourth-tutorial.html}
I tweeted earlier today that this is probably the best web/writing news of the summer, if not the
year. Yes, that’s subjective. But anyhow, let me explain why I think it’s great.
For at least a few years now I’ve been trying to figure out how a good way to generate a web site
and a print-ready PDF book from the same source document (◊xref["future-proofing"]{because
reasons}). Before Pollen, the best route seemed to be: write the documents in ◊link[2]{Markdown},
|
