List all trees with stable UUIDs, descriptions and membership counts.

Read site identity and publication status; never exposes the photo editing code.

Set website title and Cloudflare project independently of tree names.

Choose project before the first publication. Changing a published project requires a separate installation so its photo storage and URL cannot be reassigned by accident.

Add existing collection people to a tree, or remove membership only.

Reuse UUIDs found with find_people (omit tree to search all people). Relationships are visible whenever both endpoints belong to the tree; no person is copied. Removing membership preserves the person's record and all global relationships.

Create a new, empty family tree.

Rename a tree. People, backups and relationships are kept.

Delete only a tree definition. Shared people remain; undo restores the tree.

Revert the last collection-wide transaction, including all affected trees.

This is global history, not per-tree history. Undone changes cannot be redone.

Return the whole tree: every person with their parent and partner ids.

Add one or many people and their parent, partner and sibling links in one call.

Use a one-entry list to add a single person. Each entry can link to others in the batch by their ref (or name) and to existing people by id. All entries are added, or none are if any link is invalid.

Change many existing people at once: details and renames, then links to add or remove.

Use for one or many person updates or relationship changes. Each link reads "relative_id is person_id's relation"; set remove=true to remove it. Everything applies, or nothing does if any entry fails, and undo reverts it all in one step. To add new people, use add_people.

Merge a duplicate into keep_id, then remove the duplicate.

Applies across EVERY tree. Fills keep_id's missing details from the duplicate and moves its parents, partners and children. Also use it to replace a placeholder parent with the real person.

Delete a person and all relationships from EVERY tree.

To remove only their appearance in one tree, use set_tree_members(remove=True).

Find names matching every query word. Omit tree to search the shared collection.

Search globally before creating people; reuse existing UUIDs with set_tree_members.

Get a person's details with their parents, partners, children and siblings.

List things to review: children linked to only one of a couple, people with the same name, and placeholder parents. Report them to the user rather than fixing them unasked.

Name how relative_id is related to person_id (e.g. "first cousin once removed").

List a person's ancestors by generation (1 = parents, 2 = grandparents, ...).

List a person's descendants by generation (1 = children, 2 = grandchildren, ...).

Build the complete site locally, including chooser and every tree, without deploying.

Publish the ENTIRE configured website: chooser and all trees.

First call configure_website. All collection trees are public; living dates, places and notes are hidden by default. Automatic updates rebuild the entire site after edits pause. Publishing requires Cloudflare authentication; photos use a site-wide code.

Replace the site-wide photo editing code and republish the complete website.