> For the complete documentation index, see [llms.txt](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/531/benefits-and-features/dynamic-documents-vs-living-projects/benefits-of-dynamic-documents.md).

# Benefits of Dynamic Documents

'Dynamic Documents' are projects or papers that are developed using prominent tools such as R-markdown or JuPyTer notebooks (the two most prominent tools).

The salient features and benefits of this approach include:

* **Integrated data analysis and reporting** means the data analysis (as well as math/simulations) is done and reported in the same space that the results and discussion are presented. This is made possible through the concealment of 'code blocks'.
* **Transparent reporting** means you can track exactly what is being reported and how it was constructed:
  * Making the process a lot less error-prone
  * Helping readers understand it better (see ['explorable explanations'](http://worrydream.com/ExplorableExplanations/))
  * Helping replicators and future researchers build on it
* Other advantages of these formats (over PDFs for example) include:
  * Convenient ‘folding blocks’
  * Margin comments
  * [Hoverable notes](#user-content-fn-1)[^1] and links
  * Integrating interactive tools

### **Better examples, the case for dynamic documents**

{% embed url="<https://quarto.org/>" %}

{% embed url="<https://distill.pub/2020/communicating-with-interactive-articles>" %}

{% embed url="<http://worrydream.com/ExplorableExplanations>" %}

<details>

<summary>Also consider...</summary>

* Elife's 'editable graphics'... Brett Viktor?
* see corrigendum in journals Reinhart and Rogoff error?
* open science MOOC in R markdown ...
* OSF and all of their training/promo materials in OS

</details>

### Reinstein's own examples

Some quick examples from my own work in progress (but other people have done it much better)

{% embed url="<https://daaronr.github.io/dualprocess/introduction-effective-giving-responses-to-analytical-effectiveness-information.html>" %}

{% embed url="<https://rethinkpriorities.github.io/ea_data_public/eas_donations.html>" %}

### Other (randomly selected) examples

{% embed url="<https://www.fharrell.com/post/impactpo>" %}

{% embed url="<https://bookdown.org/psonkin18/berkshire/#tldr-otherwise-known-as-an-executive-summary>" %}

{% embed url="<https://bookdown.org/jsiwinski2/play-in-book/>" %}

[^1]: like this.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://globalimpact.gitbook.io/the-unjournal-project-and-communication-space/~/changes/531/benefits-and-features/dynamic-documents-vs-living-projects/benefits-of-dynamic-documents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.