4 ms·

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.co

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/gatsby-source-drupal https://github.com/gatsbyjs/gatsby/tree/master/packages/gats... And the headless Drupal GatbyJS demo: https://using-drupal.gatsbyjs.org/ https://using-drupal.gatsbyjs.org/

giancarlostoro 8y ago
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.
- dberhane 8y ago
  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.
mattferderer 8y ago
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.
- octalmage 8y ago
  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.
  - mattferderer 8y ago
    Incremental builds via Webpack being worked on. Gatsby is waiting on these - https://github.com/gatsbyjs/gatsby/issues/179 https://github.com/gatsbyjs/gatsby/issues/179

giancarlostoro 8y ago

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.

dberhane 8y ago
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.

mattferderer 8y ago

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.

octalmage 8y ago
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.
- mattferderer 8y ago
  Incremental builds via Webpack being worked on. Gatsby is waiting on these - https://github.com/gatsbyjs/gatsby/issues/179 https://github.com/gatsbyjs/gatsby/issues/179