-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move CONTRIBUTING.md to documentation site #2008
Comments
@AetherUnbound I'd like to pick this up |
Thanks, @shivamganwani! Please just ping |
@WordPress/openverse-maintainers Now I click on the link and it takes me to contributing guidelines page. All good till now.
Here comes the issue, all these links take me to 404 Not found. Can someone explain if this is really an issue or am I doing something wrong. |
Ah, great find @shivamganwani! We recently restructured our documentation (#1846) and that probably caused all those links to break. Here are the new ones:
|
@AetherUnbound so we're making a separate ticket or fixing this in this one? |
Do you mind including that in your changes in #2030? 😄 |
Not at all @AetherUnbound |
Description
Our current contributing guide exists locally in the repository: https://github.com/WordPress/openverse/blob/523a3599c34463275ce57c4e4ce6c14de1baefbd/CONTRIBUTING.md
It would be ideal to move this into the documentation site at docs.openverse.org, where most of our other quickstart/contributor information exists!
Note: When we convert this into Sphinx, we should also emphasize further the verbiage about choosing more than one good first issue - https://github.com/WordPress/openverse/blob/209cd44abed611ae4a2ef97ea77e8d2b0b612a53/CONTRIBUTING.md#friendly-notes (we've had a few folks ask about this, so it seems useful to highlight it better).
This would involve moving the file from it's current position into
documentation/general
, adding a callout for the above using a MyST callout, and then linking from the currentCONTRIBUTING.md
to the new location on the docs site.The text was updated successfully, but these errors were encountered: