Static websites. A moving workflow.
A static website serves prepared files, but the work around those files still needs structure. Keep authoring, review, generation, and publication connected without adding a live database to the public site.
Publish an artifact, not a repository
Define the directory that contains the final HTML, CSS, scripts, and public assets. Inspect that directory for accidental drafts, archives, or private configuration. Store a reviewed copy with its source revision so the published result is identifiable.
Keep paths predictable
Use directory-based pages with index documents when your static host supports them. Maintain one consistent URL shape in navigation, canonical metadata, sitemap entries, and feeds. Test direct deep links over HTTP; a file opened from a desktop folder is not the same hosting environment.
Plan for replacement and recovery
Prefer publishing an intact release when your host provides that option. Keep the previous artifact and a short verification routine. Remember that reverting static files does not necessarily revert external services, remote embeds, or configuration outside the public directory.