Groups

Put related sites in one folder and they share all of their automation. A duplication master, a navigation, or a collection of data records defined on any site in the group is visible to every other site in it. Each site still deploys to its own domain — the grouping is only for the automation and sync on your machine; the server and hosting are untouched.

How it works

Under your content root, a top-level folder whose name contains a dot is a site (its name is the hostname). A folder whose name has no dot is a group: the sites inside it are its members. Every hostname has a dot and a group label doesn’t, so the two never clash — no config needed.

sites/
  gpu/                 # a group (no dot in the name)
    gpu.org/           # member → deploys to gpu.org
    uk.gpu.org/        # member → deploys to uk.gpu.org
    _shared/           # data-only source (see below), never served
  example.com/         # a standalone site (a group of one)

On sync, members are flattened back to top-level domains: gpu/gpu.org uploads and serves exactly as gpu.org did before you moved it in. Moving a site into a group changes nothing about how it is hosted.

What gets shared

Within a group the automation is pooled into one namespace:

Links stay correct. A record shown on the site it lives on keeps its plain path (/news/…); shown on a different member it becomes an absolute link to the site it belongs to (https://uk.gpu.org/news/…).

What it’s for

Two common shapes:

Data-only sources

Inside a group, a folder whose name has no dot (or begins with _) is a data-only source: its records are read into the group’s collections, but it is never synced or served. It’s a canonical home for shared data that has no page of its own — a master list that several member pages draw from, or translation strings you filter onto different sites.

Next steps