The Resource Status for Editors framework provides server-side and client-side APIs for displaying and interacting with editor statuses, in a standard and uniform manner.
The editor status bars are natively available in the Page, Experience Fragment and Template editors of AEM.
Example use cases for custom Resource Status Providers are:
- Notifying authors when a page is within 2 hours of scheduled activation
- Notifying authors that a page was activated within the past 15 mins
- Notifying authors that a page was edited within the last 5 mins, and by whom

When developing custom Resource Statuses, the develop work is comprised of:
- The ResourceStatusProvider implementation, that is responsible for determining if a status is required, and the basic information about the status: title, message, priority, variant, icon, and available actions.
- Optionally, GraniteUI JavaScript that implements the functionality of any available actions.

-
The matching ResourceStatusProvider is passed the resource in the editor, and determines if the resource has status to be displayed. If status is needed, this implementation is responsible for building 0 or many ResourceStatuses to return, each representing a status to display.
Typically, a ResourceStatusProvider returns 0 or 1 ResourceStatus per resource.
-
Optionally, if Actions are provided for the ResourceStatus object, supporting clientlibs are required to bind functionality to the action links int he status bar.
(function(jQuery, document) { 'use strict'; $(document).on('click', '.editor-StatusBar-action[data-status-action-id="do-something"]', function () { // Do something on the click of the resource status action }); })(jQuery, document);
-
Any supporting JavaScript or CSS to support the actions, must be proxied through each editor's respective client libraries to ensure the front-end code is available in the editor.
- Page editor category: cq.authoring.editor.sites.page
- Experience Fragment editor category: cq.authoring.editor.sites.page
- Template editor category: cq.authoring.editor.sites.template