Pages & mapping

When you connect Notion, Amendary discovers the pages you shared with it. Discovered is not the same as watched: a discovered page does nothing until you watch it. Watching a page means it is classified (Help center or Engineering docs) and mapped to a repo. The Pages tab shows your watched pages by default; use “Browse workspace” to find and watch the rest.

A destination is where your docs live. Today that is a Notion workspace (pages Amendary watches and corrects, and where product updates can grow) or a GitHub repo (a docs folder or the wiki). Markdown files there are listed as pages, watched and corrected like Notion pages, with corrections written back as a commit or pull request; generated docs are published there too. Add one with Add destination at the top of the Pages tab and pick the kind. A team can have several, and Notion and GitHub work independently: a repo can publish to one, the other, or both.

On the Pages tab, open “Browse workspace”, expand a database or page to find the one you want, and select “Watch”. In the map form you pick three things: the audience (Engineering docs or Help center), the page shape (Docs & guides by default, or a runbook, incident playbook, or Product updates), and the repo it is about. That one step adds, classifies and maps the page, so it is watched right away. To stop, remove the repo mapping on the page. You can also paste a page’s Notion link into “Add by Notion URL” first.

Separate from the audience, the shape says how the page is checked. Docs & guides (the default) has stale sentences corrected as code changes. On-call runbook and incident playbook are checked more strictly: a changed command, path or default counts as staleness. Product updates turns the page into a changelog: instead of correcting it, Amendary adds dated entries under it as the mapped repo ships. You choose the shape in the same map form; most pages stay on Docs & guides.

• Help center: customer-facing pages. Checked against the repo’s change trigger (commits by default, or a branch, GitHub Releases, or tags, set per repo on the Repos tab), since these pages describe what customers see, not internals.
• Engineering docs: reference material and guides describing how the product works internally. Checked against code changes.
• Excluded: discovered but not watched. Never read or edited; nothing is touched until you watch it.

It is what counts as a shipped change for that repo, set on the Repos tab. Four options: commits on the default branch (the default), commits on a branch you name, published GitHub Releases, or new git tags. Engineering docs always follow commits on the default branch, whatever the trigger. Help-center pages follow the trigger you chose. If the trigger has no signal yet (for example Releases chosen but none published), the Repos tab shows a “No signal for this trigger yet” warning with the fix, and help-center pages mapped to that repo are not checked until it does.

Yes. In “Browse workspace”, a database expands to the pages inside it; watch any of those pages the same way. Amendary watches individual pages, not whole databases, so you choose exactly which pages to keep current.

Amendary can only see pages you shared with the integration when you connected Notion, and Notion search is not exhaustive. If a page is missing, reconnect Notion and select it (or its parent) in Notion’s picker, or paste its link into “Add by Notion URL”. A page that was deleted or unshared in Notion is shown as gone and is no longer checked.

Yes. On a watched page, add an optional path (like /api) so only changes under that folder are considered for that page. A page can be watched against more than one repo, and a repo can have many pages.

On the Pages tab, select “Disconnect” next to the connection. Amendary stops reading that workspace and forgets its discovered pages. Your Notion content is not changed, and you can reconnect any time.