Skip to content

Commit 187d12d

Browse files
committed
Rearrange repo instructions section
1 parent 800f48e commit 187d12d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,16 +81,16 @@ Regardless of the complexity of a change, when you wish to make a contribution o
8181

8282
### Repo Specific Instructions
8383

84-
#### [TOP Website Repo](https://github.com/TheOdinProject/theodinproject)
85-
86-
Before starting any work on our main website repo, you must read and follow the instructions found on [The Odin Project Wiki](https://github.com/TheOdinProject/theodinproject/wiki). These instructions will help you get the TOP app running locally, and help you with adding new paths, courses, sections, and lessons.
87-
8884
#### [TOP Curriculum Repo](https://github.com/TheOdinProject/curriculum)
8985

9086
When submitting a PR for a new lesson, or when you are making significant changes to an existing lesson, you must follow our [Layout Style Guide](https://github.com/TheOdinProject/curriculum/blob/main/LAYOUT_STYLE_GUIDE.md). This helps ensure the layout and formatting is consistent across all of our lessons.
9187

9288
If you're new to contributing to open-source, or if you just want to make a really quick PR, you can click the "Improve this lesson on GitHub" link found at the end of each lesson instead of going through the steps to fork + clone one of our repos.
9389

90+
#### [TOP Website Repo](https://github.com/TheOdinProject/theodinproject)
91+
92+
Before starting any work on our main website repo, you must read and follow the instructions found on [The Odin Project Wiki](https://github.com/TheOdinProject/theodinproject/wiki). These instructions will help you get the TOP app running locally, and help you with adding new paths, courses, sections, and lessons.
93+
9494
### Check Before Doing Anything
9595

9696
It's important that you look through any open issues or PRs in a repo before attempting to submit a new issue or work on a change, regardless of the complexity. This will help avoid any duplicates from being made, as well as prevent more than one person working on the same thing at the same time.

0 commit comments

Comments
 (0)