For the complete documentation index, see llms.txt. This page is also available as Markdown.

🗂️How the docs are organized

Read this page once. Then follow the sidebar from top to bottom for your first app. Depth is one click off that path. You should never need two homes for the same screen.

The maker path

Build in this order. Skip a section only when you already finished that job.

Order
Section
What you do here
What you do not do here

1

Get started

Connect Notion, create the first app, add a list and details, publish a checklist, make it private

Full Settings or Automation books

2

Builder

A short map of the left rail

A second Screens or Databases manual

3

Screens & components

Every screen type, view, component, and action

Billing, SSO, or webhook catalogs

4

Databases

Link, field types, sync, rollback, restriction

User login methods

5

Users

Privacy, login, signup, identity, view-as

Data sync steps (those live under Databases)

6

Settings

Brand, comments, versions, data, advanced

Publish URL and custom domain (Publish & share)

7

Publish & share

One hub: link, domain, collaborators

Builder rail tour

8

Automation

When you are ready: wizard → first approval → catalogs → screens

Re-teaching Work Queue (that guide stays under Types of Screens)

9

Integrations

Login and chat providers

Workflow webhooks (Automation)

10

Plans and entitlements

What each plan unlocks

How to build a screen

11

How-to guides

A 5-minute job

A second encyclopedia

12

Troubleshooting

One symptom, one answer, then back to the canonical page

A third copy of Automation

13

Use cases

End-to-end stories that reuse the same canonical pages

Re-teaching screen types

14

Video / Release notes / Archive

Watch, changelog, retired topics

Current setup steps

Four kinds of page

Start-here (Get started, most how-tos). One or two screens. Numbered steps. Then a “Full reference →” link into the canonical page. If a how-to needs more than about 400 words of “why,” that why belongs on the canonical page.

Canonical (one URL per topic). The long page. Every builder control, every shipped option, end-user behavior, plan gates, limits, a worked example, and troubleshooting. Gold standard: the Work Queue / Decision / Conversation screen guides and Comments.

Index / rail stub (Builder → Screens, Databases, Users, Settings, Automate; Automation native-screen index). About ten lines. A table of links. Never a third explanation of Work Queue or Sync.

Redirect. The old URL dies. It does not 404 and it does not retell the topic.

In-page shape (every canonical page)

  1. What this is / when to use it (and when not to)

  2. Before you start

  3. Build it (steps)

  4. Every control (tables)

  5. What users see

  6. Limits and plans

  7. Example

  8. Fix problems

  9. Related (the next page on the maker path)

Rules that keep the sidebar short

  • One Work Queue page: the long Types of Screens guide. The Automation index links to it. There is no second Work Queue book.

  • One sync page: Reload and sync. Get started and Workspace reload pages point there.

  • One publish hub: Publish & share. Get started publish is a short checklist that links to it.

  • New features land in the existing slot. Select Items goes under Types of Screens. Field map goes under Databases. Trigger catalog goes under Automation → Advanced Reference. Do not add a 15th top-level section.

  • Use how-to guides for short jobs; the canonical page holds the full reference.

Where to go next

If this is your first app, start at Connect Notion, then Create an app. If you already have an app and need a specific control, open Screens & components or Databases and stay on the canonical page for that topic.