AEM Component Library

[awrp]

I haven't used AEM in about 4 years so I'm familiar but not intimately so with the updated versions of the CMS. Right now, I'm doing research into whether or not this is even possible.

Ideally, what I'd like to create is a standalone site of all the different AEM 6.4 components that our development team has created over time. There are about 20 components that I'd like to display in a list similar to the Carbon Design System. This would be used as a reference guide for our UX, creatives, and content authors.

In order to minimize rework from our development team, and keep this site in sync with current component states, I want to be able to pull the component code directly from what's in AEM and display on this new standalone site. However, I'm not sure what that looks like technically. Is there a "component API" where we can pull that code out of AEM and then display in this standalone site?

I know this will probably require something custom built - I'm ok with that - but I'm unsure of where to start with the architecture. Would I be able to copy the HTL component code out of AEM, maybe via a javascript task runner like Gulp, and reformat those files into something usable?

[Andrew_Khoury]

It sounds like you are describing something along the lines of Experience Fragment building blocks, see here:

Adobe Experience Manager Help | Using AEM Experience Fragments

[kautuk_sahni · Accepted solution]

You can use content fragment and experience fragment for re-usability of the content and component(s) respectively.

Where as editable template can be used to create initial content which you can reflect on all the pages that you have create using Editable template.

Editable template:- Trying out Editable Templates in We.Retail

Content fragment:- Page Authoring with Content Fragments

Experience Fragment:- Experience Fragments