Step 8: Put it at your own address
One CNAME, and the one state that actually serves.
A published wiki gets an address the moment its world claims one — <slug>.vvd.world.
Eventually somebody wants it at wiki.theirdomain.com instead. That's one DNS record and a
wizard, not anything in your bundle.
No live preview here either. DNS, verification and SSL all happen outside this browser tab, against real infrastructure. This is the honest shape of the flow, not a simplification of it.
Open the wizard
Behind the gear at the end of the address field in the publish panel, or the world's Site & domain settings. Only world editors can manage domains.
Type the hostname
wiki.example.com— normalised to lowercase. You can't claim a hostname vvd already owns (anything onvvd.worldorvvd.sh).Add the DNS record
Field Value Type CNAMEName wiki.example.comTarget vvd.worldThen press I've added it — verify.
Wait for active
The row moves
pending→verifying→active, SSL tracked separately. Onlyactiveserves — a domain inpendingorverifyingis saved but not live, and the panel keeps the open site action pointed at the address that genuinely works.
A world holds one custom domain; removing it falls back to the .vvd.world subdomain
and leaves your published editions untouched. Most DNS providers can't put a CNAME on a bare
apex (example.com) — use a subdomain unless yours supports ALIAS/flattening.
Reference has the full error table — taken hostnames, propagation delays, the "editors only" message — for when it doesn't go straight through.
What you built
A wiki that reads a whole world with no content of its own, wears a theme from a shared catalog, lets its owner arrange the page without touching your code, and publishes to a real address — the same shape as the two templates vvd ships.
Recap
- A custom domain is one CNAME at
vvd.world; only anactivedomain serves. - One per world — removing it falls back to the subdomain and leaves your editions untouched.