Feed powered byStream Blue Logo Copy 5
GitHub Pages

GitHub Pages

Utilities / Application Utilities / Static Web Hosting

Decision about Fastly, Grunt, jQuery, Bootstrap, Jekyll, Let's Encrypt, Netlify, GitHub Pages, MaxCDN, StaticSiteGenerators, Webperf, GoogleFonts, CDN

Avatar of jdorfman
open source sustainer at SustainOSS
FastlyFastly
GruntGrunt
jQueryjQuery
BootstrapBootstrap
JekyllJekyll
Let's EncryptLet's Encrypt
NetlifyNetlify
GitHub PagesGitHub Pages
MaxCDNMaxCDN
#StaticSiteGenerators
#Webperf
#GoogleFonts
#CDN

When my SSL cert on MaxCDN was expiring on my personal site I decided it was a good time to revamp some things. Since GitHub Services is depreciated I can no longer have #CDN cache purges automated among other things. So I decided on the following: GitHub Pages, Netlify, Let's Encrypt and Jekyll. Staying the same was Bootstrap, jQuery, Grunt & #GoogleFonts.

What's awesome about GitHub Pages is that it has a #CDN (Fastly) built-in and anytime you push to master, it purges the cache instantaneously without you have to do anything special. Netlify is magic, I highly recommend it to anyone using #StaticSiteGenerators.

For the most part, everything went smoothly. The only things I had issues with were the following:

  • If you want to point www to GitHub Pages you need to rename the repo to www
  • If you edit something in the _config.yml you need to restart bundle exec jekyll s or changes won't show
  • I had to disable the Grunt htmlmin module. I replaced it with Jekyll layout that compresses HTML for #webperf

Last but certainly not least, I made a donation to Let's Encrypt. If you use their service consider doing it too: https://letsencrypt.org/donate/

8 upvotes1 comment5.1K views

Decision at TrackJS about Gatsby, Read the Docs, ReadMe.io, GitHub Pages, Jekyll

Avatar of toddhgardner
President at TrackJS
GatsbyGatsby
Read the DocsRead the Docs
ReadMe.ioReadMe.io
GitHub PagesGitHub Pages
JekyllJekyll

We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

4 upvotes2.7K views

Decision at Uploadcare about GitHub Pages, OpenSource

Avatar of Zmoki
Frontend Team Lead at Uploadcare
GitHub PagesGitHub Pages
#OpenSource

We have many #OpenSource libraries. Some of them need a demo besides documentation. We use GitHub Pages for a demo of libraries. We create a demo folder near with code of the library, add index.html with demo code and publish files only from demo folder to gh-pages. Fast and simple.

3 upvotes340 views