> For the complete documentation index, see [llms.txt](https://docs.morpht.com/convivial-for-govcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpht.com/convivial-for-govcms/theme-settings/site-wide-settings.md).

# Site-wide settings

Below the skins are settings that apply to the whole site. Most are set up once by a developer; the ones a Themer may need are:

* **Chart colours** — the default series colours for Chart components, as hex codes separated by spaces.
* **External links** — style external links, open them in a new window, and optionally show a pop-up message when leaving the site, with a regex of domains that trigger it.
* **Import redirects** — paste a two-column CSV of `source,destination` paths to create redirects in bulk.
* **Look and Feel** — apply a "look" (a bundle of modifiers) to pages by context rather than one page at a time; see below.
* **Meta** — extra meta tags built from page fields; see below.
* **Schema.org**, **Prefetch**, **ReadSpeaker**, **Convivial profiler**, **Matomo**, **Recombee tracker** — integrations; leave to your developer.

![External links](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-9a3d7a7cc2f90dcfad7c6699a6aba1f9779887d6%2Ftheme-external-links.png?alt=media)

## Look and Feel

Look and Feel applies a look — a set of modifiers such as a background or palette — to whole areas of the site based on what page is being shown, instead of an editor setting it on each page. Tick **Enable Look and Feel**, then configure:

![Look and Feel settings](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-3c29ede82206f174bc6e64e8e94c8f9fd5d844e8%2Ftheme-laf.png?alt=media)

* **Field selectors** — one `field|selector` mapping per line, saying which field on the looked-up entity holds the modifiers.
* **Complete strategies** and **Partial strategies** — one `strategy|parameters` rule per line, evaluated in order. *Complete* applies only the first matching look; *Partial* applies every matching look.
  * `entity|node,taxonomy_term` — take the look from the page's own entity.
  * `reference|field_section` — take it from the entity in that reference field, e.g. the page's Section.
  * `path|/section/*,taxonomy_term,section-a` — when the URL matches, use the look with key `section-a` from the taxonomy terms.
  * `apply|taxonomy_term,section-a` — always use the look with key `section-a`.

## Meta

The Meta feature emits extra `<meta>` tags from page values, one rule per line in the form `strategy,key,params,attributes,bundles`:

![Meta settings](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-94c11f8c09b4bb39ce619b24dd300e1e157c9134%2Ftheme-meta.png?alt=media)

* `constant,site,alpha` — a fixed value.
* `bundle,type` — the page's content type.
* `values,summary,field_summary` (or `value,…` for a single string) — a field value.
* `references,topic,field_topics|field_identifier` (or `reference,…`) — a field from a referenced entity.
* `token,type,[node:content-type]` — a token.

Add `attr1=x|attr2=y` to set extra attributes and `page|article` to limit the tag to those content types, e.g. `token,topic,[node:field_topic],,page|article`.