Every site, with a way to open both its stages.
The launcher is for tools. The Websites tab is for the sites those tools and their makers publish: one card each, with the production address, the staging address, and the key that unlocks staging. It is the same registry document as the launcher, so a new site appears the minute an operator publishes it.
A tab per group
Sites are grouped by a category in the registry, and each group is a tab with a count. All is first and lists every site under a divider for each group; the other tabs show one group each. The tab you leave on is remembered in your browser, and a group that has since gone falls back to the first tab. A new category in the registry becomes a new tab with no deploy.
Every signed-in person sees the whole tab. It is not filtered by the grants on the Access screen.
Cards
A card has the site's name, a short description, and a Production button and a Staging button, each opening in a new tab. A stage the site does not have is shown disabled. Under them, a site with a staging stage carries its staging access key, masked, with one control to reveal it and one to copy it; the Staging button already has the key applied, so you are let in without typing it.
Each card's preview is a screenshot of the site, one taken in light mode and one in dark. The card shows the one that matches your theme, falls back to the other if one is missing, and falls back to the site's initials on a gradient if there is none. A script shoots them and records when, so a re-shot preview is never served from an old browser cache.
| Production | The site's live address. Opens in a new tab. |
|---|---|
| Staging | The preview address, with the access key applied. Disabled when the site has no staging stage. |
| Access key | A shared secret for that one site's staging stage, not a password for a person. Masked until you reveal it. Aerie reads the keys from the registry; it never makes or rotates them. |
One registry document
The tools on the launcher and the sites on this tab live in a single JSON file kept in the Aerie repository, so changes are reviewed like any other. An operator publishes it to a private storage bucket, and the running backend polls it every minute with a conditional request and updates its records when the file changes. Registry edits need no redeploy.
A broken or unreachable document never takes the launcher down: the last good one keeps serving. The fields the document owns overwrite what is stored, so a status flipped to coming soon reaches every tile on the next refresh.
Editing the registry from inside Aerie is not built: the Admin screen manages people and grants only, and the registry is one JSON document that an operator publishes.
Questions about this tool?
Write to Renkara Media Group and a person will answer.