✏️(docs) Add Add DPG badge to README

[BolajiAyodeji]

Purpose

This PR includes the new DPG badge in the README file, following the guide, and links to LaSuite Doc's profile page on the DPG Registry.

General requirements

• I have read and followed the contributing guidelines
• I have read and agreed to the Code of Conduct
• I have added corresponding tests for new features or bug fixes (if applicable)

Skip the checkbox below 👇 if you're fixing an issue or adding documentation

• Before submitting a PR for a new feature I made sure to contact the product manager

CI requirements

• I made sure that all existing tests are passing
• I have signed off my commits with git commit --signoff (DCO compliance)
• I have signed my commits with my SSH or GPG key (git commit -S)
• My commit messages follow the required format: <gitmoji>(type) title description
• I have added a changelog entry under ## [Unreleased] section (if noticeable change)

[coderabbitai]

Walkthrough

The README gains one new badge in its top banner section: an anchor linking to digitalpublicgoods.net that displays a "Verified-DPG-3333AB" shield image, inserted alongside the existing GitHub shield links at lines 20–22.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change—adding a DPG badge to the README file, which aligns with the changeset summary.
Description check	✅ Passed	The description is directly related to the changeset, explaining the purpose of adding the DPG badge and linking to relevant resources and guidelines.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[virgile-dev]

Thanks @BolajiAyodeji I just launched the CI.
You'll know what you need to fix by looking at the errors.
Cheers,

[BolajiAyodeji]

All should be fixed now @virgile-dev; thanks!

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 20-22: The DPG badge link and image were added to README.md but
there is no corresponding entry documenting this change in CHANGELOG.md.
Navigate to the [Unreleased] section in CHANGELOG.md and add an entry under the
appropriate category (typically under "Added" or "Changed") that documents the
addition of the DPG badge to the README as a documentation enhancement.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 33c5d653-fd89-43c2-b666-d643ba8fd7b8

📥 Commits

Reviewing files that changed from the base of the PR and between a087fcf and 5cedaa3.

📒 Files selected for processing (1)

• README.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for CHANGELOG files in the repository and verify they contain an [Unreleased] entry
fd -i changelog -t f | head -5

# If found, check for [Unreleased] section and recent DPG-related entries
if [ -f "CHANGELOG.md" ]; then
  echo "=== CHANGELOG.md content (first 50 lines) ===" 
  head -50 CHANGELOG.md
fi

Repository: suitenumerique/docs

Length of output: 1630

---

🏁 Script executed:

# Check the git status/diff to see if the README.md DPG badge addition is new
git diff HEAD -- README.md | head -100

Repository: suitenumerique/docs

Length of output: 157

---

🏁 Script executed:

# Check recent git history for README.md
git log --oneline -20 -- README.md

# Also check git status
git status README.md

Repository: suitenumerique/docs

Length of output: 265

---

Add CHANGELOG entry for the DPG badge addition to README.

The DPG badge was added to README.md (commit 5cedaa3), but no corresponding entry exists in the [Unreleased] section of CHANGELOG.md. Add an entry documenting this documentation enhancement.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 20 - 22, The DPG badge link and image were added to
README.md but there is no corresponding entry documenting this change in
CHANGELOG.md. Navigate to the [Unreleased] section in CHANGELOG.md and add an
entry under the appropriate category (typically under "Added" or "Changed") that
documents the addition of the DPG badge to the README as a documentation
enhancement.