Hacker News Reader

Hacker News

Comment by a012 | Hacker News Reader

Parent Full thread

a012

> I strongly recommend to anyone to build their site to static HTML and serve that if at all possible.

Is there any products that support CMS as backend and automatically generate HTML as frontend OOTB?

View on HN

I recommend gatsbyjs (react.js based static generator) and it has plugin for Drupal and Wordpress.

Here is the location of the Drupal plugin: https://github.com/gatsbyjs/gatsby/tree/master/packages/gats...

And the headless Drupal GatbyJS demo: https://using-drupal.gatsbyjs.org/

So what tool would be used to extract the static information from the site conveniently? Or does it still need a running instance of Drupal to function? Cause that would still leave you vulnerable to Drupal exploits basically.

There are various things you could do with the headless Drupal: you could put it behind a Firewall or enable access control where only your front-end Gatsby.js app can have access to.

I really like Gatsby & static site generators, especially when hosted on something like Netlify.

Have you used it with a Drupal or WordPress on a larger site? To do a decoupled site, every time someone publishes a new article or a change, you are going to have to do a ton of HTTP requests during build time for Gatsby since incremental builds are not a thing yet. If you use the Drupal Paragraphs module, that can really complicate things as well. The only way around this with Gatsby that I can think of is to have Drupal create a repository of static files that get incrementally updated. Then Gatsby could grab a compressed version of this during build & create a new version of the site.

I would love to hear thoughts from anyone else though as I'm sure better ideas must exist.

I noticed this too. I wrote a WordPress plugin to trigger a TravisCI build when I publish a post and this works great, but it takes 5 minutes or so to publish a new version of the site. For me this isn’t a huge deal, although waiting 5 minutes to fix a grammar issue sucks, but for some this is going to be a bigger deal when they’re used to being able to make changes instantly.

I noticed that the Gatsby WordPress plugin hits every endpoint on your site to build the graphql data store, you could probably modify it to just hit the ones you need. Additionally I feel like there should be a way to do persistent incremental builds. At least there should be a way to cache the graphql stuff. Maybe a incremental webpack build plugin exists.

Incremental builds via Webpack being worked on. Gatsby is waiting on these - https://github.com/gatsbyjs/gatsby/issues/179

depending on how complex your url structure is you could have wget download everything from your local cms, then rsync it to your webserver. I have been considering doing this with a side project I am working on.

For our corporate site, we use Drupal internally, and then use httrack and bash to package it up statically and deploy to our public web server. This works very well, and allows our marketing department to easily maintain it while keeping our server reasonably safe.

I use Jekyll along with Jekyll+ [1] for the CMS. Put it behind CloudFlare and you have a very professional solution.

It supports multilingual content, custom content types, media... Most of what you'd do with any other CMS.

For reference, it runs the new Starbucks website [2].

1: https://github.com/Wiredcraft/jekyllplus

2: https://wiredcraft.com/blog/the-new-starbucks-cn-website-bol...

forestry.io works with Jekyll/Hugo.

+1 to Forestry. Lets me build lightning fast static sites for people that they can easily edit. I recently deployed a site that uses https://lunrjs.com/ to also allow for quick browser-side site searching.

An honorable mention goes to Netlify CMS. I just wish they had documentation on how to host the service yourself.

You can get started pretty quickly with Jekyll+ [1] and self host it at no cost [2] using now [3].

1: https://github.com/Wiredcraft/jekyllplus#quick-start

2: https://github.com/Wiredcraft/jekyllplus#installation--devel...

3: https://zeit.co/now

Movable Type?

Reply on news.ycombinator.com