Site metadata
Each Site carries metadata that tailors Flowpane's guidance and helps you organise your portfolio.
Fields
| Field | Description | Auto-detected? |
|---|---|---|
| Site name | Display name from og:site_name, application_name or <title> |
Yes |
| Platform | Your declaration of the CMS or framework | Observed independently; never overwritten |
| Audience | Target market region | Inferred from declared language and locale, then the domain ending |
| Industry | Business sector, from a list of about 150 options | No |
| Tags | Free-text labels, up to 10 | No |
| Site capabilities | What the site does: advertising, e-commerce, payments, accounts, apps | No |
Setup modal
The first time you open a Site, a modal shows the detected values. Review, correct, select the industry and optionally add tags, then click Confirm. The modal appears once per Site.
Editing later
Click Edit (pencil) in the Site header to change name, platform, audience, industry and tags. Site capabilities and the AI content preference are in Site settings → General. See Site settings.
Why metadata matters
- Platform tailors bounded guidance when your declaration and Flowpane's observation are compatible. It does not prove that a plugin manages an artefact. Joomla and WordPress connections are supported in reviewed environments; access and management depend on the Site entitlement and current capabilities. See Platform detection.
- Audience is presentation context. It is not a determination that any law or standard applies.
- Industry helps prioritise which governance artefacts matter most.
- Site capabilities decide which artefacts are required, recommended or not applicable for the Site, which changes how a missing artefact affects the Site score.
- Tags help you group Sites, for example "priority" or "client-acme".