How dpgalliance/publicgoods-scripts works
Project type and purpose
• This is a “static‐site generation & automation” toolchain for the Digital Public Goods website, implemented as an NPM‐managed monorepo with multiple “packages” (frontends, utility scripts) plus a separate Java-Maven TestAutomation suite.
• Its purpose is to crawl a WordPress back end, consolidate data, build several React/NextJS front ends (registry, eligibility quiz, map, community page, help center, roadmap), and move the results into the public website repo via CI.
File structure
– Top-level elements:
· .github/workflows: CI definitions (auto.yml, feature.yml, test.yml)
· scripts/: bash utilities (static.bash, moveFiles.bash)
· package.json & package-lock.json: root NPM workspace config, listing workspaces
– packages/automation: Node.js data‐consolidation & HTML‐generation scripts
– packages/registry, eligibility, map, community, helpcenter, roadmap: individual front-end apps (React or NextJS) each with their own package.json, src/, public/
– TestAutomation/DPGAUIAutomation: Java Maven project for UI & API tests, Allure reports, testNG.xml
– Typical build outputs under each package’s build or target folder
README for additional insights
• Describes an NPM workspace setup (Node 15+), CLI steps (npm i, clone dependent repos, run scripts/static.bash to crawl WP, run Node scripts in packages/automation, build React apps, run scripts/moveFiles.bash)
• Deployment is driven by GitHub Actions on merges or scheduled triggers, and publishes to GitHub Pages of the public website repo
Summary advice
– Capture data flow end-to-end, from CMS to user browser
– Distinguish build orchestration (CI) from runtime (static hosting)
– Keep component boundaries clear: automation vs. presentation vs. testing