Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

What options are available to store text content on AEM

Avatar

Level 1

The use case at hand is to store documentation about a product in AEM. Im looking for possible options AEM offers. Lets say below is the sample layout documentation content. I have already explored using Content fragment as one of the suitable solutions for this use case. However, Im looking for more alternatives.

 

<Document Title> 

(Text goes here)

<Short Description>

(Text goes here)

 

<Detailed Description>

(Text goes here)

<Images>

(Images goes here)

<Footer>

(Some Conclusion)

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Level 4

Hello @Ashwin_KumarSr 

 

The most common way to store the documentation in AEM is by using eaither CF, EF.

Also here are some alternative ways you can consider:

 AEM WCM (Web Content Management) Components: You could create a set of pages in a WCM where each page represents a section of your content. The pages could contain a mix of OOTB components and custom built components based on your requirements.

The approach could be to create a page template with multiple components on it that matches your sample layout. For example, you'd have:

  • A Text Component for the Document Title,
  • Two Text Components for Short and Detailed Descriptions,
  • A carousel/slideshow component for Images,
  • And a Text Component for the Footer.

Each of these components could be populated with static or authorable content in a manner similar to the following Code:

<cq:include path="title" resourceType="foundation/components/text" />
<cq:include path="shortDescription" resourceType="foundation/components/text" />

 

The other approach if your documentation can be structured as a Form with various fields you can use AEM FORMS, which can be published as HTML5 or PDF for different devices.

 

Thanks,

Venkat

View solution in original post

1 Reply

Avatar

Correct answer by
Level 4

Hello @Ashwin_KumarSr 

 

The most common way to store the documentation in AEM is by using eaither CF, EF.

Also here are some alternative ways you can consider:

 AEM WCM (Web Content Management) Components: You could create a set of pages in a WCM where each page represents a section of your content. The pages could contain a mix of OOTB components and custom built components based on your requirements.

The approach could be to create a page template with multiple components on it that matches your sample layout. For example, you'd have:

  • A Text Component for the Document Title,
  • Two Text Components for Short and Detailed Descriptions,
  • A carousel/slideshow component for Images,
  • And a Text Component for the Footer.

Each of these components could be populated with static or authorable content in a manner similar to the following Code:

<cq:include path="title" resourceType="foundation/components/text" />
<cq:include path="shortDescription" resourceType="foundation/components/text" />

 

The other approach if your documentation can be structured as a Form with various fields you can use AEM FORMS, which can be published as HTML5 or PDF for different devices.

 

Thanks,

Venkat