8. Beginning your site customization

8.1. High Level Goals today

Important

Read all of the instructions before you start

1. Work in a Codespace to implement one content/feature addition to your site

2. Create a pull request for your work.

3. Open a codespace to preview a partner’s work and give them feedback on their PR.

4. (if time) begin any revisions from your partner’s feedback.

8.2. Detailed Instructions

8.2.1. Work in a Codespace to implement one content/feature addition to your site to practice HTML

1. choose a section to work on that is a theme variable

Hint

On an Issue, if you have a checklist, you can hover over items to make separate issues for each item and it will track progress on the first issue

Warning

If you cannot open a new codespace, look for one on the list that does not have uncommitted changes on your list of all codespaces on the 3 dots menu, select “stop codespace”

2. make an issue for the specific task

3. Under “Development” click create a new branch

4. on that popup choose open in codespace

5. reinstall nox on your new codespace with pip install -U nox

6. start your server with nox -s docs-live

7. find or create th right file and edit it

8. preview your site to see that it works

9. Go to the git tab in your code space (on the very left edge: )

10. Type a commit message above the commit button

11. commit the changes to the feature-specific branch

12. sync to GitHub

8.2.2. Create a pull request for your work.

Tip

when you go to your PR tab, (or even your cdoe tab ) it might have a helper for you to do this step

1. on GitHub.com, go to pull requests

2. click new pull request, select the branch for the compare

8.2.3. Open a codespace to preview a partner’s work and give them feedback on their PR.

1. go to your partner’s repo

2. switch to the branch

3. click the green code button, open a codespace

4. preview the version of their site

5. on github.com, go to the pull request

6. leave specific comments by clicking + next to the line where you want to comment. For help see reviewing a PR

7. leave general comments by clicking on review

8. then select approve or request changes

9. submit the review

8.2.4. (if time) begin any revisions from your partner’s feedback or work on a second addition

Follow steps similar to the ones in the first step

8.3. Help

8.3.1. Tips

• You can link issues to pull requests to mark them done automatically when you merge the pull request