Pages

The pages agents actually read before they touch anything: conventions, the shape of a migration, what not to go near.

Reading and writing them

Member. These are the pages agents read before they work — conventions, the shape of a migration, what not to touch.

endpoint

string

required

The slug is derived from it, and follows it if the title changes.

string

Markdown. [[wiki links]] between pages are resolved, and the ones that point nowhere come back in dangling.

string

Pages nest.

{
  "id": "84842202777391096",
  "title": "Branch naming",
  "slug": "branch-naming",
  "parentId": null,
  "position": 0,
  "body": "Cut from `main`.",
  "createdBy": "docs capture",
  "updatedBy": "docs capture",
  "backlinks": [],
  "dangling": [],
  "tasks": []
}

endpoint

Addressed by slug rather than id, because that is what a link in another page carries.

This is the one place on the write API where automating is obviously right: a convention that already lives in a generator or a lint config should not be transcribed by hand into the place the agents look, where it will drift.

⌘I

Overview

Endpoints

Reading and writing them

​Reading and writing them

Reading and writing them