You can use the
php please multisite to automate converting from a single to a multisite installation.
When using multiple sites, you'll need to specify in the globals's YAML file which sites this collection can be used in.
# content/collections/blog.yamlsites: - en - fr
The folder structure will differ from the single site structure explained in the globals guide. Now, the
data will be relocated into separate files organized into sites. The meta level information will remain in the existing YAML file.
globals/ global.yaml footer.yaml english/ global.yaml footer.yaml french/ global.yaml footer.yaml
In these nested files, the data can exist at the top level.
# english/global.yamlfood: bacondrink: whiskysport: football
# french/global.yamlorigin: englishfood: baguettedrink: champagne
A global set will be considered unavailable for a particular site if a file doesn't exist in its subdirectory.
In a Blueprint, you can define which fields are localizable.
While editing a localized global set, only the localizable fields will be editable. The non-localizable fields will be read-only.
A localized global set should reference the origin. In the example above, the french set originates from the english, so the
sport variable will be inherited.