Add pdf-specific rendering and profiles #67
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds separate Quarto Profiles for the HTML build and the PDF build. Doing so allows us to make format-specific changes, such as omitting
data.qmd
from the pdf build (no need for a data portal in print format). This represents a major step forward in the control of our renderings while maintaining our streamlined single-job workflow.Changes overview:
_quarto.yml
has been split into two profiles:_quarto-html.yml
and_quarto-pdf.yml
_quarto.yml
is now just a pointer towards the two profilesindex.html
andabout.html
for demonstration purposes. View the pdf hereGoing forward, we can now modify content rendered to the PDF, which keeps us all sane.
Note: commits were squashed, see fork for original commit history.