> 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/set-up-synthesis-outputs/abstract-editor.md). # Abstract Editor Learn how to build an abstract displayed on Synthesis. Use Abstract Editor to write an abstract displayed on the Synthesis landing page. **Building this yourself?** You're in the right place. **Looking at a Synthesis Abstract?** See [**Synthesis Abstract.**](/review-workflow/synthesis/navigate-synthesis-outputs/synthesis-abstract.md) It displays directly on the **Synthesis landing page** itself for any reader with access. Choose Abstract Editor over [Manuscript Editor](/review-workflow/synthesis/set-up-synthesis-outputs/manuscript-editor.md) when you need a short summary rather than a full write-up — Abstract Editor is intentionally more limited: it does not support updatable tables, PRISMA insertion, or citations. If you find yourself needing those, move to Manuscript Editor instead. ### Writing Your Abstract Navigate to **Abstract Editor** under Synthesis. Any existing content is shown and can be edited at any time. It works as a standard text editor. Type or paste content, including tables, links, and images, using the formatting toolbar. You can also edit the authors displayed.

Abstract Editor showing the formatting toolbar and abstract content area. — The Abstract Editor.

### Generating An Abstract With Smart Abstract Rather than writing from scratch, Enterprise and Academic+ users can generate a structured Methods, Results, and Discussion abstract directly from the nest's data using [**Smart Abstract**](/review-workflow/synthesis/set-up-synthesis-outputs/abstract-editor/smart-abstract.md). Select the **Smart Abstract** button in the top left of the editor. Note that generating **overwrites any existing abstract content** so copy out anything you want to keep first. Once generated, review and refine it like any manually written abstract. ### Beyond The Abstract An abstract summarizes your review, but you can also use: * [Manuscript Editor](/review-workflow/synthesis/set-up-synthesis-outputs/manuscript-editor.md) is the place to draft a full write-up including updatable tables, PRISMA insertion, and citations. * [Dashboard Editor](/review-workflow/synthesis/set-up-synthesis-outputs/dashboard-editor.md) builds a visual, interactive summary from configurable modules, better suited to audiences who want to explore the evidence base at a glance rather than read it in prose. ### Next Steps


Smart Abstract	Generate an abstract from your review data.	Smart Abstract
Manuscript Editor	Draft a full narrative with citations.	Manuscript Editor
Dashboard Editor	Build a visual, living evidence summary.	Dashboard Editor

--- # 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/set-up-synthesis-outputs/abstract-editor.md?ask=&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.