Static Website Builder

Start with the pages you need

List the pages a visitor must reach, the content each page needs, and the person who will maintain it. A small portfolio might need a homepage, project pages, an About page, and an email link. A publication also needs consistent article layouts, topic archives, image handling, and a repeatable update process.

Give every route an owner and a reason to exist. This makes the architecture easier to review than a list of framework features. Write a sample article and a sample project page before selecting a theme; real content exposes layout problems that a polished demo can hide.

Choose the right authoring layer

Plain HTML keeps a small project understandable. Hugo brings reusable layouts to a content collection. Astro suits teams that want components and carefully chosen browser interactions. An existing CMS can remain your editing environment if a separate process produces a complete public export.

These options change how you work before publication. The deployment should still contain the pages, styles, images, and scripts the visitor actually needs. Check that output directly instead of judging only the development preview.

Define the static boundary

A browser can open a menu, expand a disclosure, or run a local calculation. Saving a shared submission, authenticating an account, and sending a newsletter require additional services. A plain file export does not inherit those services from its source system.

For a self-contained site, keep every essential journey inside the published pages. Use working navigation and descriptive email links. Rebuild when public content changes, keep the previous release, and check nested URLs after uploading. The builder selection guide walks through these decisions in more detail.

Questions about Start with static

Does a static website need a framework?

No. Hand-authored HTML, CSS, and a little JavaScript are enough. A generator becomes useful when repeated layouts and growing content make manual edits harder to maintain.

Can a static website be interactive?

Yes. Browser JavaScript can provide interactions. Features that need private data, persistent shared storage, or server processing require an additional service and a deliberate architecture.

Primary reference: MDN: client–server overview.