Changeset 13758
- Timestamp:
- 03/09/2024 04:42:45 AM (2 years ago)
- File:
-
- 1 edited
-
trunk/docs/contributor/documentation/README.md (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/docs/contributor/documentation/README.md
r13671 r13758 19 19 > To write documentation resources so that they can be displayed immediately into the BuddyPress GitHub repository and synchronized with a documentation website of the [BuddyPress.org network](https://buddypress.org) (in a near future, once we have a v1 ready), you need to use the [GitHub Markdown](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) language. 20 20 21 That being said, if code writers are very comfortable with Markdown, GitHub and coll obarating using Pull Requests, some of you might find it too complex. If so, no worries: our main challenge is to have an up to date **content** for our documentation resources.21 That being said, if code writers are very comfortable with Markdown, GitHub and collaborating using Pull Requests, some of you might find it too complex. If so, no worries: our main challenge is to have an up to date **content** for our documentation resources. 22 22 23 23 ### Contributing without GitHub … … 50 50 Each contribution needs to be organized as a Pull Request (PR) to the BuddyPress GitHub main branch (master). If you're familiar with GitHub and use it locally along with your Favorite editor, it's the exact same process than pulling a request for a code contribution. 51 51 52 The steps we're detail ling below are explaining how you can still contribute to docs if you have no clue about GitHub thanks to their website features.52 The steps we're detailing below are explaining how you can still contribute to docs if you have no clue about GitHub thanks to their website features. 53 53 54 54 > [!IMPORTANT]
Note: See TracChangeset
for help on using the changeset viewer.