You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,14 +5,13 @@ The OpenChain Education Work Group is working on making it easier to access, con
5
5
6
6
We plan to do this through providing the source material in MarkDown. People can change it into PDF documents, Word documents and other formats from there.
7
7
8
-
The reason for this change is to allow people to easily contribute to our editing via our Reference Library. This is hosted on GitHub and it favors formats like MarkDown that are basically text.
8
+
The reason for this change is to allow people to easily contribute to our editing via our Reference Library. This is hosted on GitHub and it favors formats like MarkDown that are basically text.
9
9
10
10
Our first step is to convert some existing documents into MarkDown. This will allow us to begin editing and updating them.
11
11
12
12
There is an online tool to convert Word documents to MarkDown, which is the first step of the process. You will find it here:
@@ -25,9 +24,11 @@ If you convert one of these documents to MarkDown, please open a Pull Request to
25
24
Now you can help with updating the documentation! The process is the same. Update the MarkDown and submit a pull request.
26
25
27
26
There is a small learning curve to take part in this new drive. However, it is quick, easy and free to get a graphical editor for MarkDown. Download it here:
28
-
<https://panwriter.com>
27
+
<https://panwriter.com>. Of course, this is only one of the tools that you can use, as MarkDown is supported by many editors.
29
28
30
29
Then download background tools for MarkDown:
31
30
<https://pandoc.org/installing.html>
32
31
33
-
That’s it! You are ready to help. We look forward to working together to make sure even more people can take advantage of our reference library as they work towards a more trusted, more efficient and more effective supply chain.
32
+
You might want to try using `git` directly at home, so that you can `clone` the repo, `commit` changes to it, `branch` the repo to include your modification in a separate branch, `push` the branch with your changes and any subsequent commits you add. While it is largely unnecessary, by getting familiar with the tool you could later exploit all the power of it.
33
+
34
+
That’s it! You are ready to help. We look forward to working together to make sure even more people can take advantage of our reference library as they work towards a more trusted, more efficient and more effective supply chain.
0 commit comments