惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
人人都是产品经理
人人都是产品经理
Cisco Talos Blog
Cisco Talos Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
V
V2EX
博客园 - 三生石上(FineUI控件)
Martin Fowler
Martin Fowler
WordPress大学
WordPress大学
D
Docker
S
SegmentFault 最新的问题
博客园 - 聂微东
美团技术团队
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Last Week in AI
Last Week in AI
M
MIT News - Artificial intelligence
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
GbyAI
GbyAI
L
LangChain Blog
Vercel News
Vercel News
博客园 - 叶小钗
MongoDB | Blog
MongoDB | Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
The Cloudflare Blog
Engineering at Meta
Engineering at Meta
T
Threat Research - Cisco Blogs
T
Threatpost
Scott Helme
Scott Helme
T
Tailwind CSS Blog
Latest news
Latest news
Stack Overflow Blog
Stack Overflow Blog
Blog — PlanetScale
Blog — PlanetScale
The Register - Security
The Register - Security
罗磊的独立博客
P
Proofpoint News Feed
腾讯CDC
S
Schneier on Security
雷峰网
雷峰网
A
About on SuperTechFans
T
Tenable Blog
F
Full Disclosure
Cyberwarzone
Cyberwarzone
博客园_首页
有赞技术团队
有赞技术团队
K
Kaspersky official blog

文章列表

Compulsive curiosity, or, how I built an infinite idea machine Gift details on the subscriber portal Portal link in the archive nav The physicists who convinced Fermilab to send Brazil's emails First, add no friction: How micropayments lost and subscriptions won Filter subscribers and automations by source Automations, rebuilt What email will look like in the future Filter subscribers by bounce date and reason Email could have been X.400 times better Three features are moving behind the paywall Firewall changes and improvements Put your name and voice into your company newsletter Simplified email address settings Subscription wall Inboxes were overwhelming before we'd even named them The US government tried really hard to screw up email Public postmortem: database connection exhaustion Ask a nerd: what is the best way to unsubscribe from newsletters? Bookshop.org embeds Email was into agents before they were cool Passwordless login Rename metadata keys in bulk A spring cleaning for our legal docs Ask a nerd: what happens when you click the spam button? Passkey support for two-factor authentication How Buttondown's API versioning works Safer defaults for the email creation API How to send email to space How we enabled Content Security Policy for everyone Recovery codes for two-factor authentication Filter sent emails by engagement rate How we migrated to TypeIDs without breaking clients How we check every link in your email Use newsletter metadata in your emails Should we bring back email exploders? Sort and filter by open and click rates Custom click tracking domains More newsletter settings in the API Revamped replies Custom email templates for everyone Simplified cancellation Ask a Nerd: Does email length affect deliverability? The changelog, reborn Swedish localization Forwarding an email is not always straightforward Public descriptions for tags OpenAPI spec for archives How Rodrigo brings a humanistic view to consumer technology Survey responses on the web How Brandon Lucas Green shares his music and supports artists Subscribers can come from anywhere. Even another newsletter platform's form. Your newsletter's archives are more valuable than your list Better tag self-management Smarter automation filters Granular API keys New design settings pages Snippets Ask A Nerd: How does newsletter cadence affect deliverability? Starred views More ways to customize your archives Inbox filtering Mastodon follower analytics Ask a Nerd: What are good open, click, and response rates for an email newsletter? How we migrated our database to PlanetScale Two new archive themes Ask a Nerd: Does attaching files to your newsletter hurt deliverability? Custom buttons now work in Markdown mode Seline and Tinylytics support Unban subscribers Announcement bars for your archives Public postmortem: archive downtime Bang paths, source routing, and how email trips were planned 2025 disposables.app Russian localization Ask a Nerd: Can you improve email deliverability with a personal domain? More locale options How we interview customers at Buttondown Bluesky analytics Minimum viable complexity Reply to conversations How Jeffery Hicks goes behind-the-scenes in his newsletter Changes to our stack in 2025 2026: Emails Randomize survey answer order TK reminders in the editor What the hell is a UTM? Why we insourced analytics Scroll sync in the editor 2026: Archives How Kelly Jensen uses Buttondown to discuss key library issues How Jamie Thingelstad uses Buttondown to explore tech topics Keeping feature creep at bay Improved filters Content Security Policy in archives Open source Sniperl.ink Auto-activating RSS reader subscriptions What the hell is ActivityPub? Gift subscriptions
How Stefan Judis teaches thousands of developers every week
Asharee Peters · 2024-01-23 · via

Stefan's a long-time Buttondown user and longer-time frontend developer. He's scouring the web to learn more about core frontend technologies and sharing them with his subscribers at Web Weekly.

As a subscriber of Web Weekly myself, it was a blast to talk with Stefan about how his newsletter stands out from the pack and what he's learned along the way.

To kick things off, give me a sense of your background. Who you are. What your day-to-day job is. What are some of the things you're interested in now?

