Merge pull request #10714 from opf/how-to-guide-docs

Adds a quick starter guide for non-techies on how to setup the tools to contribute to the docs
task/42759-new-wording-for-note-in-the-english-user-guide
Niels Lindenthal 2 years ago committed by GitHub
commit 1cd2559444
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      docs/development/contribution-documentation/contribution-support/README.md
  2. 2
      docs/development/contribution-documentation/documentation-process/README.md
  3. 2
      docs/development/contribution-documentation/documentation-style-guide/README.md
  4. 134
      docs/development/contribution-documentation/documentation-tool-setup/README.md
  5. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524201335248.png
  6. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524201506732.png
  7. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524202802004.png
  8. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524204624785.png
  9. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524205416700.png
  10. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524205510769.png
  11. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524210503915.png
  12. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524210811330.png
  13. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220524211008555.png
  14. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220525074657702.png
  15. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220525075957387.png
  16. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220525080127187-16534605509021.png
  17. BIN
      docs/development/contribution-documentation/documentation-tool-setup/image-20220525080127187.png

@ -1,7 +1,7 @@
---
sidebar_navigation:
title: Support for contribution
priority: 997
priority: 996
description: What to do if you need help or support for your contribution
robots: index, follow
keywords: help, support, documentation process, documentation

@ -1,7 +1,7 @@
---
sidebar_navigation:
title: Documentation process
priority: 999
priority: 998
description: The process of how to contribute to the OpenProject documentation
robots: index, follow
keywords: contribution, documentation, documentation process

@ -1,7 +1,7 @@
---
sidebar_navigation:
title: Documentation style guide
priority: 998
priority: 997
description: What styles and formats to follow when contributing to the OpenProject documentation
robots: index, follow
keywords: documentation style guide, style guide, format, style

