GeezerVison

Document title

Identifies the subtitle of the document.

Document date

Date format for the document

Author or authors of the document

Summary of document

Order for document when included in a website automatic sidebar menu.

Use the specified file as a style reference in producing a docx, pptx, or odt file.

Branding information to use for this document. If a string, the path to a brand file. If false, don’t use branding on this document. If an object, an inline brand definition, or an object with light and dark brand paths or definitions.

A semver version range describing the supported quarto versions for this document or project.

Examples:

• >= 1.1.0: Require at least quarto version 1.1
• 1.*: Require any quarto versions whose major version number is 1

Include an automatically generated table of contents (or, in the case of latex, context, docx, odt, opendocument, rst, or ms, an instruction to create one) in the output document.

Note that if you are producing a PDF via ms, the table of contents will appear at the beginning of the document, before the title. If you would prefer it to be at the end of the document, use the option pdf-engine-opt: --no-toc-relocation.

Specify the number of section levels to include in the table of contents. The default is 3

The title used for the table of contents.

Number section headings rendered output. By default, sections are not numbered. Sections with class .unnumbered will never be numbered, even if number-sections is specified.

Shift heading levels by a positive or negative integer. For example, with shift-heading-level-by: -1, level 2 headings become level 1 headings, and level 3 headings become level 2 headings. Headings cannot have a level less than 1, so a heading that would be shifted below level 1 becomes a regular paragraph. Exception: with a shift of -N, a level-N heading at the beginning of the document replaces the metadata title.

Target body page width for output (used to compute columns widths for layout divs). Defaults to 6.5 inches, which corresponds to default letter page settings in docx and odt (8.5 inches with 1 inch for each margins).

The style to use when displaying code annotations. Set this value to false to hide code annotations.

Evaluate code cells (if false just echos the code into output).

• true (default): evaluate code cell
• false: don’t evaluate code cell
• [...]: A list of positive or negative numbers to selectively include or exclude expressions (explicit inclusion/exclusion of expressions is available only when using the knitr engine)

Include cell source code in rendered output.

• true (default in most formats): include source code in output
• false (default in presentation formats like beamer, revealjs, and pptx): do not include source code in output
• fenced: in addition to echoing, include the cell delimiter as part of the output.
• [...]: A list of positive or negative line numbers to selectively include or exclude lines (explicit inclusion/excusion of lines is available only when using the knitr engine)

Include the results of executing the code in the output. Possible values:

• true: Include results.
• false: Do not include results.
• asis: Treat output as raw markdown with no enclosing containers.

Include warnings in rendered output.

Include errors in the output (note that this implies that errors executing code will not halt processing of the document).

Catch all for preventing any output (code or results) from being included in output.

Cache results of computations (using the knitr cache for R documents, and Jupyter Cache for Jupyter documents).

Note that cache invalidation is triggered by changes in chunk source code (or other cache attributes you’ve defined).

• true: Cache results
• false: Do not cache results
• refresh: Force a refresh of the cache even if has not been otherwise invalidated.

Control the re-use of previous computational output when rendering.

• true: Never recompute previously generated computational output during a global project render
• false (default): Recompute previously generated computational output
• auto: Re-compute previously generated computational output only in case their source file changes

Figure horizontal alignment (default, left, right, or center)

Default width for figures generated by Matplotlib or R graphics.

Note that with the Jupyter engine, this option has no effect when provided at the cell level; it can only be provided with document or project metadata.

Default height for figures generated by Matplotlib or R graphics.

Note that with the Jupyter engine, this option has no effect when provided at the cell level; it can only be provided with document or project metadata.

Default format for figures generated by Matplotlib or R graphics (retina, png, jpeg, svg, or pdf)

Default DPI for figures generated by Matplotlib or R graphics.

Note that with the Jupyter engine, this option has no effect when provided at the cell level; it can only be provided with document or project metadata.

The aspect ratio of the plot, i.e., the ratio of height/width. When fig-asp is specified, the height of a plot (the option fig-height) is calculated from fig-width * fig-asp.

The fig-asp option is only available within the knitr engine.

Method used to print tables in Knitr engine documents:

• default: Use the default S3 method for the data frame.
• kable: Markdown table using the knitr::kable() function.
• tibble: Plain text table using the tibble package.
• paged: HTML table with paging for row and column overflow.

The default printing method is kable.

Document bibliography (BibTeX or CSL). May be a single file or a list of files

