You read my post about the <output> element. You might not know what happened next.

It hit #1 on Hacker News. Even ended up #13 post of the year so far. Shared on Reddit and Lobsters. Over 60,000 people read it.

All that from a 25-year-old HTML element that most developers thought was a typo.

But the numbers aren't the interesting part.

The interesting part is what people did with it:

A Joomla developer opened a pull request citing the article as justification for accessibility improvements. Blazorise started discussions about implementing it properly. It got picked up in Polish newsletters, Chinese developer digests, and Orange's accessibility roundup.

Developers in multiple open source projects shipped actual fixes because of one blog post about an HTML element most people didn't know existed.

That's why I'm writing to you.

Here's what I learned: Developers are hungry for the web-native side of frontend again. The built-in stuff that's fast, accessible, and just works. Not everything needs a framework, a build step, or 47 dependencies.

That's what you'll get from me. Underused patterns that are already in the platform. Performance techniques that don't require rewriting your stack. The stuff that actually ships and stays shipped.

When will I send these? When I find something worth your time. Probably monthly, maybe less. I'd rather send you one thing that changes how you think about the web than weekly filler that wastes your inbox.

What's next: I'm working on a post about JS framework lock-in and how to avoid making it inevitable. It's about the decisions we make today that paint us into corners tomorrow.

If you want to unsubscribe, I get it. No hard feelings. Link's below.

If you're staying, thanks for trusting me with your inbox. I'll try to earn it.

No growth hacks, no "7 secrets," no AI-generated listicles. Just actual web development.

— Den

P.S. If you missed the original <output> post, it's here: https://denodell.com/blog/html-best-kept-secret-output-tag