The PreTeXt Guide

We assume you are using managed directories, and have WeBWorK representations file as above. Build the HTML with pretext build web. You can also use pretext/pretext to build HTML. For example:

$ pretext -c all -f html -p <publisher> -d <destination> aota.ptx

-p specifies the publication file, as described in Chapter 44.

-d specifies a folder to place all of the HTML output. If unspecified, this will be the current working directory.

There are five publisher file entries which control how a WeBWorK problem is realized within HTML output. These are divided based on where the exercise (or project-like) resides: inline, within a division of exercises, within a reading questions division, within a worksheet, or if it is a project or similar. If the class of problems is declared dynamic, then each problem has a button that readers can click to make the problem interactive. Conversely, if the class of problems is declared static, then the problems render with a static preview.

By default, inline exercises and project-like will be dynamic, under the assumption that these are meant to be worked as a reader works through the material. The others will be static, under the assumption that they will be placed on a WeBWorK server where they will be worked for scores and grades. See Subsection 44.4.4 for the precise syntax for these switches.

If an exercise is subdivided into tasks, then by default they will only be revealed incrementally as the reader answers each one correctly. If you would like to have all tasks revealed from the start, then this option may be elected in the publication file (see Subsection 44.8.6).