I Built My Own dev.to Feed Page Instead of Embedding a Widget

There’s an easy way to show your dev.to posts on your website. You paste in a widget. You let it render. You move on. I almost did that. But the more I looked at it, the more it felt slightly disconnected from how I build everything else. So I didn’t embed it. I built my own feed page instead. Why I Didn’t Use the Widget This wasn’t about avoiding convenience. It was about consistency. My site is fully hand-built — HTML, CSS, JavaScript, structured layouts, injection layers, theme handling. Everything is intentional. Dropping in a third-party widget would have worked, but it wouldn’t have felt like part of the system. It would’ve been something sitting inside it. And that difference matters more than it sounds. The Approach dev.to provides a public RSS feed. That’s data. So instead of embedding a UI component, I fetched the feed, parsed the XML, and rendered the posts as native components on my site. No iframe. No external styling. No layout overrides. Just data → structured objects →