Is static right for my site?
What you'll have at the end
A yes, a no, or a "yes, for part of it", in five minutes.
The checklist
Answer each question for the public part of your site.
| Question | Static suits it when |
|---|---|
| Do visitors mostly read and look? | yes |
| Does the content change a few times a day or less? | yes (a build takes minutes, not seconds) |
| Do visitors need to sign in to see things? | no |
| Do visitors buy or pay on the site? | no |
| Are forms the heart of the site (bookings, applications)? | no; one contact form is fine |
| Is the site under 1 GB with no single file over 100 MB? | yes, for GitHub Pages (limits) |
| May all of it be public? | yes, or you leave the rest out (Keep private content private) |
Good fits
- A brochure site for a business, a club or a practice.
- A blog or a news section.
- Documentation and handbooks.
- A portfolio or a personal site.
- An event or conference site.
- A nonprofit, a school, a community group or a public information site.
Poor fits
- A shop: GitHub's terms rule it out, and a basket needs a server.
- A members' area or intranet: whatever is behind a login is never in the copy.
- A site that lives on forms and search results, such as booking or directory sites.
- Content that changes every minute (live scores, stock levels).
Part of a site
A mixed site can still use it: publish the public pages statically and leave the rest on your own hosting. Leave pages out by path or section (step 7 of the wizard); links to them go to your live site.
Next step
Yes? Make a free website in 15 minutes. Not sure what visitors will miss? Search, forms and comments on a static site.