Citation Style Language file to use for formatting references.

Turn on built-in citation processing. To use this feature, you will need to have a document containing citations and a source of bibliographic data: either an external bibliography file or a list of references in the document’s YAML metadata. You can optionally also include a csl citation style file.

JSON file containing abbreviations of journals that should be used in formatted bibliographies when form="short" is specified. The format of the file can be illustrated with an example:

{ "default": {
    "container-title": {
      "Lloyd's Law Reports": "Lloyd's Rep",
      "Estates Gazette": "EG",
      "Scots Law Times": "SLT"
    }
  }
}

Configuration for cross-reference labels and prefixes. See Cross-Reference Options for more details.

Citation information for the document itself specified as CSL YAML in the document front matter.

For more on supported options, see Citation Metadata.

Identifies the main language of the document using IETF language tags (following the BCP 47 standard), such as en or en-GB. The Language subtag lookup tool can look up or verify these tags.

This affects most formats, and controls hyphenation in PDF output when using LaTeX (through babel and polyglossia) or ConTeXt.

YAML file containing custom language translations

The base script direction for the document (rtl or ltr).

For bidirectional documents, native pandoc spans and divs with the dir attribute can be used to override the base direction in some output formats. This may not always be necessary if the final renderer (e.g. the browser, when generating HTML) supports the [Unicode Bidirectional Algorithm].

When using LaTeX for bidirectional documents, only the xelatex engine is fully supported (use --pdf-engine=xelatex).

Include contents at the beginning of the document body (e.g. after the <body> tag in HTML, or the \begin{document} command in LaTeX).

A string value or an object with key “file” indicates a filename whose contents are to be included

An object with key “text” indicates textual content to be included

Include content at the end of the document body immediately after the markdown content. While it will be included before the closing </body> tag in HTML and the \end{document} command in LaTeX, this option refers to the end of the markdown content.

A string value or an object with key “file” indicates a filename whose contents are to be included

An object with key “text” indicates textual content to be included

Include contents at the end of the header. This can be used, for example, to include special CSS or JavaScript in HTML documents.

A string value or an object with key “file” indicates a filename whose contents are to be included

An object with key “text” indicates textual content to be included

Read metadata from the supplied YAML (or JSON) files. This option can be used with every input format, but string scalars in the YAML file will always be parsed as Markdown. Generally, the input will be handled the same as in YAML metadata blocks. Values in files specified later in the list will be preferred over those specified earlier. Metadata values specified inside the document, or by using -M, overwrite values specified with this option.

List of keywords to be included in the document metadata.

The document subject

The document description. Some applications show this as Comments metadata.

Format to read from. Extensions can be individually enabled or disabled by appending +EXTENSION or -EXTENSION to the format name (e.g. markdown+emoji).

Output file to write to

Extension to use for generated output file

Use the specified file as a custom template for the generated document.

Include the specified files as partials accessible to the template for the generated content.

Specify executables or Lua scripts to be used as a filter transforming the pandoc AST after the input is parsed and before the output is written.

Specify Lua scripts that implement shortcode handlers

Keep the markdown file generated by executing code

Keep the notebook file generated from executing code.

Filters to pre-process ipynb files before rendering to markdown

Specify which nodes should be run interactively (displaying output from expressions)

If true, use the “notebook_connected” plotly renderer, which downloads its dependencies from a CDN and requires an internet connection to view.

Extract images and other media contained in or linked from the source document to the path DIR, creating it if necessary, and adjust the images references in the document so they point to the extracted files. Media are downloaded, read from the file system, or extracted from a binary container (e.g. docx), as needed. The original file paths are used if they are relative paths not containing … Otherwise filenames are constructed from the SHA1 hash of the contents.

List of paths to search for images and other resources.

Specify a default extension to use when image paths/URLs have no extension. This allows you to use the same source for formats that require different kinds of images. Currently this option only affects the Markdown and LaTeX readers.

Specifies a custom abbreviations file, with abbreviations one to a line. This list is used when reading Markdown input: strings found in this list will be followed by a nonbreaking space, and the period will not produce sentence-ending space in formats like LaTeX. The strings may not contain spaces.

Specify the default dpi (dots per inch) value for conversion from pixels to inch/ centimeters and vice versa. (Technically, the correct term would be ppi: pixels per inch.) The default is 96. When images contain information about dpi internally, the encoded value is used instead of the default specified by this option.

If none, do not process tables in HTML input.