Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

Create Glossary Page Info in AEM

rsl_lucky
Level 3
Level 3

Hi,

 

Want to create glossary info for the site, could anyone suggest best possible solution or option for achieving it. Currently, we have two custom components, 1st would behave like carousel & 2nd component show all info. Based on selection in 1st component its navigating to respective info on 2nd component.

 

Can anyone suggest any other best solution or way to implement this glossary page suggested by Adobe instead of using these custom components approach, as we want to try avoid use of these custom components.

 

Thanks

RSL.

5 Replies
rsl_lucky
Level 3
Level 3

Yes @kimonp31365843 we did, also if any sample links of this glossary implementation would really help us.

kimonp31365843
Level 4
Level 4

Suggested approach based on personal XP:

  1. Have the glossary terms + definitions in a CSV file
  2. Upload the CSV in DAM
  3. Glossary component:
    • Editorial dialog: Provide the DAM path to the csv
    • Sling model: extract glossary terms + definitions from csv on the fly. 
    • Alternatively, you can use AJAX requests (instead of Sling model) to return the glossary contents. This makes pagination and dispatcher caching easier, as content rendering is all based on incoming AJAX requests
  4. Performance considerations:
    • loading of glossary content: maybe pagination would be in order depending on size
    • if you use AJAX approach, verify your AJAX requests can be cached (Dispatcher or in-memory or both)

Btw I am not sure if this question is specifically for Assets.

rsl_lucky
Level 3
Level 3

Thanks kimonp31365843 for the info.

Need to create a custom glossary component and render the content by fetching it from CSV uploaded on DAM, Right ? If yes, then their wont be any authoring experience to update any content in-case if required. Anyways will try with approach once & thanks for it.

kimonp31365843
Level 4
Level 4

indeed, the CSV-based approach is for cases where the glossary content is a bit more "raw". If you want to have an arbitrary set of editorial component you would probably go for a "Container" component + customization.