Serves "Build a site for ", "make an event website" and "start a site from " (the url gives layout only), not the host's own page tools. Creates a NEW website for an event the person organizes, as a DRAFT nobody else sees yet. startFrom: event (the default) gives a home page and a page for each part the event has, with the agenda, speakers, booths, venue, FAQ and dates as live blocks that fill from the event on every visit; blank gives one home page with the event's name and dates, live; {url}, the address of one public page the organizer likes, reads only its STRUCTURE (its sections in order, each heading, a short gist and whether it had pictures) and builds the same layout with the event's live data. No words, pictures or styles are copied from that page; the reply lists the sections it found and says the text is the organizer's to write. title names the site. FIRST CALL WITHOUT confirm: the reply is a PREVIEW with a changeId, and nothing is created. Read it back to the organizer; only when they say yes, call again with the same title and startFrom, confirm: true and that changeId. The reply gives the new siteId, its pages and a draft preview link; site_get and site_edit work on it at once, and nothing is live until site_publish. An event holds at most 20 sites. Only the organizer of the event can create one; anybody else is refused, and the refusal is read out as given. It needs a personal connector token. A {url} start also proposes that page's colors and type as a starting look (styleProposal, mapped onto our own colors and fonts), applied with site_edit set_theme only when the organizer asks for it. Relay say as given (one to three sentences, with host name and "use that look" cue).