ENH: Support for unified website when multiple sphinx outputs (html, pdf) are required

Is your feature request related to a problem? Please describe.

Sphinx typically build a target type such as html, latex, pdf via latex etc. from a common source. However websites for books typically need to use a number of these build types such as html and pdf to support a download option. When they are run separately – it is sometimes hard to keep the assets in sync and have up to date pdf builds of the site contents etc.

Describe the solution you’d like

Perhaps we should add a sphinx builder website that integrates the build process for multiple output types and manages the assets into a unified _build target to simply deployments.

For example:

jb build ./ --builder=website

would trigger an html build, then a pdf build and copy all necessary built files into _build/website/.

Describe alternatives you’ve considered

An alternative is we could add a sphinx extension to enable pdf downloads (via sphinx build process) for html builder with a simple option in conf for which pdf engine to use pdfhtml or pdflatex

Just not sure if this should be a builder or an extension for html to add pdf.

[choldgraf]

@DavidPowell hmm - I wonder if it’s worth opening an issue specifically about single-page PDF printing to track these kinds of usability bugs

[choldgraf]

I mean, we already use _build for jupyter_execute etc, so I think there’s already precedent for using it as a general build outputs folder