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: pages/docs/contributing/contributing-docs.md
+16-7Lines changed: 16 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,35 @@
1
1
---
2
2
title: Contributing to Documentation
3
-
sidebar: docs_sidebar
3
+
sidebar: main_sidebar
4
4
permalink: contributing-docs
5
5
folder: releases
6
6
---
7
7
8
8
We (like almost all open source software providers) have a documentation dillemma... We tend to focus on the code features and functionality before working on documentation. And there is very good reason for this, we want to share the love so nobody feels left out!
9
9
10
+
The following documentation page assumes one is running on OS X, but if you are not, you should be able to easily transpose the necessary commands to your operating system of choice.
10
11
11
-
## Setting up Development
12
+
13
+
## Setting Up Your Development Environment
14
+
15
+
### Installing Dependencies
16
+
Initially (on OS X), you will need to setup [Brew](http://brew.sh/) which is a package manager for OS X and [Git](https://git-scm.com/). To install Brew and Git, run the following commands:
To contribute to the web based documentation, you should obtain a GitHub account and fork the <ahref="https://www.github.com/singularityware/singularityware.github.io"target="_blank">Singularityware site</a> repository. Once forked, you will want to clone the fork of the repo to your computer. Let's say my Github username is vsoch, and I am using ssh:
24
+
To contribute to the web based documentation, you should obtain a GitHub account and *fork* the <ahref="https://www.github.com/singularityware/singularityware.github.io"target="_blank">Singularity GitHub Pages</a> repository by clicking the *fork* button on the top right of the page. Once forked, you will want to clone the fork of the repo to your computer. Let's say my Github username is *user99*:
This step is required if you want to render your work locally before committing your changes. For the purpose of simplicity, we will articulate how to install Jekyll and its dependencies on a Mac.
32
+
This step is required if you want to render your work locally before committing the changes. This is highly recommended to ensure that your changes will render properly and will be accepted.
23
33
24
34
```bash
25
35
brew install ruby
@@ -34,8 +44,7 @@ Now you can see the site locally by running the server with jekyll:
34
44
bundle exec jekyll serve
35
45
```
36
46
37
-
This will make the site viewable at `http://localhost:4005/` If you want a nice look into how this works, you will probably want to look into the <ahref=""target="_blank">config</a> file, or post a question to one of the <ahref="/support"target="_blank">support places</a>.
38
-
47
+
This will make the site viewable at <ahref="http://localhost:4005/"target="_blank">http://localhost:4005/</a>.
0 commit comments