> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-abstract.md).

# Synthesis Abstract

Learn how to navigate the synthesis abstract / landing page.

This is the first page you land on when you open a link to a Nested Knowledge review. If you've been sent a link and this is your first time here, you're in the right place: no account or software experience is needed to read it.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2Fk0lDDDmzMfGNziL8CmJR%2Fsynthesis%20landing.png?alt=media&amp;token=b581f628-3f20-4b8f-834c-a7a1099c89d0" alt="The Synthesis landing page, showing the review description, contributors, abstract, and navigation menu."><figcaption><p>The Synthesis landing page provides review context and links to available outputs.</p></figcaption></figure>

### What's On This Page

* **Description and Contributors** — basic context on the review: who's running it, and what it's about.
* **Abstract** — a short summary of what the review asked, how it was conducted, and what it found, if the reviewer has written one. Not every review has one yet — reviewers add this as the review progresses, so an empty or missing abstract usually just means the review is still underway, not that something's wrong.
* **Critical Appraisal Visuals** — if critical appraisal has been completed, the Domain Distribution and Traffic Light diagrams appear at the bottom of the Contributors column. [See here](/review-workflow/synthesis/navigate-synthesis-outputs/critical-appraisal-outputs.md) for how to read these.
* **Navigation to the rest of Synthesis** — a menu (left-hand, on desktop) listing whichever outputs the reviewer has built or enabled: [Dashboard in Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/dashboard-in-synthesis.md), [Manuscript in Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/manuscript-in-synthesis.md), [Qualitative Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/qualitative-synthesis.md), [Quantitative Synthesis](/review-workflow/synthesis/navigate-synthesis-outputs/quantitative-synthesis.md), [Critical Appraisal Visuals](/review-workflow/synthesis/navigate-synthesis-outputs/critical-appraisal-outputs.md), and the [PRISMA Chart](/review-workflow/synthesis/navigate-synthesis-outputs/prisma-chart.md).

{% hint style="info" %}
[Synthesis Chat](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-chat.md) is an exception and requires a valid account to use.
{% endhint %}

### Sharing This Page

Like the rest of Synthesis, this page can be shared further by link, QR code, or embed, using the share icon. This is provided the reviewer has made the review Public or Protected. Sharing the general Synthesis link, rather than a specific sub-page, sends someone here first, so they get the review's context before diving into any one output.

### FAQs

<details>

<summary>Why don't I see an abstract on this page?</summary>

The reviewer hasn't written one yet, or hasn't finished it — this is common for a review still in progress. Check back later, or ask the reviewer directly if you need a summary now.

</details>

<details>

<summary>Do I need a Nested Knowledge account to see this page?</summary>

No — if you've been sent a link and the review is set to Public or Protected, you can view this page and everything it links to without signing up.

</details>

<details>

<summary>I'm the reviewer — where do I write or edit the abstract shown here?</summary>

See [Abstract Editor](/review-workflow/synthesis/set-up-synthesis-outputs/abstract-editor.md), under Set up Synthesis Outputs.

</details>

### Next Steps

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-file-signature">:file-signature:</i><br><strong>Abstract Editor</strong></td><td>Write or edit the abstract shown here.</td><td><a href="/review-workflow/synthesis/set-up-synthesis-outputs/abstract-editor.md">Abstract Editor</a></td></tr><tr><td><i class="fa-chart-pie">:chart-pie:</i><br><strong>Qualitative Synthesis</strong></td><td>Explore findings by topic.</td><td><a href="/review-workflow/synthesis/navigate-synthesis-outputs/qualitative-synthesis.md">Qualitative Synthesis</a></td></tr><tr><td><i class="fa-chart-line">:chart-line:</i><br><strong>Quantitative Synthesis</strong></td><td>Explore numeric findings.</td><td><a href="/review-workflow/synthesis/navigate-synthesis-outputs/quantitative-synthesis.md">Quantitative Synthesis</a></td></tr><tr><td><i class="fa-clipboard-check">:clipboard-check:</i><br><strong>Critical Appraisal Visuals</strong></td><td>Read the appraisal visuals.</td><td><a href="/review-workflow/synthesis/navigate-synthesis-outputs/critical-appraisal-outputs.md">Critical Appraisal Outputs</a></td></tr></tbody></table>


---

# 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://docs.nested-knowledge.com/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-abstract.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.
