Static hosting for students

Class projects need URLs, not infrastructure résumés

When a syllabus says “host your website,” graders usually mean a public HTTPS link that shows your HTML. They rarely mean you should learn Terraform. Static hosting matches the assignment: upload files, send the URL, move on to the next lab.

StaticHost offers a short trial (~1 day) and then paid plans—there is no forever-free tier. For many assignments, GitHub Pages remains the $0 default; read free vs paid. Choose StaticHost when you want staging-like workflows, a cleaner commercial tool chain for internships, or a portfolio you will keep past graduation on Starter ($9/mo, 1 site, 2 GB).

Assignment-shaped workflow

Build what the rubric asks (hand HTML, Vite app, etc.).
If it is a JS framework, run npm run build locally—StaticHost will not.
Zip the output contents, not node_modules—zip guide.
Deploy; copy the HTTPS preview link into the submission form.
Optional: attach a custom domain if the course cares (most do not).

If the course requires PHP or MySQL on the same host, this product is the wrong category—use whatever campus host or PHP provider the instructor names. One honest sentence beats a weekend of fighting static nginx.

SPA courses and the 404 surprise

Many web-dev courses teach React Router in history mode and deploy to platforms with automatic fallback. On StaticHost, unknown paths 404 (try_files $uri $uri/ =404). Before submission night:

Switch to hash router, or
Pre-render routes, or
Use a host that documents SPA fallback.

Do not invent a rewrite. Guide: host a single-page application.

Collaboration without sharing passwords casually

Group projects can use GitHub and a deploy branch of built files—git deploy. Business plan teams features are overkill for most labs; a shared repo plus one classmate owning the StaticHost account is enough if you go paid.

Portfolio after the semester

Keep the best project on Starter, point yourname.com when you can afford the domain, and roll back experiments safely. See portfolio hosting and personal HTML. Pro ($30, 3 sites, staging) helps if you maintain class site + portfolio + internship project.

What not to do

Upload the entire coursework monorepo including graders’ private fixtures.
Commit .env with campus API secrets into a public artifact.
Expect email hosting for the student club on this product.
Expect cPanel file managers as the primary edit path.

Learning resources nearby

Beginners: static site hosting for beginners, HTML hosting for beginners. Conceptual: what static hosting is.

A realistic week shipping static hosting for students

Monday starts with a broken relative CSS path that only appears once the files leave a designer’s laptop. You flatten the zip so index.html sits at the archive root, redeploy to StaticHost, and HTTPS preview finally matches local intent. StaticHost serves prebuilt files via zip or GitHub and does not run npm, Hugo, or Jekyll remotely.

Wednesday adds a custom domain. DNS is created exactly as the dashboard specifies; verification lags an hour; the certificate appears afterward. Someone asks whether email is included—you point them at a mail vendor and keep MX untouched. Deploy history supports rollback when a publish goes wrong.

Thursday an engineer enables history-mode routing for a “cleaner URL.” Refresh on a nested path 404s. You revert to hash routing for the week’s deadline and schedule prerender work properly instead of inventing an nginx rewrite StaticHost will not apply. Preview HTTPS is available immediately; custom-domain certificates issue only after DNS verifies.

Friday staging on Pro receives a build with staging API URLs baked via public env prefixes. Production stays on last week’s known-good deploy until Monday’s review. Rollback remains one click if marketing’s late copy drop breaks mobile layout. nginx behaves like try_files $uri $uri/ =404 with no SPA index fallback.

There is a short trial (~1 day), not a forever-free tier; no cPanel, no email, no built-in CDN product.

That week is what static hosting for students looks like when the host stays boring and the team respects file truth.

Worked example: Vite lab due Friday

Syllabus: “Deploy a small interactive page; submit an HTTPS URL.”

npm create vite@latest lab04 -- --template vanilla
cd lab04
npm ci
# edit index.html / main.js per rubric
npm run build
cd dist && zip -r ../../lab04.zip .

Deploy lab04.zip on StaticHost (trial if it still covers the deadline; otherwise Starter at $9/mo). Copy the HTTPS preview URL into the LMS. Optional screenshots of the Network tab showing main.js at 200 help skeptical graders.

If the lab used a client router in history mode, switch to hash routes before Wednesday night—not Thursday at 11:40 p.m. Hard-refresh proof:

/#/step-2 works on StaticHost.
/step-2 without a file returns 404 (try_files $uri $uri/ =404).

That contrast is not a grading bug; it is the server telling the truth.

Failure table (student deploys)

Symptom	Likely cause	Fix
Submission link 404s at `/`	Nested zip (`dist/index.html` inside archive)	Re-zip from inside `dist/`
Blank white page	Wrong `base` or forgot `npm run build`	Rebuild; confirm asset URLs on preview
“Works on my machine” only	Opened `file://` or dev server	Graders need the HTTPS preview URL
Group member overwrote site	Shared account without coordination	Agree on who deploys; use Git history
PHP required by rubric	Wrong host category	Use campus PHP hosting; do not fight nginx
Trial ended mid-review	No forever-free tier	Budget Starter or host elsewhere for $0

Office-hours script (honest sentences)

When a classmate asks why “Netlify tutorials” differ, say: StaticHost does not run npm remotely and does not fall back unknown paths to index.html. When they ask about email for the club domain, say: not on this product—keep MX at Google Workspace or whatever the club already uses. When they ask about forever-free, point at free vs paid static hosting and GitHub Pages for $0 coursework, then explain Starter ($9), Pro ($30 with staging), Scale ($65), Business ($130) if they want a portfolio that outlives the semester.

Custom domains are optional for most courses. If you add one, order is fixed: HTTPS preview → DNS verify → certificate. Never tell a grader the domain is “almost ready” while verification is still pending.

FAQ

Can I finish entirely on the trial?

If the trial window covers your submission deadline, maybe. Do not gamble on a graded deadline without a plan for paid or an alternate free host.

Is StaticHost required by schools?

Unlikely. It is a tool option. Follow the syllabus if a vendor is mandated.

Will my teacher accept a preview URL?

Usually yes if it is HTTPS and public. Ask when rubrics say “custom domain.”

Can I host a Flask app here?

No. Static files only. Flask needs an application host.

How do I cite the host in a report?

State that the site is static files on StaticHost, built with X, deployed via zip/GitHub—no server-side app runtime.