Turn research and source material into a readable responsive document with controlled hierarchy, reusable fields, review, and printable delivery.
Where: Designer → Add page → Document & research.
Key ideas
- A readable long-form canvas: Document pages are responsive and start with a centered article measure rather than a fixed artboard or timeline. Their job is structured reading, not slide-by-slide or email-client layout.
- Research is context, not automatic truth: The assistant can use attached documents, Brain records, project assets, and supported research context, but the page remains authored HTML. Claims, quotations, links, and permissions still need review.
- Structure survives styling: Headings, sections, lists, tables, figures, citations, and callouts should remain meaningful before typography and art direction are applied.
Steps
- Add a Document & research page and define its audience, purpose, length, and delivery format.
- Attach the source documents or mention the exact Brain record/record part; distinguish placed assets from visual references.
- Create an outline and section hierarchy before requesting a full long-form build.
- Build semantic article content, then apply the selected design system or art direction without flattening the hierarchy.
- Expose only the fields that a reader/editor should retune repeatedly, such as title, author, date, summary, or accent.
- Check Desktop, Tablet, and Mobile reading width, tables, figures, long links, and media captions.
- Review every factual claim and citation against its source, then run the rendered visual review.
- Export a PDF when the designed document is final, or share/download compiled HTML when interactive web delivery is intended.
Good document structure
- Title, author/date, summary, and navigable heading hierarchy
- Short paragraphs, lists, pull quotes, tables, and figures used for real information
- Source notes or citations near the claims they support
- A readable line length and responsive treatment for wide content
Available assistant families
- Document/stylesheet editing and exposed fields
- Motion and interactions when a web-delivered document benefits from them
- Stock/generated images and local image tools
- Art direction, design-system checking, review, pages, and Brain context
Tips
- Mention one Brain part instead of pinning a large record when only a single section matters.
- Review content accuracy separately from visual review; the latter judges what is visible, not whether a claim is true.
Limitations and important notes
- Designer does not validate research claims or citation style automatically.
- A PDF is a snapshot and cannot preserve every web interaction.
- Very wide tables or embeds require explicit responsive handling.
Troubleshooting
The document looks like a landing page.
Re-establish article hierarchy, readable measure, sources, and section flow before adding promotional visual treatments.
A source file seems ignored.
Attach it through the supported file path or mention the exact Brain record/part, then confirm the resolved chip before sending.