Running it
Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.
The part of an application that is not a conversation. Ten pages: one per section of Settings, plus the three things that are not settings at all — the files your application publishes, the records it has stored and the visitors it counts.
Most of this can also be asked for in the conversation. The builder puts it in Settings rather than in the code, which is the right place for it — a page title written into the source is work somebody has to undo, and the next build would overwrite it anyway.
- Addresses and domainsThe address an application gets, and how to put it on a domain you own.
- Who can reach itOpen, behind one shared password, or accounts — and why the choice is enforced in front of the application.
- People who sign inThe workspace's user directory — adding the people who use your applications, which ones each may open, what you can keep about them, and two-step sign-in.
- Published filesDocuments your application hands to its users — a price list, a brochure, a form — with a stable address and no build to change them.
- IntegrationsEmail, SMS and Google — connected once, used by the application without it ever holding a credential.
- AppearanceThe browser tab, the icon, what a link looks like when somebody pastes it, and adding it to a phone's home screen.
- Redirects and search enginesOld addresses that still get visited, and what crawlers are told about each environment.
- Configuration valuesNamed values the application needs but must not contain — API keys, account numbers, thresholds.
- Your dataThe Data tab — reading, correcting, adding to and clearing out what your application has stored, one environment at a time.
- VisitorsWho is using the application, counted without identifying anybody and with nothing to set up.