HTML hosting is folder hosting
If you can save a .html file, you can understand HTML hosting. The browser requests a URL; the host returns a file. CSS and JavaScript are other files the HTML points to. Images too. That network of files *is* the website.
StaticHost stores that network for you and serves it over HTTPS. It will not teach HTML and it will not repair broken tags. It will give you a preview URL quickly, optional custom domains with certificates after DNS verifies, zip or GitHub upload, and rollback via deploy history. It will not provide email, cPanel, a forever-free plan (trial ~1 day), or a PHP engine for WordPress.
Lesson 1: One page
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Alex Rivera</title>
</head>
<body>
<h1>Alex Rivera</h1>
<p>I build small websites.</p>
</body>
</html>Save as index.html. The name matters: hosts look for index.html when someone visits /.
Lesson 2: Attach CSS without breaking paths
Create styles.css beside index.html:
body { font-family: system-ui, sans-serif; margin: 2rem; }Link it:
<link rel="stylesheet" href="styles.css" />When both files sit in the same published folder, the relative link works on StaticHost the same way it works on your computer—if you zip them as siblings. If you accidentally zip a parent folder so the site lives at /alex/index.html, then /styles.css will 404. This is the number-one beginner outage. Deep dive: zip a static site without 404.
Lesson 3: A second page
Create projects.html with a link back to index.html. Use simple names and links:
<a href="index.html">Home</a>
<a href="projects.html">Projects</a>Multi-page HTML sites map perfectly to strict static hosting. Every link is a real file. You do not need a JavaScript router. (When you eventually try React history mode, read SPA hosting—unknown paths 404 here.)
Lesson 4: Publish
- Put
index.html,projects.html, andstyles.cssin one folder. - Zip the files inside that folder.
- Create a StaticHost site on Starter ($9/mo, 1 site, 2 GB) or during the short trial.
- Upload the zip.
- Open the HTTPS preview. Click Home and Projects.
You just did HTML hosting. Deploy again whenever files change. Roll back if a publish goes wrong.
GitHub is optional. If you use it, push the HTML files themselves (or build output)—StaticHost does not compile anything. Git deploy notes.
Lesson 5: Images
Save me.jpg in an images folder. Reference with src="images/me.jpg". Huge PNGs will work but feel slow; resize before upload. Storage limits are plan-based (2 GB on Starter; higher on Pro/Scale/Business). There is no built-in CDN product; keep files lean—fast static hosting.
Lesson 6: Your name as a domain
When you are proud of the preview, add alexexample.com in the dashboard, create the DNS records at your registrar, wait for verification, then wait for the certificate. Do not promise classmates the custom URL until HTTPS works on it. Companion: HTML website with custom domain.
Lesson 7: What not to buy into yet
- You do not need Kubernetes.
- You do not need a database for a resume.
- You do not need WordPress to publish two HTML pages.
- You do not need SPA fallback myths; your multi-page links already work.
When requirements grow into a JavaScript app, graduate to how to host a frontend website. When you need server-side PHP, leave for a PHP host—one sentence, no tutorial: static hosting is the wrong category.
Practice project ideas
- Personal page with bio and links (personal HTML).
- One-page resume (resume static site).
- Class project write-up with screenshots.
- Tiny documentation set:
index.htmlplusinstall.html.
Each remains a folder. Hosting remains an upload. Confidence compounds when the mental model stays that simple.
Worked example: weekend personal site
Saturday morning: create a folder mysite with index.html, about.html, and styles.css. Write two honest paragraphs and a list of links. Put a resized photo at images/me.jpg.
Saturday afternoon: zip the contents of mysite (highlight the files, compress—do not compress the parent directory that only contains mysite). Upload to StaticHost. Open the HTTPS preview on your phone. Fix a typo; upload again; notice deploy history can save you.
Sunday: buy or reuse a domain; add it in the dashboard; create DNS; wait for verification; wait for the certificate. Share the custom URL only after the padlock works. Skip email-on-this-host fantasies—StaticHost has no mailboxes. Starter at $9 after the ~1 day trial is enough. Pro ($30), Scale ($65), and Business ($130) can wait until you have more sites or need staging/teams.
Failure table: first-site mistakes
| Symptom | Likely cause | Fix |
|---|---|---|
| Page has no style | Nested zip or wrong href | Flatten zip; match filenames |
| Clicking Projects 404s | File not uploaded / wrong name | Include projects.html; check case |
| Image missing | Path or file omitted | images/me.jpg relative path |
| Friend sees old version | Sharing custom domain before DNS/cert | Share HTTPS preview until ready |
| “Install WordPress?” confusion | Different hosting type | Stay static or move to PHP host |
| Contact form does nothing | No form endpoint | Use a form provider |
| Expect free forever | Misread trial | Trial ~1 day; then paid or free hosts elsewhere |
Extra procedure: beginner launch checklist
- [ ]
index.htmlopens locally in a browser. - [ ] CSS and images load locally via relative links.
- [ ] Zip contains those files at the archive root.
- [ ] Upload; HTTPS preview works on phone and laptop.
- [ ] Second page links work with real files (no JavaScript router yet).
- [ ] Optional: custom domain after preview is good—DNS, then verification, then certificate.
- [ ] Know how to roll back one deploy.
- [ ] Remember: StaticHost does not run npm, does not offer cPanel/email/CDN product, and uses
try_files $uri $uri/ =404.
You do not need to master everything at once. Folder → zip → HTTPS preview → maybe domain. That loop is HTML hosting.
Learning path after your first upload
Once index.html is live on HTTPS preview, grow skills in small steps—not all frameworks at once. Add a third HTML page. Then a contact link to a form provider. Then a custom domain after DNS and certificate. Only then consider a generator (Eleventy/Hugo) or a small amount of JavaScript. Each step keeps the folder mental model intact.
If a tutorial pushes you into React in week two, read the SPA guide before you deploy so refresh 404s do not feel like personal failure. StaticHost’s strict try_files $uri $uri/ =404 is easier to understand when your own links are real files. Paid plans after the short trial start at $9; you do not need Scale or Business to learn. Curiosity scales better than premature architecture.
FAQ
Why do people mention nginx?
nginx is software that can serve files. StaticHost uses a strict file-serving setup for you. You do not configure it.
Can I use Bootstrap or other CSS libraries?
Yes. Download the CSS/JS into your folder or link a public CDN URL. Prefer HTTPS links.
What is the difference between this and Google Drive link sharing?
Drive is not a website host with your domain and proper index.html semantics. Use a real static host for websites.
Do I need JavaScript?
No. HTML and CSS alone are valid.
How do I delete a mistake deploy?
Use deploy history rollback, then fix files locally and publish again.