Writing - technical

This guide explains how we write papers in a reproducible, collaboration-friendly way using Quarto. You edit the manuscript in paper.qmd (Quarto Markdown) and manage references in references.bib (CSL controls the citation style). Quarto renders the project to submission formats (PDF/DOCX/LaTeX), while Git tracks changes and supports collaboration (PRs, reviews, history). Most contributors only need two commands: quarto preview while writing, and quarto render for final output.

Rationale

The paper development process is based on Quarto, Markdown, Git, Docker, Pandoc, and CSL. The goal is to support the collaborative writing process effectively, building on powerful open-source tools and facilitating the efficient production of documents for submission. Advantages of this workflow:

Separation of content and format.
Collaboration and versioning of text with Git.
Relying on active open-source projects such as the CSL standard.
Combined writing and comments in the same document.
Reproducibility across platforms.
Generating DOCX/TeX/PDF as output.

Since the underlying open-source projects (especially CSL, Pandoc, pandoc-citeproc) evolve constantly, it is recommended to work with the latest versions.

The paper template is based on the following underlying architectural principles and considerations:

Minimal functionality: the most frequent use cases (writing, citing, creating submission files in DOCX/TeX/PDF format with different templates and citation styles) must be supported in a highly efficient way. More complex functionality (such as tables with merged cells and detailed formatting) is used less frequently, requiring less effort if not supported efficiently. It may also create fewer problems (e.g., merging complex tables, as in Word/comparisons of tables).

Setup

This section explains how to install the environment and build the paper. Quarto is required. Git, Docker, and Make are recommended. The following steps describe how to:

Set up the repository (create a new one or contribute to an existing one),
Edit the paper, and
Build the paper.

The paper template creates the following files (additional files for the analysis can be added):

├── README.md     <- README containing summaries of the paper's revisions (completed
│                    and ongoing). Revision sheets are created from this document.
├── paper.qmd     <- Contains the paper
├── Makefile      <- Contains instructions to build the paper (as PDF or DOCX),
│                    and run the analyses (if a Makefile exists in the analysis
│                    directory)
├── Dockerfile    <- Describes the Pandoc container for building the paper
│                    (called by the Makefile)  
├── literature    <- Directory containing literature summaries for Obsidian
├── figures       <- Directory containing all conceptual figures
├── output        <- Directory containing all output, such as data plots and
│                    tables, which is generated by the scripts (do not store
│                    anything else that is not generated by the scripts in this
│                    directory)
└── .gitignore    <- Contains a list of files that are excluded from Git
                     versioning (e.g., paper.pdf, which would create conflicts
                     when merging changes)

Templates (*.docx, *.tex) and styles (*.csl) are versioned in the paper repository. This can be accomplished by using the code in comments at the beginning of the Makefile.

Step 1: Set up the repository

Start your manuscript development by using the Quarto template. This template provides a structured format for your initial drafts, helping to organize content efficiently.

Option 1: Create a new repository

Select a short and pronounceable title for the paper.
Do not refer to papers by their target journal (e.g., “the Journal of Information Technology paper”).
Use our Quarto template:

git init
quarto use template fs-ise/paper-template
# change title etc.
# git add . 
# git commit ...
# etc.
# git remote add origin https://github.com/....
# git branch -M main
# git push -u origin main
quarto preview

Option 2: Contribute to an existing repository

# pull repository
git clone git@github.com:fs-ise/...
pre-commit install

Step 2: Edit the paper

The paper.qmd is written in Markdown. There are three ways to edit a paper:

GitHub edit

Does not support DOCX/TeX/PDF generation.
Does not support commits changing multiple files.
Requires an Internet connection.
No setup required.

Short illustration

Codespace edit

Supports DOCX/TeX/PDF generation.
Supports all types of commits.
Requires an Internet connection.
No setup required.

Short illustration

Local edit

Supports DOCX/TeX/PDF generation.
Supports all types of commits.
Does not require an Internet connection.
Requires some setup.

Short illustration

Step 3: Build the paper

quarto preview
# MANUALLY select a citation style by updating the link at the beginning of the Makefile
# MANUALLY select templates for DOCX/TeX/PDF by updating the link at the beginning of the Makefile

Citation styles can be selected here.
Templates are available here.
See Pandoc journal templates.

Markdown hints

Useful guides on Markdown are available online (1, 2).

It is good practice to:

Begin each sentence on a new line to make the history more readable and to facilitate merging (see semantic line breaks).

