Relay collections, published assets and your own domain
Help centers get nested collections with their own pages, files from a chat can be shared at a public link, and every site can run on your domain.
Relay, the hosted home of a project's content, learned a lot this week.
Collections with their own pages
A help center's collections can now nest, and each has a page of its own: an icon, a name, a description, an introduction, and then everything inside it. Readers get an "All collections" crumb to walk back up. Collections are edited from the nav in Relay and come from the folder layout when the help center is synced from files (_100_getting-started/index.mdx is the collection's own page).
Drafts on published articles
Editing a published article in Relay no longer changes what readers see straight away. Changes are held in a draft until Publish changes; Discard changes drops them. Control Panel keeps seeing the published version meanwhile.
Published assets
A file Claude produced in a task — an image, a video, an HTML page, a PDF or a Markdown document — opens in a viewer from its preview in the chat, with Open file, Show in Finder and Publish. Publishing puts it at content.paralect.app/<slug>: documents are rendered like a Relay article, anything else is served from the CDN. Assets in project settings lists everything published, with its link and an Unpublish button.
Your own domain
A Relay project's sites live at <slug>.paralect.app/<path> by default. Set a domain in the project's settings and point a CNAME at Vercel, and help.example.com serves the same pages. Custom CSS and <head> scripts apply on the project's own host only; on Relay's host the pages render with them stripped.