Before you start
A static practice site, version control and hosting you already control. Do not change domain records during this exercise.
Why this lesson exists
This site’s move to GoDaddy uses a GitHub workflow to publish reviewed files. The general lesson is a repeatable release process, not a requirement to use a particular host.
Do the exercise
Identify the actual source
Choose one repository and one output directory. Document the command that creates or validates the site. Keep credentials out of the files that will be served.
Preview the complete journey
Open the home page, one guide, a contact route and a missing URL. Test on a phone-sized screen. Verify local links and image paths before upload.
Separate validation from publishing
Have the workflow validate first, then upload only the intended output directory. Use the host’s encrypted transport and repository secrets for credentials. Start with a non-production destination when available.
Verify the live release
Check the public URL, images and nested pages after deployment. Compare a visible changed detail with the preview. Keep the prior commit and hosting configuration so a failed release can be reversed.
A prompt to adapt
Replace the bracketed parts with your own practice details.
Review this static-site release plan: [plan]. Identify the source repository, build/output directory, validation checks, encrypted upload method, secret storage, live verification and rollback. Flag any step that could affect unrelated sites. Do not change DNS or publish until the concrete destination and files are clear.
What this looks like
A green build with a skipped upload job is not a live deployment. A successful upload still needs a check at the public URL and on a nested page.
Check your result
Use evidence from your output. A confident explanation from the AI is not enough.
- Only the intended site directory is published.
- Credentials are excluded from served files and source.
- The live result and rollback point are verified.
If it isn’t working
If the home page works but guides fail, check nested paths, document root and server routing. Avoid changing DNS as a first response to a file-path problem.
Optional. Progress stays in this browser.
Where this came from
An original foundation lesson developed for this learning hub, informed by the site’s build and publishing workflow. Sources and approach.
Prepared September 2026. Tools and interfaces change; use current official setup instructions. Session lengths are estimates.