Zum Inhalt springen

Archiv für Mai 2016

Currently listening to the very good #btconf edition of @workingdraft . Good stuff inside. #teamweb
http://workingdraft.de/263/

Ch-ch-ch-changes

For a long time it has bugged me that the css for the recent version of my site was desktop-down. I made some adjustments for adaptive/responsive behaviour three or four years ago, but since the code base of my site is organically growing since I started it on WordPress in 2005… uhm, I think you get the picture. So all I did back then was to consider how the site should look on smaller screens, and making modifications inside max-width media queries, keeping all of the desktop-related stuff as the default styles, outside any media queries.
Of course when starting ...

E ciao Marcello!

Sorry to miss out on the 2016 IndieWeb Summit, but wishing everybody attending a jolly good time

Revisiting the Service Worker / Offline cache

Motivated by the sudden appearance of the "Add to home screen" prompt, I spent the last couple of hours to tune my Service Worker / caching behaviour:

- I can now exclude parts of my site from the service worker. This was an important feature for me, since the WordPress backend didn't sit too well with stubborn cached items.

- I established a number of caches for different items:
-- a "static" cache that has the base css and the page that gets displayed when the network is offline.
-- a "content" cache, that stores up to 25 URLs a visitor has, well, visited, while being online.
-- an "image" cache, that stores up to 45 image files, and finally
-- an "asset" cache for up to 35 files (everything that is not HTML and not an image).

The limits are rather random, but I think each cache has an build-in maximum of 50 entries (?), so to see if it works, I choosed numbers smaller than that.

Progressive Web(rocker)App

Ha! It! Really! Works!

I have to admit I was a bit sceptical of the outcome after I tweaked and added things and bits of my website at the Indiewebcamp in Nuremberg, setting up a service worker and offline caching things, adding a manifest file … while in theory I understand what all of this was supposed to do, I felt a bit dumb for not completly grasping how to control the stuff.

So as so often when learning new tricks on the web, it started with copy/pasting a working solution and trying to adapt this to my ideas.

But ...

Regressive Web Apps – Jeremy Keith

[…] Looking at most of the examples of Progressive Web Apps, there’s an even more worrying trend than the return to m-dot subdomains. It looks like most of them are concentrating so hard on the “app” part that they’re forgetting about the “web” bit. That means they’re assuming that modern JavaScript is available everywhere.
adactio.com

I'm again with Jeremy Keith here. I'm team web. Links and Urls (and being responsive) are the web's superpower. Don't cripple that by trying to emulate 'native'.

(and I want to add a second like for the usage of the word 'flabbergasted')

Wrestling with the ServiceWorker

Dear js gurus in my timeline, is this the correct way to exclude urls from the power of ServiceWorkers?

@m_ott ha, interestingly your tweet here triggered a "homepage mention" on my site, and one on the article too :-)