This guide tells you how to request and edit a page using GitHub.
Prerequisites:
- Basic knowledge of Markdown. All you need to know is in our markdown cheat sheet
- A GitHub account. If you do not have one, create a free GitHub account before you start.
Announce and discuss your proposal through a GitHub Issue
- Go to the RDMkit repo on GitHub.
- Click “Issues” in the top menu bar and look at the existing issues. See if your idea or suggestion is already being discussed.
- If an issue exists, comment and let people know if you want to contribute.
- If no relevant issue exists, create a new one: click the green “New issue” button on the right and choose a template. You can find more information on creating issues in the GitHub documentation.
- Discuss your idea with the editors through comments in the issues – you will be notified when others comment.
- You can read the comments and write your opinion/questions/answers in the “Leave a comment” box. To submit your responses, click the green “Comment” button on the right.
- You can always return to your opened issue by going to the issues section of our GitHub repo.
Tip: You can also get to the RDMkit repo on GitHub using the ‘GitHub’ link in the header of this site.
Read the guides
Before starting editing on GitHub:
- Make sure you are following our style guide.
- Follow the structure of the provided template for the page you wish to create or update.
- We use markdown. To learn how to create paragraphs, headings, format text, add links and images and much more, follow our markdown cheat sheet.
- Our pages contain metadata. Read more about them in our page metadata guide.
Tip: For more information on writing and formatting, visit GitHub’s documentation.
Start editing
Important: Only move to the following steps if you and the editors have agreed on your plans and you have read the guides.
- Find where to edit on GitHub
- If you want to contribute to an existing page, go to the page on the site and click the “Edit me” pencil icon next to the page title
- If you want to create a new page, the editors will provide a link to the page as a comment in your GitHub issue. The page will come with a predefined template based on the kind of content you want to contribute.
- You will be taken to the correct GitHub repository, where you will look for a pencil icon on the top right.
Linking resources and other pages (optional)
- If you have mentioned tools or resources in your text, you will have to add them to the tool and resource list.
- If you want to list training material or link to other RDMkit pages, add it to the page metadata. Read more on how to do this in our page metadata guide.
Important: In general terms, you must avoid manual interlinking of RDMkit pages.
Submit your first draft
- When you are happy with your first draft, go to the “Propose changes” section at the end of the page and write a title and a brief explanation of your changes.
- Click “Propose changes”.
- Create a pull request following GitHub’s documentation
- In the description of your pull request, link the issue related to this change by typing a hashtag # and the issue number. Suggestions will appear.
Tip: You can create a draft pull request when you’re not ready to submit and will need to work more on it later. You can find more information about draft pull requests in the GitHub documentation
Tip: You can return to your pull request by going to the pull request section of our GitHub repo.
Address editors’ reviews by editing your pull request
When editors add comments or add a review of your pull request, you will be notified. To address comments, you must edit your pull request:
- Go to your pull request. You can return to it by going to the pull request section of our GitHub repo
-
- Click on “Files changed” in the top menu bar.
- Click on the icon with 3 dots “…” of the file you want to edit and then click on “Edit file”.
- Make your changes.
- Click on “Commit changes”.
- Follow GitHub documentation for more information.
When all the requests have been addressed, the editors will mark the conversation as “Resolved” and the proposed changes as “Approved”. This means your content is ready to be published on the main website.
Tip: You can also edit your pull request any time if you change your mind about anything in your pull request and the request is not closed yet.