Reconstructive API for the DOM

Size: px

Start display at page:

Download "Reconstructive API for the DOM"

Brent Marsh
5 years ago
Views:

1 Reconstructive API for the DOM 281 Bloomfield Ave, Verona, NJ it s here and it changes everything

Reconstructive API for the DOM, RAPID, is an add-on for Adobe Experience Manager (AEM) that finally allows developers to manage the content of standalone websites independently of AEM.

Allows any company to use Adobe Experience Manager (AEM) with the typical restrictions of their choice of development environment or programming language.

2 Reconstructive API for the DOM, RAPID, is an add-on for Adobe Experience Manager (AEM) that finally allows developers to manage the content of standalone websites independently of AEM. Simply said, this revolutionary package gives developers an API to use AEM as a headless CMS. What does RAPID Solve? Allows any company to use Adobe Experience Manager (AEM) with the typical restrictions of their choice of development environment or programming language. Percentages of websites using various server-side programming languages. W3Techs.com, March Erlang 0.1% Python 0.2% JavaSc ColdFusion Static Ruby 0.6% 0.6% files 1.4% Java 2.5% ASP.NET 14.6% TM etc PHP 79.7% RAPID reduces the implementation time for Adobe Experience Manger (AEM) as much as 90% Don't settle - Now you can use any technology for the job

How it works in 4 Steps Install RAPID as a package in AEM Tag any or all pages you would like AEM to Author Tell RAPID where to save your content in the JCR Call content repository through a Content

enterprise CMS's on the market, Adobe Experience Manager in a flexible, headless model Reduces the need for expensive AEM developers and allows companies to innovate Reduces dependency on CMS and

3 How it works in 4 Steps Install RAPID as a package in AEM Tag any or all pages you would like AEM to Author Tell RAPID where to save your content in the JCR Call content repository through a Content as a Service (CaaS) model Advantages of RAPID, the only true headless add-on for AEM Reduces cost and time to market RAPID can have your site authored in minutes Enables you to use one of the best enterprise CMS's on the market, Adobe Experience Manager in a flexible, headless model Reduces the need for expensive AEM developers and allows companies to innovate Reduces dependency on CMS and allows you to use as much or as little of the AEM technology stack Allows you to build and serve clients with a cloud native microservices architecture Allows you to continue to have your authors use AEM with no restrictions or degraded user experience Typical use cases for RAPID For a Decoupled or Headless Architecture Website was built in a different technology than CMS Time to Market - The time it would take to rebuild website would take too long Development team is against learning a new IDE and loss of the development team would severely impact organization Development team does not want to be hindered by building inside of a monolithic CMS that does everything I.T. is trying to build out a modern application using 12 Factor app methodologies, micro-services and cloud services Enterprise website uses more than one web technology

4 Decoupled or Headless Architecture using RAPID & CaaS Content owners Content authoring environment CMS Production content repository Production web server RAPID importer Content repository Content consumer RAPID tag RAPID + CaaC Existing or new web application RAPID + CaaC Staging environment Production environment

USE CASE - Development does not want to use AEM Development team does not want to be hindered by building inside a monolithic CMS that does everything.

5 USE CASE - Development does not want to use AEM Development team does not want to be hindered by building inside a monolithic CMS that does everything. Example The everlasting battle of marketing and I.T. disagreeing on how to best move forward. Company X marketing team wants to use an in-page, WYSIWYG, top-of-the-line, CMS, such as Adobe Experience Manager, and the development team wants to build a modern Angular 2/ REACT, NodeJS, Single Page App/Process (SPA/SPP) website in the cloud using micro-services. Result When using RAPID, both marketing and I.T. win. The development team has freedom to build however they want, where ever they want, and marketing will never know the site they are authoring does not actually live in AEM. Development teams are able to build agile applications with Test Driven Development (TDD ) and Continuous Integration (CI). When a development team is able to build at the speed of agile teams, you will see a more concise finished product. Effort 20-30% reduction in time-to-market and costs. Building a greenfield application is always a huge effort. The best way to lose talented developers is make them obsolete by making them use old technologies. Building with RAPID allows IT to spend time building applications rather than learning outdated JSP driven applications and keeps your team engaged.

6 USE CASE Development team is a.net/php/etc.. shop Website was built in a different technology than CMS TM Example Company X has existing website(s) that are built in something other than Java and company X does not want spend the resources and cost to have to rebuild the site over in AEM. RAPID will proxy any site, built in any language with simple tagging of the existing website(s). Result Company X has reduced development by 90% and website continues to run as it did but now is enabled in Adobe Experience Manager for content owners to edit and publish content. etc Effort minimal - Developers will tag website where you want content owners to be able to edit and publish content

7 USE CASE How can I get to market faster with AEM? Time-to-Market - The time it would take to rebuild website would take too long Example Company X has an existing site and plans to move all assets into AEM. To rebuild website(s) in AEM is going to take too long. Using RAPID is an easy way of getting your content owners comfortable with AEM and of acclimating them to edit existing websites until an AEM monolithic type of build is complete. Some typical reasons why it would take too long: Company X trying to procure a company with AEM expertise to build AEM all-in application. Training your web development staff on AEM and gaining the necessary experience in AEM to build complicated website and have AEM be the face to your customers Training marketing on components and how to give technical teams correct specifications on what they want built Result Company X is using AEM in weeks to months rather than years and getting almost immediate ROI on CMS investment Effort - minimal to use AEM with RAPID, same as above

USE CASE Hybrid, a little in and a little out Hybrid Build Some in AEM and some outside of AEM Example Company X has an ecommerce site that talks to many back-end systems.

Some of the site you would like to build in the Cloud and some you would like to build 100% in AEM. With RAPID you are able to build as much or as little in AEM as is cost effective.

8 USE CASE Hybrid, a little in and a little out Hybrid Build Some in AEM and some outside of AEM Example Company X has an ecommerce site that talks to many back-end systems. They also have sections of their site that are heavy with content i.e., special offers, blogs, T s&c s. Some of the site you would like to build in the Cloud and some you would like to build 100% in AEM. With RAPID you are able to build as much or as little in AEM as is cost effective. Result - Company X can give a full AEM author experience for strategic parts of the site and continue to give a WYSIWYG experience for the rest of the site that could be built in the cloud controlled by the developers. Effort 20-30% reduction in time-to-market and costs for anything built outside of AEM. Developers can relinquish control of the parts of the website that they do not care about or do not have download SLAs to meet to marketing

Timeline Impact -30% 40% Project Timeline Impact +40%

9 RAPID Typical vs New Build vs Existing Typical AEM without RAPID New Build with RAPID Existing with RAPID 60% Project Timeline Impact -30% 40% Project Timeline Impact +40% Project Timeline Impact +70% 30% 30% 30% 30% 20% 10% 10% 10% 10% 10%

State of the Headless CMS Market 2018

State of the Headless CMS Market 2018 by Kentico Software Headless CMS Market in 2018 For many years, companies have been using traditional web-oriented Content Management Systems. But the world has changed.