Publish the result of your build
A static site serves HTML, styles, scripts and images. Your source may use a framework or generator, but visitors receive the generated files. Keep the output directory explicit and inspect it before publishing. Use readable URLs and direct links to individual articles.
Design for the first visit
Readable HTML should arrive before optional interactions. Give images dimensions, compress large files and defer scripts that do not affect the first screen. Test with a keyboard and at a narrow viewport. Meaningful headings, visible focus and descriptive links help visitors on many devices.
Keep caching consistent
Versioned asset names let a browser keep unchanged files while a new page points to a new build. HTML needs a different caching strategy because it connects visitors to current assets. Keep older versioned files available for already-open pages. A form needs a deliberate processing service if it is meant to submit data.