Skip to content

Latest commit

 

History

History
71 lines (47 loc) · 3.4 KB

README.md

File metadata and controls

71 lines (47 loc) · 3.4 KB
Raw

blog-pwa

What started as an experiment in 2017 mixing Hugo, Polymer, and the PRPL pattern to build a progressive web app turned into a very robust and fast engine that powers my blog. As the web platform grows, so does this engine.

Features

  • It's a progressive web app with all the fixin's (service worker, PRPL pattern, H3, et cetera)
  • The base PWA component and it's bundle weigh just 15.1KB gzip'ed on the wire.
  • Renders if there is no JavaScript via <noscript> injected fallback to static generation
  • Renders metadata to linkbots when sharing without the need for client JavaScript via server side detection and alternative render path

The basics

  • lit powers the app shell and web components, with a few vanilla web components for good measure.
  • hugo to write and manage posts and page metadata
  • workbox for generating precache and runtime caching service worker
  • rollup for handling the bundles and splitting for our PRPL lazy loading goodness
  • h2-push via http2push-gae for Google App Engine for serving

The not-so-basics

I wrote a couple zsh utility scripts to power most of the shuffle and build of the site. Why not an npm script or a gulp or grunt task you ask? Frankly, because I just felt like writing some shell scripts. Don't you want to sometimes just write some shell scripts? Is that just me?

The gist of the tools employed and their uses include.

  • sed is amazing and helps wrangle some of the JSON output from Hugo (years of old posts + multiple times moved = fun!)
  • zmv is the thing you've probably never heard of about but might want to try. Renames files fast to proper type (Hugo won't output pure JSON at moment)
  • jq is blazing fast over lots of files; validates my json output so I know things will load in the PWA and Python
  • @web/dev-server handles the dev serving
  • workbox-cli handles the service worker generation
  • rollup-cli handles the es modules and bundles splitting for prod builds
  • http2-push-manifest is super useful and works out of the box with http2push-gae
  • make has a basic set of commands that alias the zsh script for easy use
  • Okay, so there is app/package.json with prettier linting and some build commands in the yarn for rollup and what not. It's mix and match. :-)

Setup

➜ git clone git@github.com:justinribeiro/blog-pwa.git
➜ cd blog-pwa
➜ chmod +x utilities/builder.zsh

# check for tooling
➜ make setup

# run dev env
➜ make dev

# run GAE deploy silently
➜ make deploy-no-promote

By the web perf numbers

A progressive web app is only as good as the web performance it offers. I mean, who wants to sit around waiting 10 seconds for a blog post to initially load? No one.

Pulling up a trusty Moto G4 on 3G over on WebPageTest, we can see just how fast we are:

2024:

image

2023:

image

2019:

image

Just want the traces and the raw numbers? Check out the results on WebPageTest.