Use Docs for quick notes, project briefs, reference material and longer writing. Pages can be nested and linked so an idea has both a home and a path to related work.
Work with blocks
The canonical editor uses BlockSuite and Yjs. Write and format blocks, organize content and add page references. Use the editor’s contextual controls and slash menu to discover available blocks.
Pages have a comfortable reading width by default. Choose Full width when a database or larger layout needs room. Page icons, covers and appearance controls help distinguish different kinds of content.
Put data in context
Insert an inline database view to bring structured records into a document. The view points to an existing database or the database you create through its picker. It does not create disconnected copies of every record.
An inline database can appear alongside prose or in a supported callout. Records still use the same properties, permissions and underlying document content. See databases and views.
Follow connections
Page references and backlinks connect related information. Search finds accessible workspace content and preserves links to the original page or record.
For a dedicated map of those relationships, install Atlas. The map opens the same canonical documents rather than maintaining a second notebook.
Saves and conflicts
Document saves include a revision check. If another save has changed the revision, resolve the conflict instead of assuming your draft can overwrite the new version. Native clients also have persisted draft and recovery flows.
Keep a copy or export of important unsaved work before resolving a conflict. Revision checks are not a promise of simultaneous live co-editing or general offline synchronization.
Work through an agent
The MCP and CLI bridge can read document snapshots and, when writes are enabled, initialize or save them with an expected revision. Normal workspace authorization still applies.