Grouping

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/
  example/             # a group (no dot in the name)
    example.com/       # member → deploys to example.com
    uk.example.com/    # member → deploys to uk.example.com
    _shared/           # data-only source (see below), never served
  example.net/         # a standalone site (a group of one)

On sync, members are flattened back to top-level domains: example/example.com uploads and serves exactly as example.com 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:

Duplication: a duplicate master on one member fills its copies on every member. Define the footer once, on any site, and share it across the whole group.
Navigation: a navigation master is shared the same way, each copy still highlighting its own page. One menu across a family of sites.
Data: records from every member are merged into their collection, so a listing or count on one site can draw on records that live on another.

In a duplicated block, a relative link resolves to whichever site the copy sits on. Use an absolute link if you always want it to point back to one specific site.

What it’s for

Two common shapes:

Regional / translated subdomains: example.com, uk.example.com, de.example.com under one example/ folder, sharing a footer and navigation while a UK page can list the German page and vice-versa.
Separate domains, one project: frontends.com and frontends.net under one frontends/ folder, kept in step without copying markup between them.

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.