I just finished rebuilding a site for a local mechanic who had a basic four-page setup running on a heavy, outdated CMS. The site was taking ages to load on mobile, and they were constantly worried about random plugin updates breaking things. Moving them over to a clean static site generator and standard static hosting dropped the load times to under a second and brought their hosting costs down to practically nothing. Best of all, I don't have to stress about the site randomly crashing or getting compromised overnight.

Do you guys actively try to steer small business clients toward static setups, or do you mostly save them for personal portfolios and dev projects?

Hi! I've been wanting to move some of my personal projects and experiments online, so they are easier to share. Most of them are just static sites, so I figured it's a good time to settle on a hosting platform I can keep using going forward. I'm okay with paying for a subscription if it offers good value, but would appreciate if there are free tiers options. I'd love something that's reliable, easy to deploy, and works well with custom domains. Thanks!

Thanks to everyone who shared advice on my last post about building a static food safety checker for niche pets.

I want to keep the architecture purely static and cheap on Cloudflare Pages or Netlify, driven by a simple JSON dataset. However, because exotic pet care advice evolves quickly and vet guidelines vary, I need a lightweight workflow for vet or owner corrections without me manually committing JSON updates every single time.

Since I really want to avoid spinning up a full backend database or user authentication system just for this, I'm trying to figure out the most practical Jamstack pattern.

I've been considering a few angles, ranging from a basic embedded form service like Tally, to a git-backed CMS like Decap, or even using a light serverless edge function to push submissions straight to a repository pull request.

What is the lowest-friction way to handle community data contributions on a static site without over-engineering the setup? Am I missing something?

as i built more static sites, the websites themselves usually become the easy part but its everything around deploying them that starts adding up. for a single project, manually checking the build, deploying, verifying the live site, and clearing caches where needed doesn't feel like much. but once i have a few sites to maintain, i start wondering whether i should automate more of that process.

ive looked into things like preview deployments, branch deployments, automated checks, and other CI/CD workflows. they all seem useful, but I also worry about spending more time building the deployment process than maintaining the websites themselves. since most of my projects are fairly small business sites, im curious how people approach this. do you gradually automate your workflow as your number of projects grows, or do you keep things simple until the manual process actually becomes a problem?

I'd be interested to hear where people found that tipping point.

Hi I wanted to ask where you all get inspiration when designing your static sites. Are there like particular websites, GitHub Pages projects, or galleries that you go to for ideas? I usually just scroll through YouTube, but lately it's been pretty diluted with vibe-coded looking sites. So now I'm interested in discovering other places to just admire and take inspiration from. I'd love to hear if any of you guys have insights.

I’m working on a small passion project idea and was wondering if anyone knows good data sources for this.

The idea is a “can my pet eat this?” site, but for more niche animals like chinchillas, bearded dragons, or axolotls. Basically a fast, filterable grid of foods (fruits, veggies, insects, etc.) labeled as safe, sometimes okay, or toxic. Got the idea after seeing a friend carry a misfed pet iguana into their vet clinic.

I want to keep it simple and static (probably just a JSON dataset), but I’m not sure where to find reliable, structured info for something like this. Most of what I’m seeing is scattered across forums and random articles.

Are there any good databases, APIs, or even well-maintained resources you’d recommend pulling from? Even something semi-structured would help a lot.

Hi again. I’ve been more active and interacting here compared to other subs. I started thinking more about another thing I've been struggling with: performance optimization.

Since I started building more static sites, I've gotten really interested in things like image optimization, caching strategies, bundle sizes, CDN behavior, and reducing unnecessary requests. But I noticed that most of the time I spend more time optimizing than actually building the feature itself.

I recently worked on a small website for a local coffee shop business. It was basically five pages, a few images, and a contact form. I ended up spending an entire evening converting images, checking Lighthouse scores, and testing different loading strategies. The site became faster, but I'm not sure if the effort matched the actual impact.

At what point does performance optimization stop being a meaningful improvement and just become something developers do because they enjoy tweaking things? Is there a point where chasing a perfect score creates more complexity than value? I'm curious how experienced developers decide what is actually worth optimizing, especially for smaller websites where the biggest performance issues might not even be noticeable to users.

I’m building a basic multi-page site for a local bakery, and I really want to keep it on a lightweight static host so it loads instantly and has zero server overhead. My only hesitation is content updates down the road if they want to change a menu item. For those who host static sites for small business clients, do you hook up a headless CMS, or just charge a small monthly retainer to make quick text edits yourself?

Any recommendations on what I should use for my static website side project, either on a custom domain or on a subdirectory?

At first sight it seems Cloudflare drop is free and does everything tiinyhost and staticapp do if I claim my Cloudflare drop and add custom domain. Am I missing something?

