Downloads
The files the guides tell you to take. Start with the sample package: it is a working folder, so you can put your own hosts in it and host it as it stands.
aem-
toolbar- sample- package. zip A complete package: a manifest named so the extension offers to import it, plus the four configuration files it points at. Unzip it, put your own hosts in environment-config.yaml, and host the folder.
The package manifest on its own. Rename it to end in .aem-toolbar.json when you build your own package: that suffix is what makes the extension offer to import it.
config/
environment- config- template. yaml A worked environment config with placeholder hostnames, a site using stripPath and coloured environments. This is the file you edit.
config/
environment- config. yaml The bundled default the extension ships with. Deliberately empty: no authors, sites or environments are configured until you say so.
Bundled default: the quick links each screen gets, with their URL templates.
Bundled default: the contextual messages, with every assertion operator documented inline.
Bundled default: the URL patterns that tell one AEM screen from another.
The configuration files are the defaults the extension ships with. Import them through the options page, or host them yourself as part of a team package. For a team or org explains what to do with them, and Configuration is the reference for what is in them.