Publish a static site with a repeatable update path https://patrickz.ai/learn/publish-and-update-a-static-site/ OUTCOME Plan a site release with validation, a preview and a rollback checkpoint. YOU NEED A static practice site, version control and hosting you already control. Do not change domain records during this exercise. 1. 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. 2. 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. 3. 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. 4. 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. PROMPT 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. EXAMPLE / EXPERIMENT 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 [ ] 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 FAILS 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. MY RESULT / NEXT CHANGE