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: CONTRIBUTING.md
+34-3Lines changed: 34 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,8 +18,9 @@ Follow these steps when making changes. That way, they will most likely be accep
18
18
19
19
1. Fork the [newtonscript.github.com](https://github.com/NewtonScript/newtonscript.github.com) project on GitHub.
20
20
2. Create a topic branch from the `master` branch. Name your branch appropriately, reflecting the intended changes. (e.g. “new-license”, “style-overhaul”, or “responsive-design-fixes”)
21
-
3. Make commits in logical units and with explanatory commit messages.
22
-
4. Preview your changes in an HTML5-capable web browser to ensure nothing is broken and everything is rendering correctly.
21
+
3. Make your edits (please try to conform to our [style guide](#style-guide)).
22
+
4. Make commits in logical units and with explanatory commit messages.
23
+
5. Preview your changes in an HTML5-capable web browser to ensure nothing is broken and everything is rendering correctly.
23
24
24
25
SUBMITTING CHANGES
25
26
------------------
@@ -31,4 +32,34 @@ When you’ve completed your changes and are ready to merge them into the main p
31
32
32
33
That’s all there is to it.
33
34
34
-
If you followed the “Making Changes” guidelines and the changes are aligned with the vision of the project, it should be a smooth process to merged them.
35
+
If you followed the “Making Changes” guidelines and the changes are aligned with the vision of the project, it should be a smooth process to merged them.
36
+
37
+
<aname="style-guide"></a>STYLE GUIDE
38
+
-----------
39
+
40
+
## HTML
41
+
42
+
* Please write well-formed HTML to the HTML5 specification.
43
+
* Please write pretty HTML with proper indentation for nested elements.
44
+
* Please use tabs instead of spaces for indentation.
45
+
46
+
## Text
47
+
48
+
* Please alphabetize referenced materials (software, source code, reference documentation, etc.) by title and authors by last name.
49
+
* For sub lists which are more appropriately listed in chronological order (e.g. lists of publication issues), please do so.
50
+
* Please use [serial commas](https://en.wikipedia.org/wiki/Serial_comma).
51
+
52
+
## Resource Template
53
+
54
+
The following is the template used to list referenced resources (software, source code, documentation, etc.):
0 commit comments