JAMstack is cool. If you haven't heard of Static Page Generators and Headless CMS yet, now's the time.
However, if you are familiar with it, and you know how to use them, then I need your opinion and help.
How do you convince a client to a static website?
What are your favorite players?
Do you have any tricks or tips you want to share?
Latest comments (49)
Coming to this thread a little late, but I have recently had to answer this question many times over, so I decided to do a little googling and arrived here...
First, I think the discussion here went a bit off the rails. Some people went down the path of "use the right tool for the job," which is valid, but irrelevant to this thread. The situation I find myself in more often is the client is a candidate for JAMstack, but that means they are also a candidate for Wordpress, how do I convince them to buy my product? The fact is these tools both get the job done but I work faster and deliver a better product in a custom, modern tool chain. So, if you want me to build your website, then these are the tools I use, and I can give this to you with exceptional service, fewer compromises, and at a good price.
In the end, you are the product, not the website. So when I sell a client I sell myself first. So when we arrive at the question of CMS to use, the tension is between wanting ME to build it but not wanting to use something they haven't heard of.
Here's the thing, I don't do Wordpress, or joomla, or drupal ever (anymore). I don't have to make every website on earth. I spent the better part of my early career wrestling with these CMS's, and they worked well for me back then. The issue is, most clients quickly learn they don't want to mess around with design as much as they thought and are constantly calling for tutorials on how to edit the navigation or to add a tag or how to edit something I had to hard code because it wasn't something the CMS supported out of the box.
Then I got DDoS attacks on
wp-loginpages, databases that weren't backed up, or had to deal with a purchased template that didn't work 100% on the version of PHP they were running on some cheap hosting provider. I even had a template that used to mysteriously wipe the custom CSS for no apparent reason. I've spent hours trying to implement a design that a friend of a friend gave to a client, frustrated at the fact that I knew I could hard code it in thirty minutes if I didn't have to deal with making it totally editable in this CMS or work with X plugin.Then I got used to version control, continuous deployment, automated testing, and at last found Contentful. I got used to an easy CDN for images that handled all sorts of manipulations as well as being able to do full re-designs later on without ever having to migrate a database or deal with hosting. Clients were actually editing their content only, they got exactly the design they wanted, for the budget they set out for. They were happy and so was I.
The fact is I don't need to build everyone's website. And if someone comes to me that really cannot live without Wordpress I'm happy to point them in another direction. But if you want my team and I to build your site it isn't going to be with Wordpress. I will work my ass off to get you exactly the design you dreamed about and will make sure that you are satisfied enough to never want to go with another developer.
There's a lot of talk about business in this thread without actually talking about a customers number one business need. A reliable, consistent developer that delivers a super fast, awesome website and can be called on over and over again to deliver updates. My advice to you is sell yourself and your company first to the client, then use whatever technology helps YOU deliver on the best possible service to that client.
After reading this thread I realized there's a million technical reasons to not use Wordpress anymore, but very few that clients understand, because what they are buying is a service not a website.
Whether or not there is immense business value in a specific site architecture is the wrong argument to have. There is immense business value in having the right person or team do the job and do it right the first time. I craft websites now that are always backed by a headless CMS but may or may not be JAMstack compatible but I constantly remind myself before every pitch the technology is irrelevant right now, make sure they buy the team first.
Great point of view. I agree 100% about selling yourself and your services first. I don't see a problem in working with WordPress, mainly because I am rarely in charge of the backend, database, or security.
Thank you for the great response.
If a site does not have Dynamic parts or they don't really want to update content themselves you don't even have to SELL IT.
The real benefits I see on general is
1) the site can be as fast as it can be as it needs no database lookups at runtime
2) best security as there will be no login functionality to be compromised
3) Those can probably translate to reduced maintenance costs depending on the automation you set for the deployment workflow and the frequency of deployment
EDIT: Just realized the post was from last august
Every comment counts. Thanks, Giorgos! 👍
I think static sites have a much lower barrier for entry for many clients, especially when they just need simple feedback forms or contact pages. I made a static hosting service for my classmates to use for their web projects. We weren't taught about deployment as a part of the class, and they needed an easy way to get their projects online.
Thus, dragdrop.site
I was kinda inspired by Glitch, but they needed a way to upload static files that they'd already written, and allowing them to drag files into the browser to deploy to a site is a pretty cool experience.
I"m going to argue a different way in favour of the 'JAMstack'; I hate marketing buzz, but whatevs.
This is the business value from what I can see; I'm newer to SPGs, so I could be wrong, but it's my current opinion.
Static sites do the following:
They are very very fast. Most WP sites that are setup on a budget are not fast and actually require hiring the right developer, not just 'any' developer to get it to serve quickly. Not the case with SPGs, if you can write HTML, CSS and JS then you are booming; it's very hard to make a slowly served site I'd wager.
Clients think they can just slap in a plugin and get a rocking; this is why wordpress is slow and they don't know who to call or what to do and they are channelling money into SEM and SEO and losing money there hand over fist; this is a huge value.
The code tends to be more easily read. This means if they call me up and say 'hey Roger can you create an xyz or do xyz', often I can do it in an hour or so and it's still fast and it's still easily read by the next guy.
Backups are built into the system al a github/git.
Security issues are basically null. In comparison to any surface like WP, effectively using Hexo, et all is a zero risk scenario.
Price. Outside of tools like Contentful and their type, the pricing is as close to $0 as you can get, which means I'm getting the lions share and that is good for me and good for my investment in good customer service.
Important caveats:
With Netlify and CloudCannon content management is included and no longer an issue of paying some over charging headless CMS provider extortion rates to just serve content.
Most SPGs come with Let's Encrypt and CDN built in and not as a value add either.
Honestly I'm very happy to have finally sold a client on a SPG and while down the road they may need to include a more diverse solution; today it'll be a great launch site for them handling so many potential scenarios without additional work on my or their part.
PS. This doesn't at all dismiss wordpress; that would be silly to say one over the other, just simply that SPGs have a ton of value and are very valid from a business use case.
You don't sell them a static website, because that sounds lame. You sell them a professional website with optimized loading and rendering performance and improved accessibility and SEO compliance, which is - what an amazing coincident - most easily achieved with a static web site and maybe some progressive enhancement with javascript.
I recently moved a bank from sitecore over to netlify, algolia, contentful using Gatsby and react.
The biggest selling point? Cost, security and flexibility.
Moving to jam stack offers huge potential for the future I reviewed all of the architecture patterns and with the bank wanting their content produced once but available anywhere it made real sense to move away from a tightly coupled traditional CMS.
One huge benefit of headless and the JAM stack is the incremental movement you can make.
We started out using just the static website and blog posts, product info and other content was all produced in markdown files. This got us to a point of replicating what we had without needing sitecore. It was also insanely fast without any database connections and Gatsby handling the build.
After that we added in contentful and removed the markdown where appropriate.
This is wildly inaccurate and unrepresentative of the JAMstack ecosystem. I'd consider it downright naive to say there's "very little business value" in static sites.
Consider Gatsby, for example. This is an open source static site generator for React that recently raised $3.8M in funding and formed a business around static site development.
Or perhaps consider Contentful, a headless CMS popular in the JAMstack ecosystem. They just raised $28M in funding late last year.
If your clients are happy with WordPress, that's excellent. By all means stick to WordPress! Where I work, though, are clients are constantly demanding more modern toolsets and pushing the limits of what a website can be. For these clients, WordPress is not a solution in which they are interested. We work with Contentful, Gatsby, React, Serverless and more on a regular basis for some very high profile clients. I can assure you that these clients find substantial business value in these "static" websites.
We've come a long way from the previous generation of static site generators. With the ability to deploy highly dynamic, browser-based JavaScript applications to CDN's, the line between a static and a dynamic site has become increasingly blurred. Gatsby, for example, has started to move away from the term "static site generator" to avoid confusion here.
The clients with which we work are designing and requesting functionality that would not be maintainable were it implemented in a few hours with a suite of WordPress plugins, so reaching for these modern tools is much more feasible in my day-to-day work.
I strongly suggest reading up on some literature and case studies on jamstack.org/ or check out some of Gatsby's showcase to see just how much you can accomplish with these tools. You'll find sites with full login workflows, ecommerce, and more.
A static site could be run on CDN like netlify for free.
You can sell it on safety. Tell them about security benefits.