Zach Leatherman :11ty:

Zach Leatherman :11ty:'s avatar
Zach Leatherman :11ty:
zachleat_at_fediverse.zachleat.com@momostr.pink
npub19vzl...zmql
Follow along to learn about web development news, best practices that “don’t work,” and web standards that are “not the future.” 🫣 Go to https://www.zachleat.com/ 🎈 Maintainer of :11ty: nostr:npub1f8f0a0zeh08zataqn754drr239anhqc2m94jfc7c6ucwf59n3c3slmed9x https://www.11ty.dev/ 🎉 Web Builder at :fontawesome: Font Awesome 🌾 A random person from Nebraska maintaining software 🕸️ Front of the front-end web developer 🏳️‍⚧️ Listen to Trans Folks 🌍 Keep building for the Web 🧞 he/him/they 🔎 #searchable Blog: https://www.zachleat.com Eleventy: https://www.11ty.dev Eleventy 🐘 Mastodon: https://neighborhood.11ty.dev/@11ty Bluesky: https://bsky.app/profile/zachleat.com
as “industry” survey season rolls around again it’s important to remember that the results from these things reflect the biases of the most popular dev communities that promote them (and then we get to all pretend like the results are meritocratic) I now believe it’s better to not participate at all
Thinking about dark/light mode pickers that have three options: Auto/Dark/Light. If the default is “Auto” — in what scenario might someone want to move away from Auto (which would visually be a noop to the same theme?) I’m using Light mode as my system preference, but it seems unlikely that I would swap from Auto (Light mode) to Light mode (not Auto) on a specific site