While my own solution is specific to Kirby CMS, two great alternatives for self-hosted “website strike” banners have been shared - both great options to join the #globalclimatestrike with privacy-friendly, technically independent solutions:
A Wordpress plugin
“Webrocker” Tom created a port of the CMS-router-based solution to Wordpress; a simple plugin that even takes into account caching and features configuration settings.
Just as with the Kirby solution, the CMS is going to return HTTP error 503 and a simple banner page for any but manually excepted page requests on 20 September.
Self-hosting the “official” banner
Meanwhile, Matthias Ott shared a pragmatic solution for avoiding to introduce third-party dependencies to his site while using the advanced banner solution from globalclimatestrike.net: he created local copies of the JavaScript-widget and banner page - making full use of the designed experience while keeping all requests local.
To replicate this solution, incl. disabling the Google tracker:
- Save and copy index.html, the logo and widget.js into a folder on your server, e.g.
/climate-strike/
. - Then save and copy katwijk-mono-bold-web.woff2 and greve-800-web.woff2 into subfolder
/fonts/
of that folder. - Lastly include the following HTML near the bottom of your website template, replacing
PATH
with the URL of the folder with the cloned files:<script type="text/javascript"> var DIGITAL_CLIMATE_STRIKE_OPTIONS = { disableGoogleAnalytics: true }; </script> <script src="https://PATH/widget.js" async></script>
My personal preference is on the server-side solution, while the banner widget is admittedly more refined (and creates awareness in the run-up to the event). Ultimately, all of these are just means to an end - if you want to join the global climate strike on the web, choose whatever works best for you!
Footnotes
- globalclimatestrike.net has in the meantime released their own Wordpress plugin as well, but it loads the banner remotely and by default contains a Google Analytics tracker unless manually disabled. ↩
- Instructions for self-hosting have since been added to the official code repository as well, but those require experience with, and use of, Git repositories. ↩