Implementation of AEM for a Fintech Company’s Academic Project

About Customer

Our customer is a fintech giant with a strong presence in the Indian financial market. They provide tailored solutions to users ranging from personal finance to wealth management.

They offer various services including insurance, asset management, wealth management, and lending.

Business Challenges

The customer wanted their academic project to be more interactive with enhanced user experience.

• The objective was to build a website that required less manual work for adding content. They wanted a dynamic and automated system that relied on a database for ease and efficiency.
• The existing platform did not have a seamless user interface to access or upload high-quality videos.

Our Solution

• This case study examines the strategic initiative to create a new project repository for improved upkeep, set to operate as a subdomain of the current website and hosted on identical servers.
• The existing AEM servers of the website were assessed for their capacity to sustain the additional mini-website, with a focus on aspects like configuration, dimensions, processing power, and memory.
• Implementing the solution required executing numerous AEM queries to fetch content for different pages.
• Essential updates involved altering dispatcher rules to align with the project’s needs and revising certain cache rules as necessary. The subdomain is linked to the AEM content path and is structured to support an organized tier of series, seasons, episodes, and snippets.
• A clearly defined content architecture within AEM was essential to efficiently map and fulfill the dynamic content requirements. The implemented framework proposes Series at Level 0, Seasons at Level 1, followed by Episodes for extended videos, and Bites for brief clips, each correlating directly with their respective upper-level category.
• The integration of AEM with KPOINT Player and RESTful APIs is vital for presenting video metadata, like viewership numbers and playtime, on various pages. The executed content page layout and overarching AEM templates derive from the Business Requirements Document (BRD) and Experience Design (XD), and the solution was customized to the project’s specifications.

Embitel Impact

• The customer found increased engagement on the website and videos by their users.
• The users found the website easy to access and interact with.
• The new features connected with a wider community and amplified the website’s organic reach and brand visibility.

Technologies

Adobe Experience Manager