Note 07 · Practice
Review the files that will actually be public
A working folder can contain drafts and local settings. A publication should be a separate, small collection whose contents are easy to account for.
Start from an explicit release
Build the pages and their local resources into a new directory. Keep editing notes and configuration outside that tree. A short file list helps reveal accidental additions, such as a backup copy or an unfinished document. The published directory should contain only material intended for every visitor.
Check successful and missing requests
Follow the home, index, about and article routes. Confirm that the style sheet and icon load, and that a deliberately missing path returns a clear not-found response. A successful home page alone leaves much of the release unchecked. Review the actual text as well as response status.
Keep the previous release available
A new directory makes comparison and recovery easier than editing the live files in place. Keep a record of which release was published and when. If a problem appears, compare the two trees before making another change. A small, deliberate release process is usually enough for a small static site.