docs: Finish tutorial for page review

[strixy16]

Steps

• Assign yourself so it's tracked who did the review
• Check whether it is an entire new page or an update
• Read over the page thoroughly
• Leave comments if updates are needed, approve or request updates
• Delete branch once merge is complete

[jjjermiah]

from #8 Need to have a process outlined for lab members to follow when adding a page to the handbook.

Things to consider

• Branching protocol: individual branch for individual page? Deleted when merged?
• Code review: a separate lab member and anyone else?
• Merging: who is able to merge the pages? The code reviewer?

[jjjermiah]

from #7

Make a tutorial for lab members to use to add pages to the handbook. Can present this at the beginning of any group development session and have it for them to refer back to

Steps could include:

• Setting up local copy of repository
• Making a branch for their page
• Some kind of Markdown overview OR how to get Markdown out of Google docs if that works
• Pushing the page to their specific branch
• Assigning a lab mate for code review

And then a section on how to do code review.

I have a suggestion for this that I discovered in making the tutorial for page making.

If the first step for making a new page is making an issue, it gives you the opportunity to make a branch immediately associated with it. It's on the right side of the page under Development.

Once it's made, it prompts you to checkout the branch locally.

This might simplify how that setup works for newer Git users, as opposed to using git checkout and such. Could be good to provide both alternatives

[jjjermiah]

just consolidating the similar tasks *

[jjjermiah]

closed by #23 and #24