Recently I stepped into a few engagements to assess and evaluate how CQ/AEM was implemented for customers, be the implementation done by in-house developers, or via a solution partner. Since the “health check” area is a little vague, I want to use this post to list some of the exercises usually covered by such engagements. Note that some of the following might not necessarily be covered in all engagements, it varies depending based on customers needs and time given.
- Study the solution via written documentation or direct interviews with customers and system integrators.
- Review user interface, identify opportunities to optimize the performance for various experiences (web, mobile, kiosk, etc.)
- Review CQ authoring process and work with customer to streamline and optimize the authoring experience.
- Provide general performance optimization strategies including but not limited to: caching, use of CDNs, delivering the right fidelity assets at the right time, etc.
- Provide general architectural guidance (Gap analysis between reference architecture and customer’s implementation) and environment audit.
- Provide development and deployment best practices, including but not limited to:
- Review templates and components for reusability.
- Review information architecture.
- Review OSGi configurations.
- Review build and package management tools, source control being used, etc.
- Code review and scoring using code analysis tools.
- Validate the application of security checklist and go-live checklist.
At the end of the exercise, Adobe Consulting Services will compile and consolidate all the information collected, and will provide a document on all the findings from the engagement as well as suggestions and next steps.
Healthcheck is usually carried out onsite, and it typically lasts from a few days to a few weeks.