[Suggestion]: Add "Edit this page" button to the bottom of each documentation page
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11.8k
- Forks
- 7.9k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 11
Description
Summary
Implement an "Edit this page" button at the bottom of each documentation page, linking directly to the corresponding Markdown file on GitHub, allowing users to easily suggest improvements and corrections.
Example in Docusaurus:
Page
No response
Details
To encourage community contributions and streamline the process of updating documentation, it would be helpful to add an "Edit this page" button at the bottom of each documentation page. This button should link directly to the corresponding Markdown file in the GitHub repository, making it simple for users to suggest edits or fix errors.
Acceptance Criteria:
- Add an "Edit this page" button to the bottom of each documentation page.
- Ensure that the button links directly to the Markdown file in the GitHub repository.
- The link should open in edit mode if possible, so users can quickly make changes and propose pull requests.
- The button should be styled consistently with the rest of the documentation site and be easy to find.
Additional Notes:
Please ensure that links point to the correct branch (e.g., main or docs) in the repository so users are editing the most up-to-date version of the file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the documentation page rendering entry point and how each page maps to its Markdown file on GitHub; then verify the bottom-of-page button, correct branch and edit-mode URL, consistent styling, and links for representative pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100