@ -0,0 +1,134 @@
---
sidebar_navigation:
title: Tool setup
priority: 999
description: Setup the tools to easily contribute to the OpenProject documentation
robots: index, follow
keywords: contribution, documentation, documentation process, tool setup
---
# Setup the tools to easily contribute to the OpenProject documentation
This guide aims to help users that are new to Git and Markdown to contribute to the OpenProject documentation. There are a two very helpful tools that makes it extremely easy to contribute to OpenProject:
| Tool | Purpose of this tool | Website and download |
| ------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| **Git** | Git is a software for tracking changes in any set of files, usually used for coordinating work among programmers collaboratively developing source code during software development. | [https://git-scm.com/downloads](https://git-scm.com/downloads) |
| **Typora** | Typora is an application that enables you to easily edit markdown files. The markdown file format is used used for the OpenProject documentation which allows you to focus on the content instead of the formatting. | https://desktop.github.com/ |
| **GitHub desktop client** | Desktop is an application that enables you to interact with GitHub using a GUI instead of the command line or a web browser. | https://typora.io/ |
## Step 1: Install Git
If you do not already have Git installed, you can download and install the latest version of Git from [https://git-scm.com/downloads](https://git-scm.com/downloads).
## Step 2: Install Typora
You can download the installer from the website https://typora.io/#download. Follow the prompts to complete the installation. In case you need more information there are very detailed [help](https://support.typora.io/) for each supported operating systems [Linux](https://support.typora.io/Typora-on-Linux/), [macOS](https://support.typora.io/Typora-on-macOS/) and [Windows](https://support.typora.io/Typora-on-Windows/).
## Step 3: Install GitHub desktop client
You can install the GitHub desktop client on any [supported operating systems](/desktop/getting-started-with-github-desktop/supported-operating-systems). To install GitHub Desktop client navigate to [https://desktop.github.com/](https://desktop.github.com/) and download the appropriate version for your operating system. Follow the prompts to complete the installation.
## Step 4: Sign in into Github.com in GitHub desktop client
You need an account on GitHub.com to contribute to the OpenProject documentation. To exchange data between your local and remote repositories you need to first sign (File -> Options -> Sign in).
![image-20220524201335248](image-20220524201335248.png)
In the next screen click on "Continue with browser".
![image-20220524201506732](image-20220524201506732.png)
This opens your browser. To authenticate to type your GitHub.com credentials and click **Sign in**. If you have configured two-factor authentication (2FA) for GitHub enter your 2FA code in the prompt on GitHub and click **Verify**.
Alternatively, if you were already signed in to GitHub, follow the prompts to return to GitHub Desktop to finish authenticating.
After authenticating your account, you are ready to manage and contribute to projects with the GitHub desktop client.
## Step 5: Fork the OpenProject repository
If you are an external contributor you don't have write permissions on the repository https://github.com/opf/openproject/. In this case you need to fork the repository first. This basically means that you have your own copy of the repository on GitHub.com. Since it is your own repository you have write privileges here.
![image-20220524202802004](image-20220524202802004.png)
## Step 6: Clone the OpenProject repository in the GitHub desktop client
Before you can make changes you need to create a local clone of the OpenProject repository on your local computer. Open the GitHub desktop client and navigate to "File -> Clone repository".
![image-20220525075957387](image-20220525075957387.png)
In the modal window select the repository you forked in Step 5. Also select a folder on your computer for the cloned repository. Click "Clone".
![Clone a repository](image-20220525080127187-16534605509021.png)
In the next screen select "*To contribute to the parent project*".
![image-20220525074657702](image-20220525074657702.png)
## Step 7: Create a new Git branch for your change
Select the latest release branch e.g.`release/12.1` as the current branch.
![image-20220524204024162](C:\Users\nlind\AppData\Roaming\Typora\typora-user-images\image-20220524204024162.png)
In the same drop down click on "New branch". In this window insert a branch name select the latest release branch e.g. `release/12.1`.
![image-20220524204132363](C:\Users\nlind\AppData\Roaming\Typora\typora-user-images\image-20220524204132363.png)
## Step 8: Fetch origin (update local repository)
Every time you start editing please make sure you have fetched the latest changes from GitHub.com by clicking on "Fetch origin" in the main toolbar:
![image-20220524204624785](image-20220524204624785.png)
## Step 9: Open the files you want to change in Typora
In Typora open the files you want to change (File -> Open). In the file picker navigate to the local folder you selected in the step 6.
## Step 10: Make the changes in Typora and save the file
The Typora editor makes it quite easy to make changes to the file. After you made your changes do not forgot to save.
## Step 11: Commit the change to your local repository in the GitHub desktop client
Open the GitHub desktop client. Here you can see all the changes you made in the local repository.
![image-20220524205416700](image-20220524205416700.png)
Add a commit message that best describes your change. This description should allow other users to easily understand the change you made.
## Step 12: Push your changes to GitHub.com
At the moment your change is only available in your local repository. To make it available on GitHub.com you need upload (push) by pressing the button "Push origin".
![image-20220524205510769](image-20220524205510769.png)
## Step 13: Create a pull request
A pull request is a workflow to ask for a review from the OpenProject team. With a pull request you basically ask to check your changes and to copy it over to the OpenProject repository (opf/openproject). Navigate to https://github.com/opf/openproject/pulls/compare.
Here select the latest release branch e.g. release/12.1 in the first dropdown. In the second select the branch you have changed.
![image-20220524210503915](image-20220524210503915.png)
In the description field of the pull request enter a summary for the changes you made. If there is already a work package on community.openproject.org you can also add this to the description. This adds a relation between your pull request and the work package.
## Step 14: Request review
Select the label "documentation".
![image-20220524210811330](image-20220524210811330.png)
In the field "Reviewers" select "opf/doc-writers".
![image-20220524211008555](image-20220524211008555.png)
## Step 15: Wait for feedback from the reviewers
... and hopefully it is all LGTM which means "Looks good to me(rge). Congrats to your first contribution to the OpenProject documentation. We appreciate your effort :-)
Loading…
Cancel
Save