Skip to content
AEM Editorial Toolbar

An engine that knows your AEM setup, so your editors don’t have to.

This is a browser extension for AEM authors, developers and administrators. It puts the editor, the DAM asset, site admin and the page's own properties one click away, and it makes no request to its author or to any third party.

Install for Chrome

prodOne page, two addresses

You are hereauthor.acme.com/editor.html/content/acme/en/products.html

View Live opens

www.acme.com/products

and Edit Page brings you back

Two ways in

Both start with the same install. They part company at the point where you decide whether the configuration is yours alone or your team's.

Just for me

Nothing to host, nobody to ask. Two minutes.

  • Install it
  • Name your author and public hosts
  • Open an AEM page
Start

I am setting this up for a team or org

One person describes the estate once. Everyone else clicks a link and is done, and stays up to date on a schedule.

  • Get it right for yourself first
  • Write the configuration once
  • Put it in a package
  • Host it, including somewhere only your company can reach
  • Send two links to the team
Plan a rollout

What it does

Section titled “What it does”
Names the environment
A coloured badge on every AEM screen and on the live site, in the colour you gave that environment.
Both directions
View Live from the editor, Edit Page from the published site. The same mapping drives both, so the round trip lands where it started.
Lists the content fragments
On an author page, each fragment the page uses becomes a link into its editor. Nothing to configure.
Reads the page’s own properties
A link or a warning can be built out of a property your team already sets, so a convention becomes a toolbar row with no AEM code change.
Finds the DAM asset
Turn on asset links and every image that resolves to a DAM path gets an edit link into AEM.
Never blocks the page
The toolbar renders straight away. A slow or unreachable instance costs you rows, never the toolbar.

Production is red

Section titled “Production is red”

The badge is the part editors notice first. It reads the environment key you chose, in the colour you gave it, on every page the toolbar recognises. Leave the colours out and it assigns these four in the order your environments appear.

prodRed, so nobody edits it by accident
stageOrange, for the tier the business signs off on
devGreen, for the instance the developers hold
localBlue, for the AEM SDK on your machine

What it does not do

Section titled “What it does not do”

No accounts, no analytics, no telemetry, no third-party servers. The only requests it makes are to your own AEM instances, carrying the session the editor already has, and, if you set one up, your own configuration URL.

Read the privacy policy for the detail, or the FAQ for the questions an IT reviewer usually asks.