The static site with local #webpack development environment is already paying off! Google Lighthouse accessibility score for hyperbo.la is now 100 with increased text contrast. #a11y #lighthouse #hypstatic

The static site is based on webpack and webpack-html-plugin with a few preprocessor scripts that emit the templates #webpack #js

Making a mental note that I've decided to go static with hyperbola. Not sure when this project will get done, but here's to 2019. I have dreams of a custom #webpack and #markdown generator, S3 and CloudFront for distribution.

Optimizing #react bundle ... cut bundle size by 72KB. Biggest wins are turning an image into CSS + an emoji, removing unused deps, enabling mini-css-extract-plugin in release builds #win #webpack index.html is 333 KB

41-commit weekend 🤩Feel much better about my #webpack , #ansible, and #packer code #win

I completed removing build artifacts from source control. Static assets dist and document-root dirs: replaced with running #webpack on host. Third-party #ansible roles: installed from galaxy via #packer and #vagrant at provision time. #win

Significantly refactored my #webpack static asset pipeline today. No longer build assets locally and check them in. Build happens as part of #ansible provisioning. #win https://github.com/lopopolo/hyperbola/commit/eaf5b3197

The #webpack configuration, on the other hand, was not fun to get set up. I particularly struggled fighting with the gulp plugin, which pins webpack 1.x

#webpack is amazing. I added the time-elements web components to the lifestream and contact pages. Only took an hour. Before this would have been next to impossible. #frontend #win