On this page:
4.1 The book is a program
4.2 One language, multiple dialects
4.3 Development environment
4.4 A special data structure for HTML
4.5 Pollen command syntax
4.6 The preprocessor
4.7 Templated source files
4.8 Pagetrees
8.12

4 The big picture🔗ℹ

A summary of the key components & concepts of the Pollen publishing system and how they fit together. If you’ve completed the Quick tour, this will lend some context to what you saw. The upcoming tutorials will make more sense if you read this first.

4.1 The book is a program🔗ℹ

This is the core design principle of Pollen. Consistent with this principle, Pollen adopts the habits of software development in its functionality, workflow, and project structure.

4.2 One language, multiple dialects🔗ℹ

4.3 Development environment🔗ℹ

The Pollen development environment has three main pieces: the DrRacket code editor, the project server, and the command line.

4.4 A special data structure for HTML🔗ℹ

Unlike other programming languages, Pollen (and Racket) internally represent HTML with something called X-expressions. An X-expression is simply a list that represents an HTML element, meaning a thing with an opening tag, a closing tag, and content in between. Like HTML elements, X-expressions can be nested. Unlike HTML elements, X-expressions have no closing tag, they use parentheses to denote the start and end, and text elements are put inside quotes.

For example, consider this HTML element:

<body><h1>Hello world</h1><p>Nice to <i>see</i> you.</p></body>

As a Racket X-expression, this would be written:

(body (h1 "Hello world") (p "Nice to " (i "see") " you."))

More will be said about X-expressions. But several advantages should be evident already. First, without the redundant angle brackets, the X-expression is arguably more readable than the equivalent HTML. Second, an X-expression is preferable to treating HTML as a simple string, because it preserves the internal structure of the element. Third, an X-expression is a native data type in Racket.

4.5 Pollen command syntax🔗ℹ

As mentioned above, a Pollen source file is not code with text embedded in it, but rather text with code embedded. (See Pollen command syntax for more.)

4.6 The preprocessor🔗ℹ

The preprocessor is the simplest processing mode in Pollen.

4.7 Templated source files🔗ℹ

If you want to apply a particular page format to multiple sources of content — as you would in a book — you can use Pollen templates.

4.8 Pagetrees🔗ℹ

Similar to a table of contents, a pagetree is a special Pollen source file that gets turned into a hierarchical list of pages.