How roperev/ams-dsp-lts works
Project type and purpose
• This is an AEM (Adobe Experience Manager) Cloud Service boilerplate / “Helix”‐based front-end project. It provides a pattern for building WYSIWYG‐authorable, block-based web pages delivered both via AEM author/publish and via an Edge Delivery network.
File structure
• Top level:
• .github/workflows/… – CI/CD pipelines (GitHub Actions) for cleanup, build, deploy
• fstab.yaml, helix-query.yaml, helix-sitemap.yaml, paths.json – Helix routing & configuration for edge deployment
• blocks/, models/, component-*.json – Definitions of AEM blocks, content models, filters & component metadata
• scripts/ – Front-end JavaScript (editor support, AEM proxy integration, client features)
• styles/ – Global CSS, lazy-loading, fonts
• tools/sidekick – Helix Sidekick extension for local editing & debugging
• head.html – HTML snippet inserted into <head> for fonts, meta, scripts
• package.json – Node tooling, Helix CLI, dev scripts
README for additional insights
• Project uses AEM Cloud Service (LTS ≥ 2024.8) and Helix Edge Delivery
• Local dev: @adobe/aem-cli + aem up → AEM proxy on localhost:3000
• Blocks are created via JSON descriptors & accompany CSS/JS
• CI/CD through GitHub Actions & AEM Code Sync App
Detail over simplicity
• Block definitions, client libs, templates separately
• Local dev vs. production endpoints