How hlxsites/wknd works
Project type and purpose
• This is a Helix-based static site project (“WKND Demo”) that uses Adobe Edge Delivery Services to build and deliver a block-driven website.
• Key features:
• Document‐based content authoring (content lives in SharePoint/Google Drive)
• A/B experimentation and campaigns (client‐side plugin + RUM conversion tracking)
• Slack Bot integration for Lighthouse/conversion monitoring
• Standard CI (GitHub Actions) for test and release
File structure
• Top‐level directories:
• blocks/ → reusable UI components (JS+CSS)
• plugins/ → optional Helix plugins (experimentation, rum-conversion)
• scripts/ → client‐side utilities (Franklin core, analytics, consent)
• styles/ → global and feature CSS
• documentation/ → conceptual docs (audiences, experiments, campaigns)
• test/ → unit tests (blocks, scripts) + Puppeteer traffic simulator
• .github/workflows → CI jobs (run-tests, release)
• Config files: package.json (build & dev scripts), fstab.yaml (content source mapping), helix-version.txt
README for additional insights
• Describes local development: Helix CLI (hlx up) to proxy pages locally.
• CI/CD: GitHub Actions deploy to Preview & Live via Edge Delivery Services.
• External integrations:
• AEM Sidekick extension (for authoring + publishing)
• RUM service (helix-rum-js) for sampling & conversion tracking
• Slack Bot (helix-bot) for reporting
Final advice
• You capture both build‐time (CI/CD) and run‐time (delivery + client execution) phases.