There are now several competing nice services, that give you and your customer a UI to edit your static site with a webtool. https://cloudcannon.com / https://forestry.io/ / https://www.siteleaf.com/ With all of them you can set up nice content type templates and get your client to put structured content. edit: formatting
Also * https://datocms.com * https://prismic.io/ * https://www.contentful.com/
Ask HN: Do you suggest static site generators to your customers?
31–40 of 53 posts
Re: Ask HN: Do you suggest static site generators to your customers?
#32Yes. But they don't know it. They just know that their site is faster than their competitors. I've got a smallish piece of JS that gives the client a WYSIWYG editor, which speaks to Firebase. When Firebase gets an update, it triggers a rebuild. Best of both worlds.
Re: Ask HN: Do you suggest static site generators to your customers?
#33Re: Ask HN: Do you suggest static site generators to your customers?
#34I'll be doing a private release in few weeks for the beta subscribers.
Re: Ask HN: Do you suggest static site generators to your customers?
#35Re: Ask HN: Do you suggest static site generators to your customers?
#36Yes. I built a statically generated site to a Fortune 50 company. Not a microsite either, but one that was highly visible.
Re: Ask HN: Do you suggest static site generators to your customers?
#37Earlier quoted context omitted.
WordPress has had one-click updates for years and makes it easier than any other CMS I've seen. It's been doing a fine job and powering 25% of all pages on the net and growing.
The problem is that updating plugins very often breaks stuff.
Re: Ask HN: Do you suggest static site generators to your customers?
#38A real-world example would be the First Round Review (http://firstround.com/review/), designed by our studio (https://marquee.studio) and running on Proof.
Re: Ask HN: Do you suggest static site generators to your customers?
#39This is even easier then something like WordPress for them, and much simpler for me. WordPress deserves credit for its ease of use for non-technical people, however I don't view this as a good metric for what to choose for a website.
I deliver the _site folder as a finished product and put it on Cloudfront with HTTPS. That's about as simple and unbreakable as it gets. Customers can then pay a monthly retainer or occasional hourly rates for updates. If they want the source files to run the generator on their own machine that's fine too, but it costs extra.
The model isn't that much different from a wedding photographer.
Re: Ask HN: Do you suggest static site generators to your customers?
#40Non-developer staff have been fine with this, editing Markdown files within the Github interface and adding the occasional PDF. If something doesn't look right on the test site, they can ask for advice.