Figures can be included as follows and referred to as @fig:distribution. Further information on pandoc-crossref is available online.

![Figure Caption](figures/figure.jpg){#fig:distribution width=300px}

We show the findings in @fig:distribution.

To ensure compatibility with Pandoc Word and LaTeX conversion, figures should be included as JPG/PNG. For the final versions, vector graphics (PDF, EMF) should be included for LaTeX/Word, respectively.

Formulas can be included as follows:

$$ P_i(x) = \sum_i a_i x^i $$ {#eq:eqn1}

Tables can be created with GridTables (which is displayed in PDF and Word documents):

+---------------------+----------+
| Property            | Earth    |
+=============+=======+==========+
|             | min   | -89.2 °C |
| Temperature +-------+----------+
| 1961-1990   | mean  | 14 °C    |
|             +-------+----------+
|             | max   | 56.7 °C  |
+-------------+-------+----------+

Table: Findings {#tbl:findings}

We show the findings in @tbl:findings.

Markdown table editor.

Footnotes:

Text with a footnote [^1].

  [^1]: Example footnote.

Comments:

<!--
Comments can be used to add further explanations, links to references/resources,
or to keep parts of the paper that were shortened
-->

Information on references and citations is in the editing-markdown-paper section.

Note

Literature summaries: Obsidian

Literature summaries for each paper are stored in Obsidian format in the literature directory.

Citations and reference sections

Citing allows us to make the results of others understandable and give proper recognition to the authors. There are two main reasons why we cite: firstly, to respect copyrighted works, and secondly, to adhere to the principles of good scientific practice by appropriately acknowledging the contributions of others. The following examples use Markdown syntax (used by Pandoc converters and Quarto).

The syntax is based on the citation syntax (see CSL). Further information on the citation syntax is available in the Pandoc manual.

To include citations:

Add them to the references.
Cite them in the text, and
Generate the bibliography.

References (BibTeX file)

The bibliography is stored as a BibTeX file (typically references.bib) and versioned by Git.

Changes in the BibTeX file should be checked before committing.
References should be as complete as possible, including the relevant fields.
Each reference should be listed once (not multiple times).
Examples with relevant fields are summarized below.
Journal articles

@article{LeeAnderson2001,
    doi                = {10.1006/COGP.2000.0747},
    author             = {Anderson, John R},
    journal            = {Cognitive Psychology},
    title              = {Does learning a complex task},
    year               = {2001},
    volume             = {42},
    number             = {3},
    pages              = {267--316},
}

Conference papers

@inproceedings{LeeAnderson2001,
    author             = {Weber, Matthias and Remus, Ulrich and Pregenzer, Michael},
    booktitle          = {Proceedings of the International Conference on Information Systems},
    title              = {A new era of control: Understanding algorithmic control in the gig economy},
    year               = {2022},
}

Books:

@book{Kolb2014,
    author             = {Kolb, David A},
    title              = {Experiential learning},
    year               = {2014},
    publisher          = {FT Press},
}

Essays in collected editions:

@incollection{Anderson1984a,
    author             = {Anderson, Richard C},
    booktitle          = {Theoretical models},
    title              = {Role of the reader's schema in comprehension, learning, and memory},
    year               = {2018},
    pages              = {136--145},
    publisher          = {Routledge},
}

Websites

@online{Microsoft2018,
    author             = {Microsoft News Center},
    title              = {Microsoft to acquire GitHub for $7.5 billion},
    year               = {2018},
    url                = {https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/},
}

In-text citations

In-text citations can be parenthetical or narrative (see APA style). Word-for-word quotations (parenthetical or narrative) must be identified by quotation marks, and a page number must be given. Parenthetical citations tend to be preferred over narrative citations because they put more emphasis on the content, concepts, or findings instead of the authors.

The following example illustrates the citation syntax of Markdown (or the Pandoc converters used by Quarto) (link). The unique IDs (e.g., SmithEtAl2006) are used to link citations to the corresponding elements in the BibTeX file.

<!-- Example *parenthetical* citation: -->

Fitness trackers were found to have mixed effects on sedentary behavior [@SmithEtAl2006].

<!-- Example *narrative* citation: -->

@SmithEtAl2006 analyzed the effectiveness of fitness trackers.

<!-- Example *word-for-word quotation*: -->

For fitness trackers, "measures of sleep quality are inaccurate" [@SmithEtAl2006, p. 111].

When rendered with Quarto and the APA citation style, this will be displayed as:

Fitness trackers were found to have mixed effects on sedentary behavior (Smith et al. 2006).

Smith et al. (2006) analyzed the effectiveness of fitness trackers.

For fitness trackers, “measures of sleep quality are inaccurate” (Smith et al. 2006, p. 111).

Formatting guidelines

Fields

ENTRYTYPE set correctly (e.g., “article” or “inproceedings”).
author formatted correctly (Wagner, G. and Prester, J.).
title complete and in sentence case (e.g., “On the origin of species,” not “On the Origin of Species”).
journal field complete and in title case (e.g., “Journal of Information Technology,” not “JIT”).
volume, number, pages, doi fields added.

To update references based on Crossref, the colrev-sync package can be used:

colrev-sync sync

Notes

Groups of in-text citations should be sorted alphabetically (especially if a prefix is used), i.e., use [e.g., @Bacharach1989; @Gregor2006a] instead of [e.g., @Gregor2006a; @Bacharach1989].
Add {} to protect cases when necessary (e.g., {J}ab{R}ef) because CSL styles that require title case will use an automatic title-case conversion (1).
To cite software, datasets, and other artifacts, CiteAs is useful.
Journal fields: Some CSL styles require abbreviations. Temporarily replace the journal field in the BibTeX file since CSL does not handle style-specific journal abbreviations (1). JSON files containing journal abbreviations can be passed to Pandoc using the citation-abbreviations field.

Bibliography

In a Markdown document, the bibliography (also known as the references section) is created automatically based on the BibTeX file and CSL specified in the YAML header. The nocite field can be used to add references that are cited in figures/tables but not in the text.

---
title: "Writing"
bibliography: path_to_/references.bib
csl: path_to/apa.csl
nocite: |
  @Davis1989
  @LangePfarrer2017
  @StrunkWhite1999
  @WebsterWatson2002
---

... text with citations

# References

<!-- References will be generated in the specified CSL style after this heading. -->

Word/Zotero

For DOCX formats, use a reference manager plugin (such as Zotero). The reference manager should support the standardized citation styles of CSL.

Conceptual illustrations and plots

For conceptual illustrations, PowerPoint is currently recommended.

Ensure alignment, etc.
For PDF submissions, extract it as PDF (vector graphic with embedded text).
For Word submissions, extract it as EMF (vector graphic with embedded text).

To plot findings, the R package ggplot2 is recommended. ggplot2 is a powerful library and allows us to automatically update the figures when the findings change.

Note

It is possible to edit ggplot2 plots with LLMs (e.g., ChatGPT).

Quarto extensions

Books: Bookdown project.
Possible extensions (Lua filters): bibexport, abstract-to-meta, spellcheck, wordcount.

https://github.com/kapsner/authors-block https://github.com/jmgirard/embedpdf https://github.com/andrewheiss/quarto-wordcount

--- title: "Writing - technical" --- This guide explains how we write papers in a reproducible, collaboration-friendly way using Quarto. You edit the manuscript in `paper.qmd` (Quarto Markdown) and manage references in `references.bib` (CSL controls the citation style). Quarto renders the project to submission formats (PDF/DOCX/LaTeX), while Git tracks changes and supports collaboration (PRs, reviews, history). Most contributors only need two commands: `quarto preview` while writing, and `quarto render` for final output. ::: {.callout-note title="Rationale" collapse=true} The paper development process is based on Quarto, Markdown, Git, Docker, Pandoc, and CSL. The goal is to support the collaborative writing process effectively, building on powerful open-source tools and facilitating the efficient production of documents for submission. Advantages of this workflow: - Separation of content and format. - Collaboration and versioning of text with Git. - Relying on active open-source projects such as the [CSL](https://citationstyles.org/){target=_blank} standard. - Combined writing and comments in the same document. - Reproducibility across platforms. - Generating DOCX/TeX/PDF as output. Since the underlying open-source projects (especially CSL, Pandoc, pandoc-citeproc) evolve constantly, it is recommended to work with the latest versions. The paper template is based on the following underlying architectural principles and considerations: - Minimal functionality: the most frequent use cases (writing, citing, creating submission files in DOCX/TeX/PDF format with different templates and citation styles) must be supported in a highly efficient way. More complex functionality (such as tables with merged cells and detailed formatting) is used less frequently, requiring less effort if not supported efficiently. It may also create fewer problems (e.g., merging complex tables, as in Word/comparisons of tables). ::: ## Setup This section explains how to install the environment and build the paper. [Quarto](https://quarto.org/){target=_blank} is required. [Git](https://git-scm.com/){target=_blank}, [Docker](https://www.docker.com/){target=_blank}, and Make are recommended. The following steps describe how to: 1. Set up the repository (create a new one or contribute to an existing one), 2. Edit the paper, and 3. Build the paper. The paper template creates the following files (additional [files for the analysis](/research/analysis_templates.html) can be added): ```text ├── README.md <- README containing summaries of the paper's revisions (completed │ and ongoing). Revision sheets are created from this document. ├── paper.qmd <- Contains the paper ├── Makefile <- Contains instructions to build the paper (as PDF or DOCX), │ and run the analyses (if a Makefile exists in the analysis │ directory) ├── Dockerfile <- Describes the Pandoc container for building the paper │ (called by the Makefile) ├── literature <- Directory containing literature summaries for Obsidian ├── figures <- Directory containing all conceptual figures ├── output <- Directory containing all output, such as data plots and │ tables, which is generated by the scripts (do not store │ anything else that is not generated by the scripts in this │ directory) └── .gitignore <- Contains a list of files that are excluded from Git versioning (e.g., paper.pdf, which would create conflicts when merging changes) ``` Templates (\*.docx, \*.tex) and styles (\*.csl) are versioned in the paper repository. This can be accomplished by using the code in comments at the beginning of the Makefile. ### Step 1: Set up the repository Start your manuscript development by using the [Quarto template](https://github.com/fs-ise/paper-template){target=_blank}. This template provides a structured format for your initial drafts, helping to organize content efficiently. Option 1: Create a new repository - Select a short and pronounceable title for the paper. - Do not refer to papers by their target journal (e.g., "the Journal of Information Technology paper"). - Use our Quarto template: ```sh git init quarto use template fs-ise/paper-template # change title etc. # git add . # git commit ... # etc. # git remote add origin https://github.com/.... # git branch -M main # git push -u origin main quarto preview ``` Option 2: Contribute to an existing repository ```sh # pull repository git clone git@github.com:fs-ise/... pre-commit install ``` ### Step 2: Edit the paper The `paper.qmd` is written in Markdown. There are three ways to edit a paper: #### GitHub edit - Does not support DOCX/TeX/PDF generation. - Does not support commits changing multiple files. - Requires an Internet connection. - No setup required. ::: {.callout-note title="Short illustration" collapse=true} ![Illustration](https://raw.githubusercontent.com/fs-ise/handbook/main/assets/images/edit-paper-github.gif){target=_blank} ::: #### Codespace edit - Supports DOCX/TeX/PDF generation. - Supports all types of commits. - Requires an Internet connection. - No setup required. ::: {.callout-note title="Short illustration" collapse=true} ![Illustration](https://raw.githubusercontent.com/fs-ise/handbook/main/assets/images/edit-paper-codespaces.gif){target=_blank} ::: #### Local edit - Supports DOCX/TeX/PDF generation. - Supports all types of commits. - Does not require an Internet connection. - Requires some setup. ::: {.callout-note title="Short illustration" collapse=true} ![Illustration](https://raw.githubusercontent.com/fs-ise/handbook/main/assets/images/edit-paper-local.gif){target=_blank} ::: ### Step 3: Build the paper ```sh quarto preview # MANUALLY select a citation style by updating the link at the beginning of the Makefile # MANUALLY select templates for DOCX/TeX/PDF by updating the link at the beginning of the Makefile ``` - Citation styles can be selected [here](https://github.com/citation-style-language/styles){target=_blank}. - Templates are available [here](https://github.com/fs-ise/templates){target=_blank}. - See [Pandoc journal templates](https://github.com/sachsmc/pandoc-journal-templates){target=_blank}. ## Markdown hints {#markdown} Useful guides on Markdown are available online ([1](https://bookdown.org/yihui/rmarkdown/){target=_blank}, [2](https://bookdown.org/yihui/rmarkdown-cookbook/){target=_blank}). It is good practice to: - Begin **each sentence on a new line** to make the history more readable and to facilitate merging (see [semantic line breaks](https://sembr.org/){target=_blank}). Figures can be included as follows and referred to as `@fig:distribution`. Further information on [pandoc-crossref](https://lierdakil.github.io/pandoc-crossref/){target=_blank} is available online. ```Markdown ![Figure Caption](figures/figure.jpg){#fig:distribution width=300px} We show the findings in @fig:distribution. ``` To ensure compatibility with Pandoc Word and LaTeX conversion, figures should be included as JPG/PNG. For the final versions, vector graphics (PDF, EMF) should be included for LaTeX/Word, respectively. Formulas can be included as follows: ```latex $$ P_i(x) = \sum_i a_i x^i $$ {#eq:eqn1} ``` Tables can be created with [GridTables](https://pandoc.org/MANUAL.html#extension-grid_tables){target=_blank} (which is displayed in PDF and Word documents): ```Markdown +---------------------+----------+ | Property | Earth | +=============+=======+==========+ | | min | -89.2 °C | | Temperature +-------+----------+ | 1961-1990 | mean | 14 °C | | +-------+----------+ | | max | 56.7 °C | +-------------+-------+----------+ Table: Findings {#tbl:findings} We show the findings in @tbl:findings. ``` [Markdown table editor](https://www.tablesgenerator.com/markdown_tables){target=_blank}. Footnotes: ```Markdown Text with a footnote [^1]. [^1]: Example footnote. ``` Comments: ```Markdown  ``` Information on references and citations is in the [editing-markdown-paper](/research/writing_conceptual.html) section. ::: callout-note **Literature summaries: Obsidian** Literature summaries for each paper are stored in Obsidian format in the `literature` directory. ::: ### Citations and reference sections Citing allows us to make the results of others understandable and give proper recognition to the authors. There are two main reasons why we cite: firstly, to respect copyrighted works, and secondly, to adhere to the principles of good scientific practice by appropriately acknowledging the contributions of others. The following examples use Markdown syntax (used by Pandoc converters and Quarto). The syntax is based on the [citation syntax](https://pandoc.org/MANUAL.html#citation-syntax){target=_blank} (see [CSL](https://citationstyles.org/){target=_blank}). Further information on the [citation syntax](https://pandoc.org/MANUAL.html#citation-syntax){target=_blank} is available in the Pandoc manual. To include citations: - Add them to the [references](#bib-file). - [Cite](#citing) them in the text, and - Generate the [bibliography](#bibliography). #### References (BibTeX file){#bib-file} The bibliography is stored as a BibTeX file (typically `references.bib`) and versioned by Git. - Changes in the BibTeX file should be checked before committing. - References should be as complete as possible, including the relevant fields. - Each reference should be listed once (not multiple times). - Examples with relevant fields are summarized below. - Journal articles ```bibtex @article{LeeAnderson2001, doi = {10.1006/COGP.2000.0747}, author = {Anderson, John R}, journal = {Cognitive Psychology}, title = {Does learning a complex task}, year = {2001}, volume = {42}, number = {3}, pages = {267--316}, } ``` - Conference papers ```bibtex @inproceedings{LeeAnderson2001, author = {Weber, Matthias and Remus, Ulrich and Pregenzer, Michael}, booktitle = {Proceedings of the International Conference on Information Systems}, title = {A new era of control: Understanding algorithmic control in the gig economy}, year = {2022}, } ``` - Books: ```bibtex @book{Kolb2014, author = {Kolb, David A}, title = {Experiential learning}, year = {2014}, publisher = {FT Press}, } ``` - Essays in collected editions: ```bibtex @incollection{Anderson1984a, author = {Anderson, Richard C}, booktitle = {Theoretical models}, title = {Role of the reader's schema in comprehension, learning, and memory}, year = {2018}, pages = {136--145}, publisher = {Routledge}, } ``` - Websites ```bibtex @online{Microsoft2018, author = {Microsoft News Center}, title = {Microsoft to acquire GitHub for $7.5 billion}, year = {2018}, url = {https://news.microsoft.com/2018/06/04/microsoft-to-acquire-github-for-7-5-billion/}, } ``` #### In-text citations{#citing} In-text citations can be parenthetical or narrative (see [APA style](https://apastyle.apa.org/style-grammar-guidelines/citations/basic-principles/parenthetical-versus-narrative){target=_blank}). Word-for-word quotations (parenthetical or narrative) must be identified by quotation marks, and a page number must be given. Parenthetical citations tend to be preferred over narrative citations because they put more emphasis on the content, concepts, or findings instead of the authors. The following example illustrates the citation syntax of Markdown (or the Pandoc converters used by Quarto) ([link](https://pandoc.org/demo/example33/8.20-citation-syntax.html){target=_blank}). The unique IDs (e.g., ``SmithEtAl2006``) are used to link citations to the corresponding elements in the BibTeX file. ```Markdown  Fitness trackers were found to have mixed effects on sedentary behavior [@SmithEtAl2006].  @SmithEtAl2006 analyzed the effectiveness of fitness trackers.  For fitness trackers, "measures of sleep quality are inaccurate" [@SmithEtAl2006, p. 111]. ``` When rendered with Quarto and the APA citation style, this will be displayed as: > Fitness trackers were found to have mixed effects on sedentary behavior (Smith et al. 2006). > > Smith et al. (2006) analyzed the effectiveness of fitness trackers. > > For fitness trackers, "measures of sleep quality are inaccurate" (Smith et al. 2006, p. 111). ::: {.callout-note title="Formatting guidelines"} **Fields** - `ENTRYTYPE` set correctly (e.g., "article" or "inproceedings"). - `author` formatted correctly (Wagner, G. and Prester, J.). - `title` complete and in sentence case (e.g., "On the origin of species," not "On the Origin of Species"). - `journal` field complete and in title case (e.g., "Journal of Information Technology," not "JIT"). - `volume`, `number`, `pages`, `doi` fields added. To update references based on Crossref, the `colrev-sync` package can be used: ```sh colrev-sync sync ``` **Notes** - Groups of in-text citations should be sorted alphabetically (especially if a prefix is used), i.e., use `[e.g., @Bacharach1989; @Gregor2006a]` instead of `[e.g., @Gregor2006a; @Bacharach1989]`. - Add `{}` to protect cases when necessary (e.g., `{J}ab{R}ef`) because CSL styles that require title case will use an automatic title-case conversion ([1](https://citationstyles.org/authors/#/titles-in-sentence-and-title-case){target=_blank}). - To cite software, datasets, and other artifacts, [CiteAs](https://citeas.org/){target=_blank} is useful. - Journal fields: Some CSL styles require abbreviations. Temporarily replace the journal field in the BibTeX file since CSL does not handle style-specific journal abbreviations ([1](https://citationstyles.org/authors/#/csl-limitations){target=_blank}). JSON files containing journal abbreviations can be passed to Pandoc using the [citation-abbreviations](https://pandoc.org/MANUAL.html#option--citation-abbreviations){target=_blank} field. ::: #### Bibliography{#bibliography} In a Markdown document, the bibliography (also known as the references section) is created automatically based on the BibTeX file and [CSL](https://citationstyles.org/){target=_blank} specified in the YAML header. The `nocite` field can be used to add references that are cited in figures/tables but not in the text. ```Markdown --- title: "Writing" bibliography: path_to_/references.bib csl: path_to/apa.csl nocite: | @Davis1989 @LangePfarrer2017 @StrunkWhite1999 @WebsterWatson2002 --- ... text with citations # References  ``` ::: {.callout-note title="Word/Zotero" collapse=true} For `DOCX` formats, use a reference manager plugin (such as Zotero). The reference manager should support the standardized citation styles of [CSL](https://editor.citationstyles.org/about/){target=_blank}. ::: ### Conceptual illustrations and plots For conceptual illustrations, PowerPoint is currently recommended. - Ensure alignment, etc. - For PDF submissions, extract it as PDF (vector graphic with embedded text). - For Word submissions, extract it as EMF (vector graphic with embedded text). To plot findings, the R package [ggplot2](https://ggplot2.tidyverse.org/){target=_blank} is recommended. ggplot2 is a powerful library and allows us to automatically update the figures when the findings change. ::: callout-note It is possible to edit ggplot2 plots with LLMs (e.g., ChatGPT). ::: ::: {.callout-note title="Quarto extensions" collapse=true} - Books: [Bookdown](https://bookdown.org/yihui/bookdown/){target=_blank} project. - Possible extensions (Lua filters): [bibexport](https://github.com/pandoc/lua-filters/tree/master/bibexport){target=_blank}, [abstract-to-meta](https://github.com/pandoc/lua-filters/tree/master/abstract-to-meta){target=_blank}, [spellcheck](https://github.com/pandoc/lua-filters/tree/master/spellcheck){target=_blank}, [wordcount](https://github.com/pandoc/lua-filters/tree/master/wordcount){target=_blank}. https://github.com/kapsner/authors-block https://github.com/jmgirard/embedpdf https://github.com/andrewheiss/quarto-wordcount :::