How dpgalliance/dpg-resources works
Project type and purpose
• This is an open-source documentation repository (“DPG Resources”) that serves as a static knowledge base for Digital Public Goods (DPG) applicants and maintainers.
• It houses Markdown guides, templates, best practices, example code snippets (MongoDB-Express REST API), and assets. Its end goal is to generate a browsable website (likely hosted via GitHub Pages or a similar static-site host).
File structure
• Top level
– README.md, CONTRIBUTING.md, LICENSE.txt → project metadata & governance
– docs/ → all content that drives the static site (Markdown, images, templates, code examples)
• docs/
– Markdown content (best-practices.md, open-standards.md, etc.)
– docs/assets/ → images, badges, video files
– docs/platform-independence/mongodb-express-rest-api-example → a stand-alone example with its own app/ and server/ subdirectories, Docker, package manifest
• No src or build folder: implies content files are ingested directly by a static-site generator or GitHub Pages engine.
README for additional insights
• Indicates that this repo is purely documentation, meant to be a “knowledge base” with templates and guides.
• No custom backend or database; it’s a content hub linking out to external DPG resources.
Detail
– Break out the CI/CD step into lint → test → build if desired.
– Show that docs/assets folder contents become static assets in the final site.