- Adobe · . stands for Reconstrucve API for the DOM. It is an add-on for Adobe Experience Manager...

4
281 Bloomfield Ave, Verona, NJ 07044 Reconstructive API for the DOM its here and it changes everything www.aandes.com

Transcript of - Adobe · . stands for Reconstrucve API for the DOM. It is an add-on for Adobe Experience Manager...

281 Bloomfield Ave, Verona, NJ 07044

Reconstructive API for the DOM

its hereand it changes everything

www.aandes.com

www.aandes.com

stands for Reconstruc�ve API for the DOM. It is an add-on for Adobe Experience Manager (AEM) that allows developers to manage the content of standalone websites independently of AEM. Simply said, this revolu�onary package gives developers an API to use AEM as a headless CMS.

Ÿ Allows any company to use Adobe Experience Manager (AEM) with no restric�ons of their development environment or language.

Ÿ Significantly reduces the �me it takes to implement Adobe Experience Manger (AEM)

What does RAPID Solve?

Don't se�le - Now you can use any technology for the job

Percentages of websites using various server-side programming languages.W3Techs.com, June 13 2016

Java 2.7%

ASP.NET 15.8%

Erlang 0.1%

Python 0.2%

JavaScript 0.3%

Perl 0.4%

Ruby 0.6%

ColdFusion 0.7%

PHP 82.1%

etc...GoLang

www.aandes.com

How it works

Advantages of RAPID,the only true headless add-on for AEM

Ÿ 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 CaaS model or Simply use RAPID+

Ÿ Reduces cost and �me to market – RAPID can have your site authored in minutes

Ÿ Enables you to use one of the best enterprise CMS's on the market, AEM, 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 li�le, of the AEM technology stack

Ÿ Allows you to build and serve clients with a cloud na�ve micro-services architecture

Ÿ Allows you to con�nue to have your authors use AEM with no restric�ons or degraded user experience

Ÿ Website was built in a different technology than CMSŸ Time to Market - The �me it would take to rebuild website would

take too long Ÿ Web team is against learning a new IDE and loss of development

team would severely impact organiza�on Ÿ Development team does not want to be hindered by building inside

of a monolithic CMS that colors everythingŸ IT is trying to build out a modern applica�on using 12 Factor app

methodologies, micro-services, cloud Ÿ Enterprise website uses more than one web technology

Typical use cases for RAPIDand a Decoupled or Headless Architecture

www.aandes.com

Content owners

Staging environment Produc�on environment

Produc�oncontent

repository

Content consumer

Exis�ng or new web applica�on

RAPID + CaaCRAPID tag

Content authoring environment CMS

RAPID importer Content repository

Produc�onweb server

RAPID + CaaC

Decoupled or Headless Architecture using RAPID & RAPID+