[Enhancement]: Add build status badges for multilingual documentation versions

[Adrija-verse]

Type of Enhancement

Adding/improving 'Further Reading' resources

Relevant Page(s) URL (if applicable)

NIL

Current Content Snippet (Optional, but helpful)

The DISCOVER Cookbook now supports multiple versions (v1.0, v2.0+) and multiple languages (English, Spanish, etc.) through a sophisticated CI/CD pipeline. However, there is currently no visual indicator showing:

• Whether the latest builds succeeded or failed
• Which language versions are building successfully
• The status of deployment previews

This creates several issues:

[ ] Maintainers cannot quickly identify build failures without checking Actions tab
[ ] Contributors don't know if their PR broke the build for specific language versions
[ ] Users have no confidence indicator for documentation stability

Proposed Enhancement / Suggestion

Add automated build status badges to the repository README and documentation site that display real-time deployment health for the multi-version, multi-lingual documentation pipeline.
Specific Changes:

Add GitHub Actions workflow status badge to README.md
Add Netlify deployment status badge
Optional: Create build matrix table showing per-version/per-language build status
Optional: Add "last successful build" timestamp to documentation footer

Rationale & Expected Impact

Problem Being Solved:
The DISCOVER Cookbook now has a sophisticated CI/CD pipeline (implemented during GSoC 2025) that handles:

Multiple documentation versions (v1.0, v2.0+)
Multiple languages (English, Spanish, extensible to more)
Automated deployments with concurrency control
Netlify preview deployments for PRs

However, there's currently no visual indicator of system health. Stakeholders must manually navigate to the Actions tab to verify build status, creating several pain points:

Maintainer friction: Manual checking required to verify deployments
Contributor uncertainty: No immediate feedback if their PR broke builds
User confidence: No trust signal that documentation is actively maintained
Debugging delays: Build failures not immediately visible

Why This Matters:

The infrastructure investment from GSoC 2025 is significant—badges make that investment visible
Professional open-source projects use status badges as quality signals
Reduces cognitive load on maintainers who must verify deployment status
Enables faster incident response when builds fail

Why Now:

Infrastructure is stable and mature
Low implementation cost with high visibility gain
No dependencies on other features
Can be implemented independently by a single contributor

Additional Resources / Further Reading

This idea is given by me. If the maintainers assign me to do this enhancement then i may proceed with PR for adding enhancement. Please let me know if i can proceed or not

Contribution

• I agree to follow the DISCOVER Cookbook's Code of Conduct and Contributing Guidelines.
• I would be willing to draft a pull request to implement this enhancement.

[dharitripravasahoo]

Hi
I’m interested in working on this enhancement and would like to take this issue up.
Please let me know if I can proceed with the implementation.
Thanks!

[Aman123933]

Hi! I’d like to work on this issue if it’s still available.
Please let me know if I can proceed or if there’s anything specific you’d like me to follow.

[Adrija-verse]

Hi maintainers! 👋

TL;DR: I've implemented the badge enhancement and submitted PR #474 for review.

Implementation Complete

I've added a GitHub Actions workflow status badge to the README that provides real-time visibility of the documentation build pipeline health.

PR: #474
Changes: Single line addition to README.md
Risk: Zero (documentation-only change)
Testing: Badge verified and rendering correctly

What This Solves

From the original issue, this addresses:

• "Maintainers cannot quickly identify build failures" → Badge shows pass/fail instantly
• "Contributors don't know if their PR broke the build" → Badge updates in real-time
• "Users have no confidence indicator" → Visible quality signal

Technical Details

Badge added:

[![Documentation Build](https://github.com/numfocus/DISCOVER-Cookbook/actions/workflows/build-gh-pages.yml/badge.svg)](https://github.com/numfocus/DISCOVER-Cookbook/actions/workflows/build-gh-pages.yml)

Targets workflow: build-gh-pages.yml (your main deployment workflow)
Updates: Automatically when workflow runs
Links to: Actions page for detailed logs

About Netlify Badge

I investigated adding a Netlify badge but found:

• netlify.toml exists but no Netlify deployment in GitHub Actions
• Unclear if Netlify is actively used or legacy config

If Netlify is still in use, I'm happy to add that badge too—just need:

1. Netlify site ID
2. Confirmation it's actively deployed

If not, the GitHub Actions badge fully addresses this issue.

Next Steps

The PR is ready for review whenever convenient! It's a straightforward change that should merge cleanly. Happy to address any feedback or make adjustments.

Looking forward to contributing more to DISCOVER-Cookbook as I prepare for GSoC 2026! 🚀

[Adrija-verse]

Hi @maintainers!

Following up on this PR when you have a moment.

Summary:
This PR adds a GitHub Actions workflow status badge to the README (+3 -1 lines) to provide visibility into the build pipeline health, as requested in #474.

Status:

• Changes are minimal and focused (only README.md)
• Badge tested and renders correctly
• Links to the correct workflow (build-gh-pages.yml)

Note on Netlify: The Netlify deploy preview failures are expected for external contributors due to access restrictions and don't affect the validity of this PR.

No rush at all—just wanted to make sure this didn't get lost in the queue. Happy to make any adjustments if needed!

Thank you for your time and for maintaining this great project!