💻 Some junk I've built

✨ Emojis as favicons

A simple JavaScript snippet to render emojis as favicons on a page.

💺 Places I've been

A map of the places I've been. It's pretty incomplete as of yet, both in terms of code and the places I haven't recorded correctly and haven't been yet :)

📅 Life calendar

A pretty depressive calendar that shows my life, if I turn out to be 90 years old, with each "lived" day marked green. I added some life events I've had so far on there.

🥗 My recipes

I collect my recipes here. I really liked my moms recipe book and want to collect my own somewhere. Having it online rather then in a physical book makes more sense to me.

📝 Notes

I feel like Archer really holds up as a TV show

Having a public Zettlekasten System is sounding more and more appealing to me.

Web Components are supported in all modern major browsers

"Web Components" and "Modern Major Browsers" are both moving targets, so this might not always be true, but Web Components can be shipped to most users for basic usability.

ChromeEdgeFirefoxIEOperaSafari
customElements547963No4110.1
ShadowRoot537963No4010.1

If there was a real need to support older browsers, you could resort to using a polyfill, but that comes with its own limitations.

References

‘Window.CustomElements - Web APIs | MDN’. n.d. Accessed 30 March 2021. https://developer.mozilla.org/en-US/docs/Web/API/Window/customElements.

‘ShadowRoot - Web APIs | MDN’. n.d. Accessed 30 March 2021. https://developer.mozilla.org/en-US/docs/Web/API/ShadowRoot.

Using the operating system fonts on a website instead of loading a web font is much more feasible in 2020 than in previous years since system fonts have gotten much better.

Loading system fonts instead of web fonts are preferable if possible for Web Performance since there is no network request required to get the font and the end-user will avoid a potential Flash Of Unstyled Text.

Wonder if I can pay a designer to refresh my website 🤔

Made by hand and JS in Reykjavík and London.