AEM expert in architecture, development, cybersecurity & AI (Vertex AI, Gemini, OpenAI), vector search & CMS transformation

As part of a major project to migrate from a Core Media CMS to AEM Cloud, I served as a Business Analyst and Epic Owner. Collaborating closely with business stakeholders, including the global omnichannel excellence team, country marketing leaders, brand managers, and creative & marketing agencies, I provided project management, consultation and advisement on AEM-based website development while leading the migration from CoreMedia CMS to Adobe Experience Manager (AEM) as a Cloud Service. Utilizing BABOK guidelines, I systematically captured and documented author requirements, converting them into Jira epics/user-stories to guide the project team through the blueprinting and development phases. Key business processes, such as executing mobile tariff orders, were realized within AEM. I oversaw the implementation of my concepts, ensuring alignment with business needs, integration of SEO strategies, and compliance with accessibility standards like WCAG 2.1. This approach covered the entire AEM Cloud platform, optimizing performance and ensuring successful delivery across all areas through continuous monitoring and coordination.

• Accessibility and SEO Enhancement: Led the effort to integrate accessibility (WCAG 2.1 compliance) and SEO best practices into the AEM Cloud platform. This included conducting audits, defining necessary enhancements, legal requirements and overseeing their implementation to ensure an inclusive and optimized web presence.
• Requirement Analysis and Documentation: Translated business requirements into detailed technical specifications, epics, and user-stories. Ensured these were effectively communicated and implemented by the development team.
• Issue Analysis and Improvement Planning: Identified issues faced by content authors in the AEM Cloud environment. Provided actionable improvement suggestions and incorporated these into the product launch schedule.
• Whitelabeling Application Development: Developed a Whitelabeling application intended to serve all brands under the client’s portfolio. This included creating a flexible and scalable architecture that could be customized and reused across various brands. Integrating AEM with other solutions (Analytics, Target, CRM).
• Process Analysis and Documentation: Conducted thorough analysis and documentation of existing processes for migration into Adobe Experience Manager (AEM) Cloud.
• Review and Gap Analysis: Conducted thorough reviews of existing AEM templates and components, identifying gaps between current implementations and business expectations. Developed strategies to address these gaps and optimize template and component usage.
• Jira Management and Executive Reporting: Managed the creation of Jira tickets based on stakeholder requirements, including detailed technical specifications. Presented project progress and key decisions to executives and business units, facilitating informed decision-making.
• Executive Presentation: Conducted a presentation for executives, business units, and key decision-makers of the client, detailing the scope of the transition, specific requirements, and benefits to enable informed informed decision-making.

Technologies:

• Adobe AEM Cloud
• Core Media
• Vue 3
• Varnish
• MFE (Micro Frontend)
• Content Fragments
• Jira
• Confluence
• Miro
• WCAG 2.1
• SEO
• Accessibility

