Preprocessing

sbt-site supports basic variable substitution via the PreprocessPlugin if for example you need to replace a version string in a source file or a generated HTML file. More advanced preprocessing, such as interpreting code snippets with tut, is possible via additional configuration as shown below.

Variable Substitution

The PreprocessPlugin reads files from an input directory, substitute variables and writes them to an output directory. In addition to preprocessing static content it is also possible to use the plugin either before or after invoking a site generator. To enable, add this to your build.sbt file:

enablePlugins(PreprocessPlugin)

By default files are read from src/site-preprocess but this is configurable by setting sourceDirectory:

sourceDirectory in Preprocess := sourceDirectory.value / "site-preprocess"

Variables are delimited by surrounding the name with @ symbols (e.g. @VERSION@). Values are assigned to variables via the setting preprocessVars: [Map[String, String]]. For example:

preprocessVars in Preprocess := Map("VERSION" -> version.value, "DATE" -> new Date().toString)

The setting preprocessIncludeFilter is used to define the filename extensions that should be processed when makeSite is run.

preprocessIncludeFilter := "*.md" | "*.markdown"

The default filter is:

"*.txt" | "*.html" | "*.md" | "*.rst"

Preprocessing Markdown files with tut

The tut sbt plugin allows you to write documentation with fenced code blocks that is typechecked and run as part of your build. For example this markdown snippet:

Here is how you add numbers:

```tut
1 + 1
```

Will show the result of running the code in the Scala REPL:

Here is how you add numbers:

```scala
scala> 1 + 1
res0: Int = 2    
```

The following example shows how to use it to preprocess a collection of markdown files before running a site generator.

enablePlugins(ParadoxSitePlugin, TutPlugin)
sourceDirectory in Paradox := tutTargetDirectory.value
makeSite := makeSite.dependsOn(tut).value

The example uses the Paradox site generator but can be adapted to any site generator which understands markdown by configuring its sourceDirectory accordingly. For Jekyll, this would be:

sourceDirectory in Jekyll := tutTargetDirectory.value