building quality into the aem publication workflow with active standards by dan hanley and david...
TRANSCRIPT
Building Quality into the AEM Publication Workflow
With
Who are you guys then?Dan HanleyCTO, ActiveStandards
David PeadDeveloper, ActiveStandards
Our Company
• Specialists in Digital Governance & Compliance• Delivering technology and consulting solutions to global
enterprises• Clients include: Shell, Unilever, HP, Oracle, Canon…
• Our technology platform & AEM connector
• Live demo• Lifting the hood• Roadmap & extensions
Agenda
Our PlatformA central point of visibility and control for digital quality & compliance
• Scans enterprise websites against a set of “checkpoints” – digital rules representing a company’s online compliance standards• Best practice checkpoints (e.g. WCAG 1.0 and 2.0 /
Section 508 Accessibility, SEO, Usability, Mobile Web)• Companies’ unique brand and business rules (e.g.
fonts, colours, corporate terminology and editorial standards)
• Comprehensive reporting on quality and compliance issues
• Suite of tools to help editors find and fix the detected issues
Online DashboardScans entire web presence and ensures quality and compliance of live sites.
AEM ConnectorONE-click page validation within the AEM environment ensures errors are caught and fixed pre-publication.
LIVE WEBSITES
Adobe Experience Manager
Where does our AEM Connector fit?
Live demonstration
1
ActiveStandards API
ActiveStandards Connector
AEM
Front End
ActiveStandards AEM Connector Overview
GET/service/
activestandards
POST /assets
Asset (JSON)
1 2
Assets: Decorator FilterWhich issue is where?
• Page passes through filter
•Unique <div> tags are added
• Logic in filter controls mark-up
• Passed as asset to API
ActiveStandards API
ActiveStandards Connector
AEM
Front End
ActiveStandards AEM Connector Overview
GET/service/
activestandards
POST /assets
Asset (JSON)
1 2
Get /assets/{assetID}/status
Checkpoints (JSON)
3
Status endpoint
• Asset• Checkpoi
nt• Results
ActiveStandards API
ActiveStandards Connector
AEM
Front End
ActiveStandards AEM Connector Overview
GET/service/
activestandards
POST /assets
Asset (JSON)
1 2
Get /assets/{assetID}/status
Checkpoints (JSON)
3
Get /assets/{assetID}/errors/{checkpoin
tID}Issues (HTML)
4
Optional parameter of highlightSource.If true, will return “source view” (right)• HTML returned
• data-ast-issue=“true” attribute
• embedded highlighting style, if required
• mark-up re-writing is controlledby within our platform
Error endpoint: HTML returned from assetID & checkpointID
ActiveStandards API
ActiveStandards Connector
AEM
Front End
ActiveStandards AEM Connector Overview
GET/service/
activestandards
POST /assets
Asset (JSON)
1 2
Get /assets/{assetID}/status
Checkpoints (JSON)
3
Get /assets/{assetID}/errors/{checkpoin
tID}Issues (HTML)
4Validation errors
(JSON)
5
• Mashery made• API key gives access to a client’s website listing• Website example
• Checkpoints• Assets – As we’ve seen– In addition, options to retrieve asset details,
content, run a spell check or finds relatedassets based in websiteID
ActiveStandards API: dev.activestandards.com
Configuration: OSGi Bundles
Decorator FilterDefine the root against which componentswill be validated
Validator Service– API key, access to clients ‘context’
i.e. website listing– Website ID, ties validation to specific
checkpoint ruleset
Code Review 1: Client Libs
ActiveStandards.base.js
ASTIssueRenderer.js
ActiveStandards.componentListener.js ActiveStandards.injector.j
s
Code Review 2: Key Java Classes
‘Main’ package
‘Loader’ package
‘Service’ package
‘Model’ package
• Touch UI• Custom checkpoints per website • Workflow events• Permissions – making the connector
only available to specific websites or users
Roadmap & ExtensionsActiveStandards AEM connector scoops 'Industry Game-Changer' award at Adobe Summit EMEA 2015activestandards.com/adobe_gamechanger
For more information contact:Dan Hanley, CTO, ActiveStandardsT +44(0) 20 7019 [email protected]
Questions?