Realisation of the complete web appearance ([link] with Adobe CQ 5.5. On the basis of a HTML click dummy from a design agency, I developed the components and templates and delivered them with an example content package.

• Closed User Groups member area for the staff.
• Consulting on how to use ACL with CUG
• Development of complex components and templates with an easy to use author-interface.

Technologies:

• Adobe DAY CQ 5.5
• Java 7
• jQuery

Special development of a complex AEM extension, based on an existing AEM platform. Wrote conceptual design, planning, architecture and realization with integration in the multi-tenant environment.

• Developed the AEM frontend with HTL, Coral UI and AngularJS 1.3;
• Developed AEM REST Services and connected them to the frontend.
• Architecture of the ACL. Defined special user groups which can access this “AEM Tools” extension, using LDAP.
• Developed special AEM workflows for approval of changes.
• Green field project setup with Maven, clientlibs, designs.
• Extended the existing Continuous Delivery environment (Jenkins, Sonar) for usage of this project.
• Developed special data transfer between Apache Dispatcher and AEM Publish server.

Technologies:

• Adobe AEM 6.3
• Multi-Tenant Environment
• Coral UI
• AngularJS

Support, consulting, and project management for the business department in the implementation of business requirements within the Adobe AEM project. Acting as the central interface between external development partners, internal IT, and the business unit (client). Responsible for tracking requirements in terms of time and budget, identifying solutions for daily challenges (development, platform, services, production bugs), defining business requirements, and designing the technical architecture. Additionally, full project management responsibility for my own implementation projects.

• Supported the divisions by creating functional documents, cleared technical questions.
• Product owner for some AEM specific tasks.
• Verification of technical concepts of external service providers.
• Verification of functional concepts in the AEM context.
• Migration of Assets from Scene7 to Dynamic Media Cloud.
• Micro services with Docker to outsource AEM business logic.
• Introducing A/B tests with Adobe Target.
• Optimizing frontend performance in AEM. First paint, reordering JS-Libs, adaptive images, loading component content on demand.
• Planning and controlling of website rollouts on global area for new markets and brands.
• Architecture of an API Gateway to hold all REST-services on one place to gain benefits in caching and performance.

Technologies:

• Adobe AEM 6.1
• AEM Apps
• Sling Models
• Sightly
• Java
• JavaScript
• Bootstrap 3
• Granite UI

Conception and architecture of a blog with Adobe CQ 5.6. In workshops with the customer we discussed the functional requirements and based on them the technical architecture solution was build.

Technologies:

• Adobe DAY CQ 5.6
• Social-module from CQ5.

Migration of an e-commerce platform, based on Adobe CQ5.6.1 & Hybris, to Adobe AEM6 with “Sightly”.

• Development of components with Sightly, WCMUse, Adapter Factory, Sling Models.
• Adoption of the new web layout, adding responsive capabilities for smartphones and tablets.
• Implementing use cases from the old Hybris environment into the new AEM6 platform.
• Bug Fixes, Changes

Technologies:

• Adobe CQ 5.6.1
• Adobe AEM6
• Hybris
• Sightly
• Java
• jQuery

Based on the review of the existing old application that took place in May 2019, extensive concepts have now been written to update the outdated AEM environment to the latest AEM 6.4 (later 6.5) technologies. In my role as project manager and implementation partner, I managed the timely implementation of the requirements specification.

These concepts previously created, are now being gradually implemented. The previous components will be redeveloped with React to take Adobe's approach towards "AEM-Agnostic" into account, so that the application can later be transformed towards Headless CMS.

In addition, a separate AEM network was established in the federal data center in order to bring the application previously hosted by an external company back into the company's own network. A separate build pipeline was also set up for the development, test and production environments.

Technologies:

• Adobe AEM 6.5
• React (JSX)
• TypeScript (TSX)
• NPM
• Node.js
• WebPack
• Jest
• Jenkins

Advanced the development of a longstanding AEM application, overseeing its migration to newer versions (6.3, 6.4, 6.5), serving multiple Swiss Federal Authorities such as the FSO, SECO, DETEC, SFOE, FOPH, and other government bodies, including obtaining security clearances from agencies like FEDPOL. Engaged in requirement gathering discussions with clients and executed the desired functionalities. Also conducted several content migrations from various legacy systems into the new AEM environment. This included migrations from older CQ versions, involving components and content. In mid-2021, I spearheaded a relaunch project that completely redesigned and redeveloped the AEM application, incorporating the latest features of AEM 6.5 and focusing on 'Cloud Readiness' in development.

• Developed specialized components using Vue.js, AngularJS, AlpineJS, and React for Touch UI.
• Customized legacy components based on CQ5 Classic UI.
• For the subsequent relaunch, all components were developed exclusively with Vue, and existing ones were migrated to this technology.
• Focused on headless components for reusability in non-AEM-based projects.
• Integrated external systems (e.g., Postfinance Payment) via REST & SOAP and imported data (JSON, XML) into the AEM content structure.
• Redesigned the search functionality and developed a single-page application as a search component using AngularJS.
• Integrated the React Component Generator for the development of React-based AEM components.
• Authored Groovy migration scripts to transfer content from multiple foreign CMS systems to AEM.
• Adopted components from these external systems into AEM.
• Performed frontend performance optimization (page load times, data volume, lazy loading, etc.).
• Prioritized the optimization of mobile views.
• Integration of commerce functionalities, such as PostFinance for payment processing.
• Developed the successor to the AEM project with a headless approach for data delivery and external UI rendering via Vue.
• Managed a separate frontend project based on Vue, providing components (Molecule Design Pattern) for AEM and other CMS environments.
• Utilized Core Components as the foundation for custom component development.
• Implemented Experience Fragments and AEM Styles Policies for content design and interaction with CSS breakpoints.
• Consolidated and restructured fragmented project configurations (Page Properties, OSGi Configs, Component configs, Language Nodes…) for centralized use.
• Developed Microservices with NodeJS as an interface between AEM and various API endpoints to outsource business logic.
• Created specialized component dialogs based on Coral UI and AlpineJS.
• Integrated Google Custom Search.
• Web Application Security: Identified security vulnerabilities within the AEM application, implemented preventative measures based on the OWASP Top 10, installed Adobe hotfixes, hardened production environment...
• Conducted security scans, evaluated results, and developed various security tools to prevent hacker attacks such as "Verb Tunneling".
• Analyzed current issues faced by authors in handling the AEM Cloud environment, created improvement suggestions, and incorporated their implementation into the product launch schedule for AEM.
• Supported the implementation of requirements from the marketing department and relevant stakeholders (e.g., data protection, business units, IT).
• Jira Ticket Creation: Gathered business requirements and created Jira tickets, including detailed technical specifications, which were subsequently implemented by the development team and myself.
• Stakeholder Requirement Gathering: Collected and documented stakeholder requirements in Jira tickets to ensure clear and actionable guidance for the development team.

Technologies:

• Adobe AEM 6.5
• Vue.js 2
• Groovy
• TypeScript
• AngularJS
• React
• AlpineJS
• WebPack
• Storybook
• NodeJS

Further development and realignment of the existing 3 AEM platforms (HUKDE, HUK24, VRK) with AEM 6.5.x.

• Development of new AEM components with Core Components.

• Replacement of an IBM WebSphere and migration of the use cases into the AEM backend:

• Replacing placeholders in AEM content that were previously replaced in WebSphere. Now a completely new logic for the AEM backend content rendering implemented.

• Conception and development of a routing service (Redirect Manager), which encapsulates the redirects, alias, vanity URL of the pages in its own AEM tool and controls it centrally up to delivery to the Apache Dispatcher.

• Further development / bug fixing of the 3 AEM applications

• Analysis of the current state of the REST services landscape including creation of a postman collection for the new development of an API gateway layer

• Use of these REST services in newly created online calculators

• Development of forms with AEM Forms.

• Migration scripts with Groovy for minor content adjustments (content bugs, conversion to new components).

• Implemented strategic security enhancements to counteract vulnerabilities associated with manipulation of web request methods, thereby bolstering the application's defense mechanisms against prevalent cyber threats.

Technologies:

• Adobe AEM 6.5
• AEM-Security
• TypeScript
• NPM
• Node.js
• Adobe Core Components
• AEM Forms
• Coral UI

Maintenance and modernization of a long-established CQ5-AEM 6.5 application with outdated technologies, as well as planning and gradual migration to the AEM Cloud. The focus is on technological upgrades and optimizations to align the application with the requirements of the AEM Cloud.

• Integration of the new AEM Archetype structure with WebPack and Vue.js into the existing application.
• Replacement of the Gulp-based frontend build process with WebPack.
• Introduction of a Vue frontend library based on Atomic Design patterns to replace JSP components with jQuery and Terrific.
• Migration of Classic Dialogs to Touch UI with Coral.
• Resolution of web security vulnerabilities identified through penetration tests.
• Implementation of proactive penetration tests to detect and prevent future security issues.
• Ensuring accessibility compliance according to WCAG 2.1 standards.
• Implementation of advanced SEO measures to enhance visibility for search engines and AI crawlers.
• Planning of the migration to AEM Cloud, including architectural concepts and step-by-step updates to the legacy application.
• Development of an exit strategy from AEM Cloud.
• Analysis of migration costs and evaluation of alternative CMS solutions compared to AEM Cloud.
• Analysis of alternative content management systems (Magnolia, Liferay, Sitecore, Typo3) as decision options for the Adobe Cloud migration. Development of an exit strategy.

Technologies:

• Adobe AEM Cloud
• Magnolia
• Vue 3
• Content Fragments
• Jira
• Confluence
• Miro
• WCAG 2.1
• SEO
• Accessibility

I applied in that company as an employee and later I came back as a Freelancer.

• Further development of a brand new real estate web platform in Austria.
• Development of partner web pages in the real estate and financial area for customers of this company.
• Established new business processes in the extranet application
• Connected new financial institutes via web services (SOAP) to this extranet app.
• Complete relaunch for the German web platform.
• Developed the mobile version of it.
• Added tracking with Webtrekk to all web platforms

Technologies:

• Java 1.5 with frameworks JSP
• JSF
• Facelets
• MyFaces
• Spring 2
• EJB2
• Hibernate
• JAX-WS
• FirstSpirit 3 CMS

For a manufacturer of consumer goods in the household, its website, based on AEM 6.5, has been continuously developed for years. In addition to my activities in this main project, I took over the "Corporate" sub-project, which involved building a completely new AEM website.

• Full stack development of new components and templates with various JavaScript technologies (Vue.js, AngularJS, jQuery)
• Further development of the forms and sending them by email
• Development of new backend services to deliver data to the frontend
• Connection of a SAP Hybris Commerce system for article data
• Connection to Phrase.com for translated texts
• Acquisition of service tickets

Technologies:

• Adobe AEM 6.5
• TypeScript (TSX)
• NPM
• Node.js
• WebPack
• jQuery
• AngularJS
• Vue.js
• Jenkins

Audi.com, EON with CQ5

• Further development of existing web portals with Adobe DAY CQ5.x for automotive and energy companies.
• Usage of modern JavaScript-frameworks for frontend development.
• Development of new CQ-components with user-friendly author dialogues.
• Further development of the HTML5 prototype with adapting its layout to CQ5.
• Infrastructure tasks for configuration and controlling the CQ5 servers.
• Upgrade process from CQ5.4 (Java 6) to CQ5.6.1 (Java 7)

Technologies:

• Adobe DAY CQ 5.4 & 5.6.1
• SASS
• Grunt
• Node.js
• jQuery
• Mobify
• Ruby