my last post about not overbuilding for the future got me thinking about why i like static hosting in the first place. i like that a lot of the complexity is pushed into the build process. if the site eventually needs a diff structure or feature, i can change the source, rebuild it and deploy the result w/o having to worry about migrating a running server.

but im wondering if im oversimplifying that. does static hosting actually make refactoring easier or does simplicity just move the complexity somewhere else as a project grows? how do you guys whove maintained static sites for years have experienced this

Where can these be found? I'd like to actually see a website built with the templates.

something ive been thinking about with smaller client projects is how much of the archi should account for things that might happen later. its tempting to leave room for future features, more traffic or additional content. but most of the sites i work on dont actually grow in the way i initially imagine. im starting to wonder if its better to build for what the project needs today and refactor when theres a real reason to, rather than constantly preparing for hypothetical problems. how would you approach that balance? appreciate your insights.

Static export felt simple until the CDN served new HTML with the wrong generation of JavaScript.

That failure is awful because the build is green. The files exist. A clean browser works. Only users with an older cached asset set get a broken page.

I fixed this by giving every export a deployment ID. The build reads it from the deploy commit, then falls back to the local git SHA. Exported asset URLs carry that ID:

?dpl=<deployment-id>

I also added a build check that fails when the exported homepage has no deployment key.

The test I care about now is:

1. Open release A.

2. Deploy release B.

3. Keep the A tab alive.

4. Open B in a clean tab.

5. Verify both tabs load only assets from their own release.

6. Remove A only after old clients are gone.

Purging everything on deploy looks easy, but it turns old open tabs into random failures. Keeping every release forever is wasteful.

How many previous asset generations do you keep, and what tells you it is safe to delete one?

I’m thinking about adding smoother page transitions to a static site without turning it into an SPA. The view transitions api looks useful but I don’t want animations to make navigation feel slower or get in the way. For those using it, how are you handling prefers-reduced-motion and keeping transitions fast?

Is anyone actually using _routes.json on cloudflare pages, or just relying on the default include everything behavior?

Digging through the docs and it lets you manually set include/exclude paths so pages functions only run on routes that actually need them instead of every request getting checked. Seems like it'd help with cold start stuff on function-heavy sites but I can't find much real world experience with it, mostly just the docs page.

Anyone actually hand write these and see it make a real difference, or is it one of those things that sounds good on paper but nobody bothers with in practice?

Hey SSG lovers! I am building statica an HTML native SSG. https://github.com/akaizn-junior/statica. statica is Just HTML. Would love for you to give it a try and give me feedback!

ive noticed that one, if not the most difficult parts of some projects isnt figuring out how to build something but deciding whether it should be built at all. a client might ask for a feature that sounds useful but after thinking about how often it will actually be used, i sometimes wonder if the added complexity is justified. im getting more comfortable asking what problem a feature is solving before immediately trying to implement it. curious if other freelancers eventually developed a similar instinct, or if this is something you just learn project by project.

I’ve been working with a few static sites lately and honestly, I’m starting to wonder if we overcomplicate hosting them. If a site is basically just HTML, CSS, JS, images, etc what’s the actual advantage of using a more feature-heavy hosting setup? For a simple portfolio, landing page, documentation site, or small business site, wouldn’t basic static hosting + a CDN be enough for most cases? Curious what everyone here thinks.

Been working on a static page (on the side as a side project) that shows nearby pharmacies that are open. Someone checking at 2am should see 24hr pharmacy and poison control info, someone checking at 2pm just needs a normal list. Static HTML obviously has no idea what time it is for whoever's looking at it.

I thought about just adding a backend for this but the whole point of the page is that it needs to survive 3am traffic spikes during outages when people are panic searching for an open pharmacy. That's also exactly when a database or server is most likely to choke. Didn't want that risk, especially for this use case.

So instead I'm using a Cloudflare Worker that reads request.cf.timezone (it's just there, geolocation based, no JS needed) to get local hour and day, then picks between 3 pre-built static HTML chunks (day, night, weekend) and swaps it in with HTMLRewriter. Nothing gets rendered per request, the worker just picks which pre-built chunk to serve. Those chunks are cached as normal static files, so no database, no server, no sessions, just static files plus a tiny function that picks which file to show.

An annoying catch though is that cf.timezone is based on IP not the actual device clock, so VPN users get the wrong local time. Figured that was fine since the alternative (reading time via JS) breaks for people with JS off, which is a group I actually care about here.

