Automate GitHub Pages with IFTTT, Glitch and Jekyll

Re:Automate GitHub Pages with IFTTT, Glitch and Jekyll by doublerebel on Friday November 24, 2017 @11:58PM (#15774520)

This seems like too easy a question, but

- WordPress is dynamic, not static, which contributes to:

- WordPress takes more resources to run, and

- WordPress regularly has security holes

- WordPress is therefore not simple because it requires maintenance

- WordPress relies on countless server- and client-side dependencies, which contributes to the maintenance and server requirements

[ Parent | on HN ]

Re:Automate GitHub Pages with IFTTT, Glitch and Jekyll by paradite on Saturday November 25, 2017 @01:30AM (#15774728)

> WordPress relies on countless server- and client-side dependencies

Which you have access to the source code and ability to choose when to upgrade.

Compare that to GitHub, Glitch and IFTTT, which:

- Also have countless dependencies, but not just in the source code, in their service architecture as well

- You do not have access to source code

- Can make your blog offline when they experience service disruption

[ Parent | on HN ]

Re:Automate GitHub Pages with IFTTT, Glitch and Jekyll by btgeekboy on Saturday November 25, 2017 @02:27AM (#15774871)

The only step in that chain that can take your blog offline for visitors is GitHub pages. The cool thing about static sites is they're really easy to replicate to a second provider. Or a 3rd, 4th, nth...

[ Parent | on HN ]