What you can build in Pages

Combine documents, visualizations, data, and shared work in one Page.

A Page can be a report, a visual explanation, a task tracker, or a focused interactive tool. Ask an agent for the outcome you want and the content it should use.

What you need	Page features	Guide
Quantitative analysis	Charts, metrics, sparklines, targets, heatmaps, and tables	Charts and dashboards
Relationships and processes	Flowcharts, sequence diagrams, hierarchies, and dependency graphs	Graphs and diagrams
Structured information	Searchable tables, saved datasets, shared records, and connected resource views	Tables, datasets, and databases
Tracking work	To-dos, boards, milestones, timelines, decisions, risks, and polls	Tasks and trackers
Visual evidence	Images, galleries, captions, regions, and before/after comparisons	Images and comparisons
Research and review	Citations, source excerpts, evidence, and revision comparisons	Evidence and sources
Calculators and focused tools	Scenario controls, local calculations, and permitted resource operations	Interactive Pages
Feedback	Whole-Page comments, passage comments, replies, and change requests	Comments and passage changes

Start with a useful request

Create a project review Page from these notes. Include a progress chart, a diagram of dependencies, and a shared to-do list. Label missing data and leave unknown owners unassigned.

You do not need to specify a component schema. Describe the job, the source material, and the interactions you want.

For an existing chat answer, Make a page asks the agent to turn it into a new Page. Ask the original author to refine the result.

Choose what should be saved

A Page has several kinds of state:

• Document content: text, layout, component definitions, and retained images are versioned with the Page.
• Saved data: a Page can refer to a specific dataset version.
• Shared work: tasks, votes, comments, and other records have their own saved revisions.
• Local exploration: a filter or calculator input may only affect your current view until you explicitly save it.
• Connected data: supported views or tools read current resources, subject to access.

Restoring document history does not rewind shared tasks, comments, or votes. Updating a dataset does not silently switch older Page bindings to the new version.

Markdown or HTML

Markdown Pages combine readable documents with supported visual and work components. HTML Pages support custom styling and JavaScript for focused interfaces.

Both can be useful without a running authoring agent once their content is published. Live tools and source data still depend on current access and availability.

Begin with Quickstart, then use the guides above to expand the result.