modified CONTRIBUTING.md

[robertnjenga]

Fixes #5588

What changes did you make?

• Replaced:

2. Complexity: Good second issue

• Self-assign an issue with the Complexity: Good second issue label.
• Complete steps in 2.7 Working on an issue to create a solution for the issue
• Complete steps in 3.1 How to make a pull request to get your solution reviewed by the website-merge team
• Once your pull request is merged, you can work on your next issue.

Progress through issues with increasing complexity in the following order:

1. Good first issue
2. Good second issue
3. Small
4. Medium
5. Large

• With:

2. Repeat Use front matter loader to import markdown content, start on switchin… #1 with a new good first issue

Progress through issues with increasing complexity in the following order:

1. Good first issue (x2)
2. Small
3. Medium
4. Large
5. Extra Large

Why did you make the changes (we will use this info to test)?

• to remove references to "good second issue" from CONTRIBUTING.md in order to avoid confusion, since we are no longer creating issues with the label `Complexity: good second issue'.

For Reviewers:

• Do not review changes locally, rather review changes at https://github.com/robertnjenga/website/blob/issue-branch-5588/CONTRIBUTING.md

Screenshots of Proposed Changes Of The Website (if any, please do not screen shot code changes)

No visual changes have been made.

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

From your project repository, check out a new branch and test the changes.

git checkout -b robertnjenga-issue-branch-5588 gh-pages
git pull https://github.com/robertnjenga/website.git issue-branch-5588

[Thinking-Panda]

Availability: Weekdays
ETA: 10/4

[DorianDeptuch]

Availability: Weekday afternoons/evenings
ETA: EoD 10/5

[Thinking-Panda]

@robertnjenga nice work on this issue. Branches are setup correctly, code changes are as mentioned in the issue and clean. The changes are reflecting in the test link provided. Thank you!

[DorianDeptuch]

Hi @robertnjenga ,

Thanks for taking up this issue. You correctly stated what changes were mad, why they were made, and you linked to the updated template on your forked repo. It was a little hard to read through the "What" and the "Why" sections at first due to the formatting. The correct changes were made in the template and everything else looks good. Great job!

[adrianang]

Hi @robertnjenga — good job with this issue so far! The branching is set up correctly, the corresponding issue is linked, the change of updating step 2 and the progression outlined in the CONTRIBUTING.md document has been made exactly as requested, and this change is reflected in your branch of the document.

Before I can merge this issue, there's just one change that should be made: can you remove the details and summary tags in the Screenshots section of your PR and instead state that no visual changes have been made? Doing this will help keep our documentation clean and easy to use (by indicating at a quick glance that there were no visual changes).

Once the PR has been correctly edited, I can merge this PR to the codebase; everything else is looking good so far!

[adrianang]

Hi @robertnjenga — thank you for making the edit in your PR! It looks good to me and everything else had stayed the same from the last review.

Thank you for taking up and completing this issue! 🙌🏼