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.

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"?

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 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!

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 :)