I'm Stefan. I was born and raised in Germany. I live in Berlin. I've been doing JavaScript stuff since — I don't know, I feel like I've lost count at this point. Maybe I'm closing 15 years with a background in frontend engineering. Seven or eight years ago I started blogging and getting involved in the community in Berlin. And because I spend a good chunk of time reading Frontend news, I thought why not start sharing the good things “officially”,

At first it was just monthly — "Stefan Judis' newsletter", kinda thing — and then I saw that the domain webweekly.email was free. It was like, "should I rebrand? Should I buy the domain?" At the end, I did it with the assumption that it looks more serious; it looks bigger than it maybe is, and that it looks more official than a Weekly Newsletter from a random stranger on the internet. Since then, I have done this newsletter thing on a weekly basis, and it is going well!

Many people know how to do something with React, Vue, Angular, or whatever you want to call it — but don't know anything about the underlying bits, like the DOM and HTML. I want to reach people who are interested in that.

Can you talk a bit more about the type of content you try to cover? What is your ideal subscriber? What do they look like? What information and links are you trying to curate for them?

The ideal subscriber of Web Weekly is someone who is curious to understand how things work. My incentive isn’t to know and share how to do ABC with Framework DEF, but rather, understand how the web works.

I, for example, talked to a lot of people and did some workshops, teaching, and boot camps in Berlin. There is an astonishing amount of people who are very good at frameworks. I think the web industry is on its way to the next abstraction layer. Many people know how to do something with React, Vue, Angular, or whatever you want to call it — but don't know anything about the underlying bits, like the DOM and HTML. I want to reach people who are interested in that.

If I sit in front of my computer, and I'm like, "huh, that's new" — I can’t be the only person. This is how I want to progress. So an ideal Web Weekly edition, for me, includes something I learned. And I see huge value in sharing nerdy details and fundamental web dev facts.

Going back to the shift from monthly to weekly, can you talk about why you made that shift? You mentioned it can be hard keeping up that publishing schedule.

If you run something monthly, your subscriber base will grow very slowly. Eventually, it almost felt like it’s not worth it. The impact was too low and I wanted to see results. Also, very few people wait for or expect a monthly email. 😅

I started doing it weekly with the idea to grow it faster and maybe start making some money out of it.

I think there is a misconception out there — "oh, just because I used to work in DevRel means I must get thousands of subscribers just by sneezing". It's still hard! There's no magic bullet.

Where do most of your subscribers come from these days?

Without doing anything, I can see something between two and six subscribers per day coming from my own domain at stefanjudis.com. So there is organic growth. If I had the time, enough money, and energy, I probably would double down on the social thing and ads.

I think there is a misconception out there — "oh, just because I used to work in DevRel means I must get thousands of subscribers just by sneezing". It's still hard! There's no magic bullet.

But speaking of "organic growth", it can be such a loaded term. Organic growth does not equal organic growth because if a person with 100,000 Twitter followers grows their list organically, the list will grow a thousand times quicker than mine. 😅 Sometimes talking about organic growth is comparing apples and oranges.

You're not only the nicest person but also super responsive. It is incredible what you're doing.

So what brought you to Buttondown?

I started playing around with Buttondown because a person chatted on Twitter and was vouching for you and your service, which is still exceptional. You're not only the nicest person but also super responsive. It is incredible what you're doing.

I think your personal approach is super valuable. It feels great not to be a ticket number in a ZenDesk queue.

I don't know how you do it, but if I need something or if there is a problem, you're back with me in 12 hours and we figure it out. I think this is what makes Buttondown stand out.

Your use of Buttondown — with building your own archives and so much custom frontend work — is unique. How does Buttondown fit into your CMS?

First off, my setup with Buttondown is weird. I only use three things:

  1. Your subscriber management
  2. Your email sending
  3. Your editor

It's like Buttondown in 'headless mode'. I publish and write things in Contentful; from there, I publish it to my blog. Then I have a little tool that transforms my Contentful Markup (I have some custom things on the blog) to Buttondown Markdown and I simply paste it into the editor.

I've got a custom layout that you enabled for me around a year ago, just to have a custom footer and header.

But overall, I think Buttondown does the job just fine. It is out of my way. I think the default styles work. The emoji handling works. I think everything works out of the box. I don't have many customizations.

What could Buttondown do to make your life easier, either in terms of publication or sending things out?

Analytics. I wish there was a bit more power in the analytics section because there's so much data in newsletters that is fun to poke around -- I like to open up my computer and look at the user. Even if there is one person overnight, I look at their overall stuff. I do that every day. So, a bit more power there dividing by week, month, by day, or something.

Beyond that, what I would definitely appreciate is if there would be in Buttondown, a quick way for me to get the CTR in ads. If I could set an attribute on a link, I could go to the overview page and say, "the CTR on this ad was 2%." That would be tremendously valuable.