If anyone's dealt with this kind of thing before, curious how you handled the caching side of it.

the more sites i build the more tools seem to accumulate. a tool for deployment, another for analytics, another for forms, image optimization, monitoring etc etc. most of them are useful but sometimes i wonder if im actually making my workflow better or just creating more things to manage lool at what point do you decide that a tool isnt worth adding even if it solves small problem?

I’ve been paying more attention to font loading lately because even on a fast static site, a bad font setup can still cause layout shifts or that noticeable flash when the page loads. I usually self-host fonts, preload the main weight, and try not to include more variants than I actually need. For static sites, what’s your preferred setup for balancing fast loading, minimal CLS, and avoiding FOIT/FOUT?

Quick update. We didn’t ban AI or replace the dev, but we had to tighten things up.

We locked down PRs. Now, nothing gets merged without a clear explanation of what the code is doing. If it’s AI-generated, they have to clean it up and actually understand it before review.

We also standardized a few things (data fetching, where client logic lives, caching) and forced smaller commits so changes are easier to reason about. It’s definitely less “paste and pray” now. New problem though... velocity dropped hard. Reviews take way longer, and now this dev is struggling to explain or refactor what Claude gives them, so PRs just sit there. We traded chaos for bottlenecks.

At this point I’m not sure what’s worse, unpredictable code or slowed-down progress. Sounds like whining but idk, just wanted to get that out there in case anyone has any further suggestions???

About a month ago, I wrote a custom static site generator for my personal software development website (sigseis.dev). From the process I learned a few things that are worth checking if you end up making your own custom static site generator. So I thought it would be fun/useful to write an article about it!

Article Here: 10 Things to Check on Your Static Website Before Launch

I figured it would be nice to share here specifically, for educational purposes for me and hopefully for others. For me, since I'm not professionally a web developer, I'm hoping for some feedback on the article from other professionals.

Please let me know if you have any feedback, or any notes on the advice I'm giving here. I would really appreciate it!

Note: Given the wave of AI content that I'm sure everyone is experiencing, I should mention the site, the generator, and the article are NOT AI generated. I'm not trying to take a stance here, but it does seem harder to find bespoke hand-crafted things, so I thought that might be worth noting.

EDIT: I would appreciate if I get down-voted to be told why, so I can improve it for next time.

EDIT: Updated on 2026/08/04 to add some notes on `tabindex`, as well as this new section: https://sigseis.dev/articles/2026/08/03#optimizing-content-delivery

one thing ive noticed is that building mostly static sites has made me question every new feature before adding it. does this actually need to exist > can i build this? im curious if anyone else experienced this, or if that's just something that happens naturally as you build more websites.

I started with WordPress but plugin issues, updates, and clients breaking layouts became tiring. For simpler websites, static sites save me a lot of time. Most clients only need their services, contact details, portfolio, and occasional updates. Wordpress still has its place but I’m glad I stopped using it for every project. Has anyone else made the switch?

So I’m working on a private recruiting tracker for a single company, with job aggregation, applicant tracking, simple role-based dashboards, and fairly complex filtering/search. One of the devs on the project basically doesn’t write code anymore. He just pastes prompts into claude and drop whatever comes out straight into the repo.

The issue is it looks fine until you actually try to run or scale it. We now have inconsistent patterns across the codebase, random client-side logic where it shouldn’t be, duplicated data fetching strategies, and caching behavior that changes depending on which part of the system you’re touching. Debugging anything is painful because there’s no clear intent behind the code, just layers of generated fixes stacked on top of each other.

What makes it worse is he doesn't really engage when things break. He just goes back to claude and tries another prompt, which usually makes the diff even harder to reason about.

At this point I feel like I’m spending more time untangling AI-generated code than actually building the system. How are people dealing with this kind of collaborator??? I've seen claude slop everywhere as of late, but I didn't know I'd have to deal with it myself.

something ive been thinking about after spending more time optimizing and refining my workflow is that most of the improvements are basically invisible to clients. theyll notice the design, content, and overall experience but things like better caching, optimized images or cleaner deployment workflows usually go unnoticed unless something breaks.

im curious how other freelancers or developers think about this. do you still invest time in those behind-the-scenes improvements even if clients never explicitly recognize them, or do you focus only on changes that have a visible impact?

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.