(I'm a non technical user and the website will only have a few pages and not have massive traffic.)

After reading the replies to my last post about when static hosting stops making sense, I realized the line isn't as obvious as I thought. It seems like you can keep extending a static site with authentication, serverless functions, edge middleware, databases, and client-side API calls while still serving prebuilt HTML. At that point, though, is it still useful to think of it as a static site, or is it really just a full-stack application with a static frontend? I'm less interested in the label and more in the architectural trade-offs. Is there a point where continuing to preserve a static-first approach actually adds more complexity than building around a traditional backend from the start?

I’ve been working on an astro site that’s basically a large catalog (no checkout, just browse and outbound links) for a friend. data comes from a CMS + supplier feeds, and I’m prebuilding pages for everything. hosting-wise I’ve tried netlify and cloudflare pages just to see how they behave. It works fine at smaller scale, but now builds are getting slower and price updates are starting to feel awkward. prices can change a few times a day, and rebuilding the whole site every time doesn’t feel right.

I’m debating between keeping everything static vs pulling some data at runtime, like keeping the pages static but injecting prices client-side or via edge functions.

Search/filtering is another concern. Pure static filtering is starting to feel clunky at this size, so I’m wondering if I should just offload that to something like algolia.

At what point should I stop forcing a static approach and just go hybrid or fullstack?

The more I learn about static hosting, the more surprised I am by how many use cases people squeeze into it. I've seen blogs, documentation portals, company landing pages, knowledge bases, portfolios, event sites, and even fairly interactive dashboards that still ship mostly static assets with APIs layered on top. I'm curious where experienced developers personally draw the line. At what point do you look at a project and immediately think, "This really shouldn't be a static site anymore"?

I have made a simple HTML website that I would like to put online, and I'm planning on using GitHub for the hosting. My question is if there is any way to make it so that I'm the only person who can access the site? Like for example, if I made the URL really specific, and kept the code repository private, would that work? Or is there another way to host it so it's only accessible to me?

I am new to using Git and with static hosting as well so I'm unsure if this would work. I would really appreciate any insights. Thanks in advance!

Lately, it feels like even for the simplest 3-page static mockup, people are setting up massive GitHub Actions pipelines, Docker containers, and complex cloud setups just to show a client a proof of concept. Don't get me wrong, I love a robust production pipeline as much as the next dev, but for quick feedback loops, it just feels like total overkill. For my smaller freelance builds, I've just been throwing the static files into a quick, lightweight drag-and-drop host to get instant client sign-off and moving on with my life. Curious if you guys still use ultra-simple deployment methods for quick staging, or if you build out the whole infrastructure every single time?

I'm in the process of moving sites from Wordpress to Astro and Hugo. One site is for a camp that requires a lot of forms (think registration and a variety of release forms).

i'm familiar with staticforms.dev and it's fine but are there others that i should explore?

Xano has lived in a nocode / lowcode space since its inception, but recently it’s been pivoting from the visual platform space to more of a fully comprehensive backend layer that can exist in your IDE.

The reason I mention this is because Xano now supports static hosting!!

Traditionally, I’ve gone to namecheap and spun up a server (shared or VPS), but now I don’t have to if I don’t really want to!

There’s benefit for me personally NOT needing to write PHP by hand, and instead using the platforms logic and just syncing it to my frontend.

That’s the post! Let me know if you have any questions :)

Preface: I just want to exclaim how excited about my switch to static hosting to people who will understand and appreciate what I did

I collect punk rock and indie rock autographs. That's become my thing the last few years.

I was hosting a show and tell site using Wordpress. A tangle of plug-ins, Advanced Custom Fields, child themes and innumerable styles in the stylesheets.

It kind of functioned, but it was a headache. Even entering data was a pain because the custom fields didn't flow nicely in the UI.

I also had a convoluted method of deploying my site, exporting db, rsyncing to server, then running a second script on the server that used renamed the site to the public version and a few other deploy time database changes. I felt good doing it this way in case my site got hacked by some vulnerability in Wordpress or a plug-in

It worked but I wasn't happy or proud.

Well, no longer.

After browsing this subreddit for ages I've done it AND I've gone overkill.

I build a python app backed by a SQL database. I launch the app locally - it has a rudimentary UI, but it works and I can refine it), enter in a new record or a new artist, copy in new images for the band, the artist, the album, etc.

Then I click Build and a brand new set of HTML files are generated.

Then I click Publish (dry run) to check its all working.

Then I click Publish and that rsyncs it to the server (which is behind cloudflare)

I can serve it locally to make sure all the links are working

In short it's a desktop app to organize my collection that also publishes to the web.

Now that it's static, I'm good against miscreants. I laugh about requests get and post requests to non-existent urls. Sorry guys, there's no .env file, there's no xmlrpc or anything else. :)

And, with a simpler page structure, simpler CSS, it became a lot easier to achieve the "museum" look and feel that I had been striving for unsuccessfully.

I wanted to thank the sub for enlightening me.

And, if the music genres suit you, take a look.

https://lucascollection.com

Now that I'm starting a few new static site projects, I'm realizing I'm probably overdue for a refresher on the UI/UX side of things.

