examples of interactive user tools built as an AEM component | Community
Skip to main content
August 4, 2017
Solved

examples of interactive user tools built as an AEM component

  • August 4, 2017
  • 2 replies
  • 970 views

I have a client that would like to build an interactive tool as an AEM component where the user has several numerical inputs, and the function is to output a graph and figures from an equation. Does anyone have any examples of interactive user tools such as finance calculators or quizzes built as a component in AEM?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

This use case would be done through custom AEM components. Using HTL or JSP on the front end and Java on the backend (OSGi services)  - there is not much that cannot be programmed for AEM.

A few year ago - during a code contest for AEM - we had an entry that we flipped to an article. It was developed by https://www.linkedin.com/in/edubey/ and represents an AEM Custom Quiz component for use on an AEM web page.

The use case for this was a quiz. I hope this would point you in the right direction...

Scott's Digital Community: Developing a custom Adobe Experience Manager Quiz Component

2 replies

smacdonald2008
smacdonald2008Accepted solution
Level 10
August 4, 2017

This use case would be done through custom AEM components. Using HTL or JSP on the front end and Java on the backend (OSGi services)  - there is not much that cannot be programmed for AEM.

A few year ago - during a code contest for AEM - we had an entry that we flipped to an article. It was developed by https://www.linkedin.com/in/edubey/ and represents an AEM Custom Quiz component for use on an AEM web page.

The use case for this was a quiz. I hope this would point you in the right direction...

Scott's Digital Community: Developing a custom Adobe Experience Manager Quiz Component

August 7, 2017

Thank you! In this case, (as an AEM implementer and not a developer) are you saying that it can't be built as a component that has AEM dialog box inputs, that could potentially be used and changed across multiple pages and sites within AEM?