# Site settings The Site settings tab of the admin page, `/admin/site`, is where the operator chooses what this site shows without touching the chain: the alpha strip, an announcement, featured and hidden DAOs, verified and hidden tokens, the home page's texts for search engines, links, analytics, the RPC endpoints and the block explorer. This page describes every field: what it changes on the site, its label on the tab, the rules it must follow, and an example. ## How the settings work The settings live in one file on the server, `/var/www/collab/shared/site.json`. The tab shows them in seven cards: **Notices**, **DAOs**, **Tokens**, **Search engines**, **Links**, **Analytics** and **Network**. Each card has a preview, **On the site**, of what the change looks like, and a badge when it holds changes (**Changed**) or problems (**… to fix**). Every field is checked as you type, with the same rules the server applies, and checked again by the server when you save. A field the server refuses is marked with the server's message. Saving changes nothing on chain. It changes what this site shows, and only this site: other copies of COLLAB, GL1X and wallets are not affected.  ## Saving The save box beside the cards, **Site settings**, shows the state: "Everything is saved", "Unsaved changes in Notices, DAOs", or "… fields to fix before saving". **Save changes** sends the whole form; **Discard changes** goes back to what the server has. Leaving the page with unsaved changes asks first. After a save, the box says when, and what follows: "config.js carries the settings now, and pages show them on their next load. The static pages follow at the next prerender run, which was requested." So a change reaches visitors in two steps: - **At once:** `config.js` is rewritten. Every page reads it on its next load and applies the alpha strip, the announcement, the links, featured and hidden DAOs, verified and hidden tokens, the RPC endpoints and the explorer. - **At the next prerender run** (requested by the save, usually within seconds): the prerendered copies of the pages, which carry the settings in their HTML for the first paint and for search engines, the home page's search-engine texts, the sitemap, the token list file and the member network. If someone saved other settings meanwhile, the box says "The settings changed on the server meanwhile." Saving would replace them with this form; **Load them instead** discards your changes and loads theirs. The server keeps the version each save replaces in `shared/history/` (the newest 50). The file's format is in [Data formats](data-formats.md#site-settings). ## When a setting changes the security policy Every page carries a Content-Security-Policy that lists what it may load and connect to. Two settings change it: an analytics ID, and the RPC endpoints. The admin service cannot write the pages or nginx's configuration itself; after the save it asks root's content policy step to do it: 1. `collab-apply.path` sees the request and starts `collab-apply.service` (`collab apply`, as root); 2. the step checks every value of `config.js` again, writes the new policy into the release's pages and COLLAB's own nginx file, tests nginx with `nginx -t` and reloads it; 3. when nginx refuses, it puts every file back and records why; 4. it asks for a prerender run, so the prerendered pages carry the new policy too. The save box and Status show the policy's badge as the step goes: **Updating** for a few seconds, then **In step**, or **Update failed** with nginx's reason. `sudo collab apply` runs the step by hand and prints what it did ("policy applied: 15 file(s) updated" in the release rehearsal, after a GA4 ID was saved). See [INSTALL.md, section 6](INSTALL.md#6-site-settings-and-the-content-policy). ## Notices The **Notices** card: "COLLAB says on every page that it is an alpha; the text is yours to word. An announcement reaches every visitor at once." ### The alpha strip | Key | Label | Rules | |---|---|---| | `alpha.show` | **Show the alpha strip at the top of every page** (a switch) | true or false; true by default | | `alpha.text` | **Alpha strip text** | plain text on one line, at most 200 characters; empty means the standard text | The strip is the dark band at the very top of every page: an **Alpha** tag, the text, and a link to the security notes. Switched off, pages start with the top bar. The **Alpha** badge beside the COLLAB wordmark stays either way. The standard text is "Alpha: COLLAB runs on GenesisL1 mainnet and has had no external audit. Use small amounts." The strip shows it without the leading "Alpha:", since its tag already says so; a text of your own that starts with "Alpha:" (or "Alpha." or "Alpha -") is shown the same way. ```json "alpha": {"show": true, "text": "COLLAB runs on GenesisL1 mainnet and has had no external audit. Use small amounts."} ``` ### The announcement | Key | Label | Rules | |---|---|---| | `announcement.text` | **Announcement** | plain text on one line, at most 300 characters; empty for none | | `announcement.href` | **Its link** | optional: an https address, or a path on this site that starts with `/` | | `announcement.tone` | **Tone**: **Information** or **Warning** | `info` or `warn` | The announcement is one line under the top bar of every page, with an information or a warning icon, and **Read more** when it has a link. A path such as `/votes` opens on the site; an https link opens in a new tab. **Remove the announcement** clears all three fields. A link without a text is refused: "Write the announcement, or clear its link." From the release rehearsal: ```json "announcement": {"text": "Open Proteomics Lab launched OPC: see it on the tokens page.", "href": "/tokens", "tone": "warn"} ``` ## DAOs The **DAOs** card: "Hiding changes nothing on chain: it only decides what this site lists. A DAO is either featured or hidden." Type a DAO's web address (its slug), or paste the address of its page (`https://…/dao/`), and press the card's button. Each entry is looked up on chain and shows the DAO's title and slug, or why it could not: "No DAO with this name on this deployment yet. It applies if one is created." or, before a deployment is published, "Looked up once COLLAB is deployed here." ### Featured DAOs | Key | Label | Rules | |---|---|---| | `featuredDaos` | **Featured DAOs**, button **Feature** | up to 24 slugs, in the order shown; no DAO twice; none of them hidden | The home page shows up to six featured DAOs, in this order, under "Featured DAOs", in place of the six largest by members that it shows under "DAOs on COLLAB" otherwise. Use the arrows to change the order. Tokens launched by a featured DAO count as verified on the tokens pages ("Issued by a DAO this site features"). A slug has 3 to 48 lowercase letters, digits and hyphens, starts with a letter, has no double hyphen and does not end with one. Featured DAOs are named by slug only. ```json "featuredDaos": ["open-proteomics-collective", "longevity-data-commons"] ``` ### Hidden DAOs | Key | Label | Rules | |---|---|---| | `hiddenDaos` | **Hidden DAOs**, button **Hide** | up to 1,000 slugs or treasury addresses; none of them featured | A hidden DAO is left out of the DAOs directory, the search, the home page, the sitemap and the member network. The directory says how many: "This site leaves 1 DAO out of its lists." Its pages stay open to anyone with the link, with a notice, "Hidden on this site. Its operator leaves this DAO out of the directory, search and the sitemap. Its pages stay open to anyone with the link, and nothing about it changed on chain.", and they ask search engines not to index them. A treasury address is `0x` and 40 hexadecimal digits, not zero, with a right checksum when written in mixed case. It is stored in lowercase. The DAO hidden in the release rehearsal, by its slug and by its treasury address (one of the two is enough): ```json "hiddenDaos": ["quiet-assay-circle", "0x187b085f8854c58943682cddd5a5acd68c438a48"] ``` ## Tokens The **Tokens** card: "Verified tokens carry a badge on the tokens page and in swaps, so buyers can tell them from look-alikes. Hidden ones are left out of listings." Type a token's address, or paste the address of its page (`https://…/tokens/0x…`). Each entry is looked up on chain and shows the token's symbol and name, or "No token contract at this address on this chain." ### Verified tokens | Key | Label | Rules | |---|---|---| | `verifiedTokens` | **Verified tokens**, button **Verify** | up to 1,000 token addresses; none of them hidden | A verified token gets a check mark beside its symbol on the tokens list ("Verified by this site's operator"), **Verified by this site** on its page and in the swap ticket, and **Verified** in the swap's token picker; the warning that it is not verified goes away. wL1 is always verified, as part of the deployment, and so are tokens launched by a featured DAO. Verify only tokens whose contract address you have checked with their issuer: anyone can create a token with any name or symbol. The token from the release rehearsal: ```json "verifiedTokens": ["0x01120971d58403594875afffe0efc4e4f4607195"] ``` ### Hidden tokens | Key | Label | Rules | |---|---|---| | `hiddenTokens` | **Hidden tokens**, button **Hide** | up to 1,000 token addresses; none of them verified | A hidden token is left out of the tokens list, the swap picker's list, the pools list, the search and the sitemap. Its exact address still finds it, and its page stays, with a notice ("This site hides … from its lists. … Nothing changed on chain: the token and its pools work as before.") and asks search engines not to index it. Addresses follow the rule of treasury addresses above, and are stored in lowercase. Each entry is a full `0x` address of 40 hexadecimal digits: ```json "hiddenTokens": ["0x…"] ``` ## Search engines | Key | Label | Rules | |---|---|---| | `seo.title` | **Title** | plain text on one line, at most 70 characters; empty means the standard title | | `seo.description` | **Description** | plain text on one line, at most 200 characters; empty means the standard one | "The home page's title and description, which search results and link previews show." The hints say what reads best: about 50 to 60 characters for the title, and 120 to 160 for the description. The standard title is "COLLAB | Scientific DAOs on GenesisL1". These two go into the home page's `