Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Prepare a page you can recognize
Open the local P1 page. Which practice repository and hosting project will you use?
Review your work
Names a separate practice repository and hosting project.
Identifies the visible P1 marker on the opened local page.
2. Review and send the change to GitHub
What files did you send, and can you find the intended homepage in the remote practice repository?
Review your work
Lists the intended public website files and checks that private files are excluded.
Confirms the remote repository contains its homepage at the publishing root.
3. Connect the repository to hosting
Does the signed-out public URL show your P1 page? If not, what do you actually see?
Review your work
Reports the signed-out public URL’s actual page or error.
Uses the P1 marker to distinguish the intended page from a different deployment.
4. Trace a stale public page
Which version do the repository, host and public page currently show? Where does the mismatch begin?
Review your work
Records the version observed in GitHub, the hosting deployment and the public page separately.
Locates the first mismatch and chooses a check at that stage.
5. Publish and verify P2
Provide your P2 result and the checks that show the intended edit reached the public page.
Review your work
Connects the public P2 result to the matching repository change and deployment record.
Reports a browser check of the actual edited content or action.