How phoolhbti/citraining works
Project type and purpose
• This is an Adobe Experience Manager (AEM) multi‑module Maven project (“citraining”) that builds:
• OSGi bundles and Java back‑end logic (core, bundle, bundle‑taglib)
• JCR content and configs (content, ui.apps, ui.config, ui.content)
• Front‑end assets via Webpack (ui.frontend)
• Dispatcher configurations for Apache HTTP caching (dispatcher, dispatcher.ams)
• Integration and UI tests (it.tests, ui.tests)
File structure
• Top‑level aggregator pom.xml ties together modules: all, core, content, ui.apps, ui.config, ui.content, ui.frontend, dispatchers, test modules.
• “core” contains OSGi services, servlets, filters, schedulers, Sling models.
• “bundle‑taglib” and “bundle” produce additional OSGi bundles for custom JSP taglibs.
• “content” holds generic content package definitions.
• “ui.apps” and “ui.content” deliver /apps and /conf JCR packages.
• “ui.config” delivers OSGi configurations under /apps/citraining/osgiconfig.
• “ui.frontend” compiles SCSS/JS into AEM clientlibs.
• “dispatcher” and “dispatcher.ams” produce Apache Dispatcher vhost/farm configs for on‑premise and AMS.
• “it.tests” runs JUnit ITs against AEM instances.
• “ui.tests” runs WebDriver/Selenium tests in containers (Docker compose).
README
• The README is minimal. Use module names and Maven lifecycle as source of architecture.