Dev.to articles on any website.

Dev.to is the public-facing brand of DEV Community, but the platform itself is Forem, an open-source codebase released under the MIT License and developed publicly on GitHub at github.com/forem/forem. Forem was open-sourced in 2019 and has been the basis for Dev.to since the platform's founding in 2017 by Ben Halpern, Jess Lee, and Peter Frank. Because Forem is open source, the platform's architecture, API surface, and content model are visible to anyone, which is unusual in the writing-platform world and matters enormously for widget tooling. Where Medium relies on undocumented internal endpoints and Substack ships a closed JSON feed, Forem ships a documented public API at dev.to/api covering articles, users, organizations, tags, comments, listings, and reactions, plus standard RSS feeds at dev.to/feed/yourhandle. The API is rate-limited generously for unauthenticated public read access and explicitly supported for third-party tooling, including widgets like this one. Forem is also self-hostable, so any community running their own Forem instance has the same API surface available, which is why Poper supports both dev.to and self-hosted Forem instances behind the scenes through a single configuration. The open-source-first culture of Dev.to is the durable reason a Dev.to widget stays working when other community-platform widgets break: the contract is in the open, the codebase is in the open, and the community itself has a stake in keeping the API stable.

Dev.to is not a generic blog. The community has a specific culture built around inclusivity, beginner-friendliness, and constructive feedback, enforced by a moderation team and a clearly stated code of conduct. Articles tend to surface in waves driven by the community's tag system and the homepage feed rather than by a single editor's curation, which means even a first-time writer with a useful tutorial can land on the homepage if the article is well-tagged and timely. For a widget, this matters because the metadata that signals quality on Dev.to is different from a generic blog. Reaction counts (heart, unicorn, fire, bookmark) are the visible social proof on every article. Comment counts indicate active community discussion. Tags signal the audience, with conventions like #beginners, #showdev, #help, and tags like #rust or #typescript identifying the technical surface. A widget that strips this metadata and renders Dev.to articles as plain title-plus-summary cards is throwing away the most valuable signal the platform produces. Poper renders all four reaction types, comment counts, tag pills, and reading-time badges natively because that is what visitors expect to see when they recognize a Dev.to article. The cultural detail also shows up in code formatting. Most Dev.to articles are tutorials with significant code content, and Forem's Markdown renderer applies syntax highlighting via a stable theme. A widget that flattens code blocks to plain text destroys readability for the entire purpose of the article. Poper preserves Forem's code-block rendering with monospace typography, language hints, and a syntax-highlight palette that matches Dev.to's defaults out of the box, with customization available for sites that want a darker or lighter palette.

Tags on Dev.to function as topical channels. The home feed at dev.to/t/rust is effectively the Rust community on DEV, and it includes tutorials, debate posts, release announcements, and reading lists. Same for dev.to/t/webdev, dev.to/t/ai, dev.to/t/devops, and several hundred other technology tags. For a company building a developer-relations marketing program, this is gold. A SaaS company building a Rust-based observability tool can run a landing page at companyname.com/rust-resources that embeds dev.to/t/rust articles authored by their own team, alongside curated community content from other authors that uses their tag, building both authority and audience trust on a single page. Poper supports multi-tag merged feeds where you paste #rust, #webassembly, and #systems-programming and the widget interleaves all three tag streams chronologically, deduplicates articles that carry more than one of the requested tags, and surfaces all the metadata. This single feature replaces what would otherwise be a custom backend job pulling three separate Forem API endpoints and merging them, and it is the most-used feature on the Pro plan. Beyond tag filtering, Forem also supports series, which are ordered collections of articles by the same author. A 9-part tutorial on building a database from scratch is a series. A 4-part introduction to functional programming in Elixir is a series. Most generic blog widgets do not understand series ordering and render the articles in reverse-chronological order, which means a tutorial reads backwards. Poper queries the Forem series endpoint and renders the articles in chapter order, which is critical for any landing page that presents the series as a guided learning path. This is the difference between a tutorial reading list that converts visitors into students and a confusing pile of articles that visitors abandon.

Dev.to organizations are first-class entities. A company creates an organization page at dev.to/your-company and any number of contributors can publish under the organization byline. This is the canonical Dev.to format for DevRel marketing, and well-known engineering teams have used it for years to anchor a developer-facing content program without standing up a separate blog. The organization page on Dev.to itself is fine, but most companies want the writing to also show up on their main marketing site, the careers page, and the documentation site, not just on dev.to. A Dev.to feed widget pointed at the organization slug pulls every article from every contributor, sorts chronologically, and renders all of them with bylines intact. New articles by any team member appear on every embedded surface within an hour of publishing on a Free plan, or every 5 minutes on Pro. There is no manual cross-posting workflow, no editorial backlog, no risk of a contributor's article missing the marketing site because someone forgot to forward it. A common deployment pattern: the careers page embeds the full organization feed, the homepage embeds the most recent three articles, and individual product landing pages embed tag-filtered slices (the database product page embeds organization articles tagged #postgres and #database, the AI product page embeds articles tagged #ai and #llm, and so on). All four embeds reflect the same source of truth, and a single article authored once by the DevRel lead surfaces in every relevant product context automatically. This is the highest-leverage pattern Dev.to enables for a company building an engineering brand on the open web.

The single most common SEO mistake when embedding any blog widget is duplicating content without a canonical reference. Search engines see the same article body on dev.to and on yoursite.com, treat one as the original, and either suppress the other from rankings entirely or split ranking signal between the two URLs. The fix is to include a rel=canonical link tag pointing the embedded article back to the original dev.to URL, telling Google explicitly that yoursite.com is republishing and dev.to is the source. Poper handles this automatically. Every embedded article emits Article JSON-LD structured data with headline, author, datePublished, dateModified, image, and a canonical URL field set to the original dev.to article. Visitors browsing your site see the article rendered inside your design, but search engines see a clear signal that dev.to remains the canonical source. Your DEV ranking is preserved, and your site receives the SEO benefit of a fresh, content-rich page block without competing against your DEV article for the same query. This is exactly the same pattern Dev.to itself recommends for cross-posted content, where authors are encouraged to set the canonical_url field on cross-posts so the original SEO weight stays where it should. The widget makes this automatic from the embed direction. Combined with the asynchronous loading and global CDN edge caching that keeps the widget under 40KB gzipped and lazy-loaded below the fold, the performance and SEO posture of a Dev.to feed widget is among the cleanest of any embeddable blog widget on the market in 2026.