Skip to content

Latest commit

 

History

History
68 lines (35 loc) · 2.83 KB

README.md

File metadata and controls

68 lines (35 loc) · 2.83 KB

my-blog

Features:

  • favicon - DONE!
  • google analytics - DONE!
  • SEO - DONE!
  • turn into a PWA - DONE! - TO BE IMPROVED IN FUTURE WITH WORKBOX

Acknowledgements:

Tag Generator - Python

Jekyll Site/Repo for reference

Note: UA (Universal Analytics) was configured instead of G- see Configure o Analytics para um Website (Universal Analytics)

I used https://looka.com/ for LOGO design.

SEO

Turn website into PWA

Working without Workbox ... In this approach I have specifically to say what are the routes that I want to cache for offline support.

"service-worker_reference.txt" - for reference: Como transformar um site no github pages feito com jekyll em uma pwa

"service-worker.js" - active for now, with offline page: Adding a service worker to Jekyll

Manually managing the cache storage via your Service Worker script can be a tedious task. The number of files and their names may change, so hard-coding them does not seem like a good idea. That’s where Workbox comes in.

TODO: Another tutorial, but using Workbox

Jekyll website to progressive web app

Note: For now if you Lighthouse audit the site, PWA is checked.

Important site to know more about PWA and ServiceWorker cache: PWAdvent.dev https://pwadvent.dev/day/5/

Change to a regular theme instead of a Gem-based theme

With this change I now have all the freedom to make changes to my blog.

Up and Running with GitHub Pages, Part 4, Jekyll Themes

Important command for copying files from minima gem: xdg-open $(bundle info --path minima)