[Feature] : Documentation Feedback Widget

Problem

Documentation is only as good as its maintenance. Currently, there is no direct way for a user to signal that a specific page is outdated, unclear, or broken, other than opening a GitHub issue (which has high friction).

Proposed Solution

Implement a "Was this page helpful?" feedback widget at the bottom of every documentation page.

Key Features

1. Simple Binary Feedback:

   • "👍 Yes" / "👎 No" buttons at the bottom of the docs layout.

2. Optional Context:

   • If "No" is clicked, optionally expand a small text area asking "What went wrong?" (e.g., "Outdated", "Confusing", "Example didn't work").

3. Analytics Integration:

   • Send this event data to the existing analytics provider (Google Analytics or similar, if configured) or log it to a service like Netlify Forms (since the site is hosted on Netlify).

4. GitHub Issue Link:

   • Provide a "Report an issue on GitHub" link next to the feedback widget for more detailed bug reports.

Technical Feasibility

• Implementation: Docusaurus Swizzle feature can be used to wrap the DocItem component or append to the DocItemFooter.
• Backend: Netlify Forms is a great zero-config backend for this since netlify.toml is present in the repo.
• Scope: ~2 weeks.
  • Week 1: Swizzle DocItemFooter component and build UI.
  • Week 2: Integrate with Netlify Forms or Analytics API and style it to match the theme.

Value

Provides a passive, low-friction channel for improving documentation quality, essential for complex tools like OpenRefine.

Start by locating the Docusaurus DocItemFooter swizzle entry point and reading netlify.toml. Check whether an analytics provider is configured before deciding between analytics and Netlify Forms. Done means every documentation page has the binary feedback UI, optional context for negative feedback, and a GitHub issue link with the chosen submission path working.