Choosing a domain for a site is a poor experience because the two capabilities are presented as one #34

New Issue

2026-09-21T07:18:11Z

cgalo5758 commented

2026-09-21 07:18:11 +00:00

The question

A member picking a domain for a wiki site meets a chooser that reads badly: it mixes claiming a domain with serving a site at one. The registry already keeps the two apart, as a claim (ownership of a domain and everything under it) and a placement (the record that wires one exact domain to the site that serves it), but the member surfaces present a domain as a property of a site. Should the two capabilities be conveyed as separate things a member holds, and what does each surface then show?

What depends on the answer

The member's site pages, the member's domain pages and the operator's Domains page all render the same two objects. Whether a member claims a domain first and then points it at something, or picks a domain in the middle of creating a site, decides the shape of all of them, and whether a member can hold a domain before there is anything to serve at it.

Options known so far

Keep domains inside the site flow and rework the chooser alone.
Split the surfaces the way the registry is split: claiming a domain is its own act, and serving a site at a domain is a second act reachable from either side.

Decided when

The domains model states what a member holds and what a member points at, and the member and operator surfaces present that split.

Migrated from status/issues.md at b7a0e15

## The question A member picking a domain for a wiki site meets a chooser that reads badly: it mixes claiming a domain with serving a site at one. The registry already keeps the two apart, as a claim (ownership of a domain and everything under it) and a placement (the record that wires one exact domain to the site that serves it), but the member surfaces present a domain as a property of a site. Should the two capabilities be conveyed as separate things a member holds, and what does each surface then show? ## What depends on the answer The member's site pages, the member's domain pages and the operator's Domains page all render the same two objects. Whether a member claims a domain first and then points it at something, or picks a domain in the middle of creating a site, decides the shape of all of them, and whether a member can hold a domain before there is anything to serve at it. ## Options known so far - Keep domains inside the site flow and rework the chooser alone. - Split the surfaces the way the registry is split: claiming a domain is its own act, and serving a site at a domain is a second act reachable from either side. ## Decided when The domains model states what a member holds and what a member points at, and the member and operator surfaces present that split. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/domains area/fedwiki area/member-ui labels 2026-09-21 07:18:11 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#34