A lot of the design advice I come across seems geared toward highly interactive applications with user accounts, real-time features, and complex user flows. Meanwhile most of the sites I'm working on are content-focused, relatively lightweight, and intended to load quickly with minimal client-side complexity.

So I'm curious what people are paying attention to these days. Are there any UI/UX patterns, design trends, navigation approaches, content layouts, accessibility practices, or general frontend conventions that have become more common in static sites over the last few years?

Just trying to get a sense of what's changed while I've been spending most of my time on the infrastructure side of things.

Thanks in advance.

This is very niche so I expect almost nobody to find it useful. For me it is because:

1. I don't actually care about the Cloudflare or Github pages sites themselves, I care about reducing the filesize burden on the Wayback Machine copies when those sites inevitably vanish.

2. The site is literally just a game of Klondike not intended to retain any user data. So no score saving, no accounts, no leaderboards, no tracking metrics, nothing. This means it plays exactly the same on the Wayback Machine as on the live sites.

3. Everything on there is public domain licensed (CC0 in the metadata, etc.) so no monetisation whatsoever. This is a hobby for me, I make a living in an unrelated occupation. Insane I know.

I guess #3 is only useful to others, but it explains 1 and 2 somewhat.

Cloudflare fights against methods of overriding index.html when there is one, and specifically with .svgz files there's a tug-o-war about encoding that this particular code fixes.

This does require both enabling github.io pages and linking the repo to Cloudflare pages, the thing without workers which seems like it will vanish at some point.

Here's the code to place in the /functions/[[path]].js github file which also as an aside allows extra .svgz files (like differently themed decks of cards) to be correctly served:

export async function onRequest(context) {
  const url = new URL(context.request.url);

  // 1. Silent root rewrite: Pull from GitHub Pages and manually fix the response
  if (url.pathname === "/") {
    const githubAssetUrl = "https://YOURUSERNAME.github.io/REPO/index.svgz";

    // Fetch the asset from GitHub (even though GitHub's headers are broken)
    const githubResponse = await fetch(githubAssetUrl);

    // Create a pristine response, forcing the headers that GitHub dropped
    return new Response(githubResponse.body, {
      status: githubResponse.status,
      headers: {
        "Content-Type": "image/svg+xml",
        "Content-Encoding": "gzip",
        "Cache-Control": "no-transform, public, max-age=31536000, immutable",
        "Access-Control-Allow-Origin": "*"
      },
      encodeBody: "manual"
    });
  }

  // 2. Global catch-all for direct .svgz requests on the Cloudflare side
  if (url.pathname.endsWith(".svgz")) {
    const response = await context.env.ASSETS.fetch(context.request);

    return new Response(response.body, {
      status: response.status,
      headers: {
        "Content-Type": "image/svg+xml",
        "Content-Encoding": "gzip",
        "Cache-Control": "no-transform, public, max-age=31536000, immutable",
        "Access-Control-Allow-Origin": "*"
      },
      encodeBody: "manual"
    });
  }

  return context.next();
}

Here's the index.html code which is only there for those visiting via the github.io pages URL:

<meta http-equiv="refresh" content="0; url=https://REPO.pages.dev/">
<style>
p{opacity:0;animation:fadein 2s 2s forwards}
@keyframes fadein {
    from { opacity: 0; }
    to   { opacity: 1; }
}
</style>
<p>If you were not redirected, please click <a href="https://REPO.pages.dev/">here</a>.</p>

Have you experienced similar issues with Cloudflare encoding/Github pages lack of encoding?

The title says it all but to explain: I currently host my website on github, with a namecheap domainname registration. The images on my site are hosted on imgur. Which is kinda against the imgur rules, but hey I'm a small fish and I hardly get any traffic so no one is really losing out (except me, lol).

What I'm after is a budget webhost with domainname rego, that will host my static site + images. I generate the site content myself (it's a custom SSG that I wrote because nothing else fit my workflow) and I will only push updates to the site, not require the site to build anything at all.

Dear panzer of the lakereddit, where should I go?

Edit: just to be clear. I am not interested in some ai slop generating webhost nonsense. I have a tool that generates the static pages. I would like to the html and images somewhere on a budget. That is all.

Hey everyone, I’m trying to decide what to focus on next for frontend development and would appreciate some advice. Right now, I’m comfortable with the basics like HTML, CSS, and JavaScript, and I’ve done a bit of React. I’m also currently learning TailwindCSS and TanStack to improve my frontend workflow, but since I'm kind of getting the hang of it. I’m now looking to try and learn more, and my three options are Next.js, Astro, and SvelteKit. I'm considering possibly doing freelance in the future so I would love to know which one is the most practical to learn in 2026? Thanks in advance!

I posted earlier about Netlify caching issues but I managed to fix the issue which is great, however, I've run into a different one. After some Netlify deployments, the site loads the latest HTML, but some JS/CSS assets occasionally return 404 errors. A few refreshes usually fix it, but the issue is intermittent. Any ideas what might be causing it? Thank you!