Pages & mapping

When you add a destination, Amendary lists its pages or articles. Listed is not watched: a listed page does nothing until you watch it. The Pages tab shows your watched pages. Use Browse on a destination’s card to find and watch the rest.

Separate from the audience, the type 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. Architecture decisions holds one record per real decision; its history is never rewritten, only its evidence and references are corrected. Product updates turns the page into a changelog that grows as its source repos ship. A page has one type, set on the page row (not per repo), and you can change it any time. The audience limits the types: Engineering docs can be Docs & guides, On-call runbook, Incident playbook or Architecture decisions; Help center can be Docs & guides or Product updates. Product updates are Notion only. A Zendesk or Intercom article is always Help center, Docs & guides, with no picker. More on Document types.

Yes. A page can be mapped to several repos. Its audience and type stay the same for every repo. Add another repo with “Add repo” on the page row, and give each mapping a role (next question).

• Help center: customer-facing articles. Checked against what the destination’s card names under Help articles follow: what counts as shipped for a repo (see below) or a changelog URL. Every Zendesk and Intercom article is Help center.
• Engineering docs: reference material and guides describing how the product works internally. Checked against code changes.

• On the Notion or GitHub tab, set the page’s audience to Checks paused, or select pages and use Pause checks. The page is not checked or edited, and its repos are kept. Set an audience again to resume.
• A Zendesk or Intercom article cannot be paused. Unwatch it instead.
• Unwatch stops watching the page and drops its repos.

Set it under What counts as shipped 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 you choose. Help-center pages follow your choice. The same signal feeds a Product updates changelog. If nothing has shipped that way yet (for example Releases chosen but none published), the Repos tab shows “Nothing has shipped this way yet” with the fix, and help-center pages mapped to that repo are not checked until it does. A help center that follows a changelog URL checks each new dated entry instead.

Yes. In Browse on the Notion card, 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 open the … menu on the Notion card, select Add a page by link… and paste its link. 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. Bulk Map has the same optional path filter. A page can be watched against more than one repo, and a repo can have many pages.

Run a cleanup first. It reads the pages you pick, watched or not, and marks the ones that describe things gone from your code as Probably remove. On the Pages tab, “Find pages to clean up” opens it when Cleanup is on for your team.

Yes, when Diagrams is on for your team (early access). A watched Notion page mapped to a repo has a Diagrams section in its row, with Suggest a diagram. See Diagrams.

• Notion, Zendesk, Intercom: an owner opens the … menu on the card and selects Disconnect. Amendary stops reading it and deletes the corrections and check results for its pages (and product-update entries for Notion). Reconnecting does not bring them back.
• GitHub: an owner selects Remove destination in the same menu. Amendary unwatches its pages and stops writing to the repo. The repo stays connected on the Repos tab.
• Nothing in the destination itself is changed.

• Queue & reviews: what happens once a watched page gets a correction.
• Glossary: destination, audience, type and the other terms used here.