Just for me

Nothing to host and nobody to ask. You need your AEM author URL and your public site URL.

1. Install it

   Install from the Chrome Web Store, then click the extension icon and choose Full Extension Settings.

2. Add your instance

   Go to Configuration, then Environments, then + Add Environment, and fill in four fields.

   • Author host. Your AEM author instance, such as author.acme.com. A bare hostname implies https; an instance on http or a non-standard port needs its full origin, such as http://localhost:4502.
   • Site key. The site’s folder name under /content in AEM, so acme for /content/acme/....
   • Public host. The domain the site is live on, such as www.acme.com.
   • Strip path. The path segment that is in the author URL and not in the public one, such as /en. Leave it blank if there isn’t one.

   Strip path is the one people get wrong. If /content/acme/en/products.html is published at www.acme.com/products, then /en is the segment to strip. If your public URLs keep the language code, leave it blank.

   Repeat for staging, development and your local SDK if you have them.

3. Open an AEM page

   The toolbar appears as a small rail with a coloured badge, and the extension icon shows a green ON. Press View Live. If it lands on the right page, you are finished. If it lands on a 404, the strip path needs adjusting.

What you get with no further configuration

On a page in the AEM editor:

prodPage editor

• View Livehttps://www.acme.com/products/kettles
• Page Propertieshttps://author.acme.com/mnt/overlay/wcm/core/content/sites/properties.html?item=/content/acme/en/products/kettles

On the published page, the return trip and three more:

prodPublished page

• Edit Pagehttps://author.acme.com/editor.html/content/acme/en/products/kettles.html
• Page Propertieshttps://author.acme.com/mnt/overlay/wcm/core/content/sites/properties.html?item=/content/acme/en/products/kettles
• Open Enclosing Directoryhttps://author.acme.com/sites.html/content/acme/en/products
• Show Asset LinksPuts an edit link on every image that resolves to a DAM assetOverlays on the page itself

On any author page the toolbar also asks the instance which content fragments the page uses, and adds a row listing them. A page that uses none gets no row.

If it does not appear

The toolbar renders on hosts you have configured and nowhere else, so an absent toolbar is nearly always the host entry.

• Check the form of the entry. A bare hostname such as author.acme.com matches any scheme and port. An instance on http or a non-standard port needs its full origin, such as http://localhost:4502. A port with no scheme, such as localhost:4502, is ambiguous and is ignored.
• Check the site key matches the folder name under /content.
• Check the public hostname is listed under that site if the toolbar is missing on the live page only.
• Check which editor you are in. The toolbar works in AEM’s classic Touch UI editor. In the Universal Editor it stays empty whatever you configure, and the FAQ explains why.

More of these in the FAQ.

Next

• Configuration is the reference: path transforms, page property tokens, environment colours, and where configuration comes from.
• Worked examples show four estates, the configuration each one writes, and the URL every toolbar row opens.
• Setting it up for a team turns your configuration into something your colleagues install with one click.