> 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/536/readme-1/contents-page.md).

# Content overview

A "curated guide" to this GitBook; updated June 2023

{% hint style="info" %}
**You can now ask questions of this GitBook using a chatbot:** click the search bar or press cmd-k and choose *"ask Gitbook*."
{% endhint %}

## Some key sections and subsections

### *Learn more about* The Unjournal*, our goals and policies*

[Frequently Asked Questions (FAQ)](/the-unjournal-project-and-communication-space/~/changes/536/faq-interaction.md) For authors, evaluators, etc.

[Explanations & outreach](/the-unjournal-project-and-communication-space/~/changes/536/readme-1/writings.md) Writeups of the main points for a few different audiences

[Why Unjournal?](/the-unjournal-project-and-communication-space/~/changes/536/benefits-and-features.md) Important benefits of journal-independent public evaluation and The Unjournal's approach, with links to deeper commentary

[Our policies: evaluation & workflow](/the-unjournal-project-and-communication-space/~/changes/536/policies-projects-evaluation-workflow.md) How we choose papers/projects to evaluate, how we assign evaluators, and so on

### Other resources and reading

[Parallel/partner initiatives and resources](/the-unjournal-project-and-communication-space/~/changes/536/parallel-partner-initiatives-and-resources.md) Groups we work with; comparing approaches

[What is global-priorities-relevant research?](/the-unjournal-project-and-communication-space/~/changes/536/the-field-and-ea-gp-research.md) What research are we talking about? What will we cover?

## Detail, progress, and internal planning

*These are of more interest to* people within our team; *we are sharing these in the spirit of transparency.*

[Plan of action](/the-unjournal-project-and-communication-space/~/changes/536/readme-1/plan-of-action.md) A "best feasible plan" for going forward

[Grants and proposals](/the-unjournal-project-and-communication-space/~/changes/536/grants-and-proposals.md) Successful proposals (ACX, SFF), other applications, initiatives

[UJ Team: resources, onboarding](/the-unjournal-project-and-communication-space/~/changes/536/management-tech-details-discussion/uj-team-resources-onboarding.md) Key resources and links for managers, advisory board members, staff, team members and others involved with *The Unjournal* project.

*Note: we have moved some of this "internal interest content" over to our Coda.io knowledge base.*


---

# 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/536/readme-1/contents-page.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.