Static website hosting for beginners

Beginners do not need a server textbook to put a résumé online. You need finished files, a host that accepts a zip, an HTTPS preview you can trust, and a domain when you are ready. This guide explains who static hosting is for, the publish path, and when to pick a different product.

Who beginners actually are

Treat dated zips as your memory. Labels beat heroic recalls after a bad publish. Rollback is there, but only if you know which artifact was good.

Storage is a budget. Compress photos. Leave raw camera files on a backup drive, not in the web zip.

Staging on Pro helps when you maintain more than one experiment. Starter remains enough for many single properties.

Publish path without Linux

Confirm you have publishable files with index.html at the intended root.
Fix relative paths; remove file:// and accidental http:// asset links where you can.
Zip carefully; extract once to verify structure.
Create a SiteHost site; use the short trial to prove the publish.
Upload the zip or connect GitHub; open HTTPS preview on desktop and mobile.
Fix, republish, or roll back until preview earns trust.
Point DNS at your registrar; wait for verification and the custom-domain certificate.
Share the domain publicly — not the preview — after that certificate looks right.

That order prevents most self-inflicted outages.

When to pick a different product

Pick a different product when you need a full CMS with editorial roles, server-side code you maintain, or bundled email. SiteHost is for static files with preview HTTPS and domain certificates after DNS — not for every website genre on earth. Related reading: static hosting for documentation, html hosting for personal websites, and website hosting for a personal brand.

Résumé at yourname.com

A beginner publishes a résumé on Starter, learns relative CSS the hard way on preview, then points yourname.com after a friend QA pass.

Plan numbers without panic

Starter is $9/mo for 1 site and 2 GB. Pro is $30/mo for 3 sites, 10 GB, and staging. Scale is $65/mo. Business is $130/mo when teams and larger site counts matter. The trial lasts about a day; then you pay. There is no forever-free plan, no website builder, no cPanel, no email hosting, and no built-in CDN. Match storage to compressed media. Climb tiers when site count or teamwork demands it — not for vibes.

Habits that prevent redo weekends

A beginner publishes a résumé on Starter, learns relative CSS the hard way on preview, then points yourname.com after a friend QA pass.

Boundaries worth repeating

file:// CSS that vanishes

When a stylesheet (or image, or script) is referenced with a file:// path, you are asking visitors’ browsers to read a disk location on your computer. They cannot. The CSS file may sit correctly inside the uploaded zip and still never load, because the HTML never requests the hosted copy. Beginners trust local preview and skip the extract test. Editors and “open in browser” shortcuts rewrite paths quietly. Your defense is mechanical: extract the zip into an empty folder and open index.html from that extract before every upload. Relative paths such as css/site.css survive laptop, HTTPS preview, and custom domain. Certificates do not rewrite hrefs. DNS does not invent stylesheets. Fix the files, republish, then celebrate.

One more practical note on static website hosting for beginners

Keep the scope of static website hosting for beginners aligned with what SiteHost actually sells: static file hosting with immediate HTTPS preview and custom-domain certificates after DNS verifies. The worked reality for this article is a beginner publishes a résumé on starter, learns relative css the hard way on preview, then points `yourname. When someone tries to expand the project into server management, a website builder you do not have, or email inboxes on the same SKU, pause and separate products. Write down the public URL only after it is a domain you control. Keep a prior zip. Click the phone number or primary button yourself on preview. Related reading: static hosting for documentation, html hosting for personal websites, and website hosting for a personal brand. If storage pressure appears, compress media before you climb from Starter to Pro; if site count grows, Pro’s three sites and staging are the usual next step; Scale and Business wait for larger portfolios and teams. That is the whole economics story without unlimited fairy tales.

Field notes you can reuse next month

Create a simple folder on your computer named for the site and the month. Drop every zip you publish into it. When a stakeholder asks what changed, open the folder instead of reconstructing history from memory. If you work with a designer, agree that they deliver archives that extract to index.html at the root. If you work with a developer who loves client-side routers, agree on real files for public URLs before anyone prints QR codes. If you are cost-sensitive, revisit whether you still need Pro’s staging or whether Starter covers the live property alone. If you are security-sensitive, re-scan your HTML for http:// after each vendor gives you a new embed snippet. If you are speed-sensitive, weigh images on a scale that is not a marketing graph — look at file sizes on disk. These notes are not glamorous. They are how static sites stay calm on SiteHost without cPanel, without a website builder, and without pretending email was included.

Questions people actually ask

Is SiteHost a fit for static website hosting for beginners?

If you have finished HTML/CSS/JS files (or a static export) and want zip or Git publish with HTTPS preview and a custom domain after DNS, yes. If you need a CMS runtime or inboxes, pick those products separately.

Is there a forever-free plan?

No. The trial is about a day; then you choose a paid plan such as Starter at $9/mo.

Does hosting include email?

No. Keep mailboxes with a mail provider and be careful with MX records when you only meant to point the website.

When do I point DNS?

After the HTTPS preview looks right. Custom-domain certificates follow successful verification.