Wordpress Users: What scares you the most about static websites?


so po qwo ro
BuSo Pro
Oct 7, 2014
I have a handful of Jekyll sites. These are micro-niche sites, things that I knew could add some extra revenue to my business and I had no intention of flipping.

I agree with what @Steve Brownlie was basically saying - that the ease-of-use of WordPress prevents a site being unfairly devalued to 90% of prospective buyers.

Beyond a few projects I have with the intention of flipping I have absolutely no use for WordPress... I hate it, it's caused me more problems in terms of hours spent than learning HTML/CSS ever did.

I started up with Hugo the other day. I absolutely love it, even compared to Jekyll. There's no going back to WordPress on any future projects for me. Once my existing ones are flipped there will be no more flipping anyway.

I don't concur with @Ryuzaki regarding Static Sites being good for little 10 page sites. With static site generators like Hugo (which still create static sites) I think that you could easily have many hundreds of pages all managed and deployed easily.

What interests me the most about WordPress vs X is that there are so many passionate and angry WordPress supporters out there who will defend it against all logic... I think it's a pointless argument, you either know or you don't.


BuSo Pro
Oct 9, 2014
In my case, what kept me with Wordpress for the longest time wasn't quite fear as much as concern. Concern in not knowing much about the ecosystem of static site generators. The whole "stick with what you know" thing. Also concern in some of my own deficiencies in programming skill. I think most of that concern stemmed from wondering how to replicate plugin functionality I was using.

Over time, I've come to realize I never even needed many of those plugins in the first place. In other cases, being able to take a step back and see things from more of a systems programming standpoint, I've had realizations that there were simply better ways I could achieve something without needing some third party plugin.

For example, generating pages from data files. Like taking a JSON file and generating a page for each object in that file. The end result being, for certain page types no longer needing a separate markdown or other file for every single page on a site.

What kept me moving the direction of static sites is, I always had this feeling there was a better way to be building a lot of the sites I was building. Building a database-powered SMB website for some local business... when they have less than 10 site pages... Just feels like using a sledgehammer to hit a nail.

The dilemma I'd always come to, though, is what to do if a client wants a CMS so they can edit content themselves? That kept me on the fence with static sites for awhile. Thankfully, in the last few years a number of CMS solutions have popped up to solve that. Some, like Netlify, are actually free or close to it. There are others as well, such as: Contentful, Forestry, Cockpit

With most of these newer standalone CMS options, however, knowledge of Javascript is becoming a more important factor. That's going to be a pain point for many, because the more time spent coding means less time on efforts that drive ROI. For others, maybe writing a few lines of JS is no big deal.

Another +1 for Hugo. Out of all the SSGs I've used, I've been by far the most productive with it. It'll easily handle several thousand pages, even with complex queries. Several users in that community have stress tested it up to I believe ~650K pages. At that point, build times are in the tens of minutes.