AEM Architecture and Consulting
I'm an Adobe Certified AEM architect with 13+ years in CMS and full-stack engineering, 10+ of them on Adobe Experience Manager. At Credera (formerly TA Digital) I worked my way from senior full-stack engineer to technical lead, principal engineer and technical architect. Along the way I built 10+ enterprise AEM platforms from scratch and won the STAR Award three times, plus several Spot Awards.
I write the code myself: Java, OSGi, Sling, JCR and Dispatcher on the back end; React, Angular, Lit and Tailwind on the front end. The designs I hand over are ones I've built and run in production.
What I do
1. AEM as a Cloud Service migration
Moving from on-prem AEM or Adobe Managed Services to AEM as a Cloud Service changes how you build and deploy.
- Readiness assessment: run the Best Practices Analyzer (BPA), then rank what has to change: incompatible patterns, deprecated APIs, custom replication agents.
- Code refactoring: split
/appsand/libsfor the immutable repository, move to OSGi R7 configs and modern Sling Models. - Cloud Manager CI/CD: pipelines, quality gates, security scans, and custom automation through the Cloud Manager APIs.
- Cutover: phased content sync, Dispatcher converter rules and a CDN switch-over, so authors keep publishing throughout.
2. Adaptive Forms and self-service portals
- Multi-step application flows built with AEM Adaptive Forms and the GuideBridge API, such as admission portals and document intake, designed so new panels and rules plug in easily.
- Identity and signatures: Jumio for ID and document checks, DocuSign for e-signatures.
- Self-service dashboards where students and customers track their application, upload documents and fix problems without calling support.
3. React and headless AEM
- React in AEM: React code kept in its own repositories and pulled into the AEM archetype build, shared across brands such as Capella and Strayer.
- Drag-and-drop components: AEM components wrapping React, with authoring dialogs so marketers build pages without developer tickets.
- Headless content: Content Fragments, Experience Fragments and persisted GraphQL queries served to Next.js with SSR and on-demand ISR.
4. Enterprise integrations
- Middleware and ERP: MuleSoft, PeopleSoft, Axway and Perceptive.
- Offline fallback: when PeopleSoft is down for maintenance, applications are stored in MongoDB and a message queue, then synced back automatically once it returns. Users never see the outage.
- SSO and MFA: Ping Identity (PingFederate) with OAuth2/OIDC.
5. Phased migration with Adobe Target
- Module by module: move features off legacy platforms such as OpenText TeamSite/LiveSite one at a time instead of a single big launch.
- Traffic ramp: Adobe Target A/B tests send a growing share of visitors to the new AEM pages.
- Retire safely: watch performance and user behaviour before switching the old system off.
6. Monitoring and performance
- Logging and APM: frontend logs into Splunk with alerts, New Relic on the server side.
- User journeys: Quantum Metric to find where users drop off and which client-side errors they hit.
- Speed: Core Web Vitals, font preloading, removing render-blocking resources, and Dispatcher caching rules for heavy traffic.
Selected work
- Capella University marketing site: multi-domain platform with personalised enrolment paths.
- Strayer University marketing and paid media pages: multi-brand landing pages built on a modern archetype with Webpack.
- Capella & Strayer Action Center: self-service application portal on Adaptive Forms and React.
- Sophia Learning: affordable, competency-based online learning platform on AEM.
- Capella results and catalog: course catalogue and academic results applications.
- Document Management System: high-volume document intake with self-service verification.
Certifications and awards
- Adobe Certified Expert, AEM Sites Developer
- Oracle Certified Java SE 6 Developer
- STAR Award (3x) and several Spot Awards at Credera / TA Digital