AMD: Building One Developer Community

AMD's developer audience is a constantly evolving group; someone experimenting with AI on the AMD ROCm™ Software might also be shipping a game with AMD FSR™ Technologies and helping an enterprise team evaluate EPYC™ and Instinct™ hardware capabilities.

AMD needed a community platform that could match that reality without splintering into multiple separate properties.

To address that challenge, the AMD Developer Community Team set out to create a unified destination where developers could engage with the broader developer ecosystem regardless of their primary focus.

The AMD team built a Discourse instance with 50+ categories, a points-based gamification model through external portal API integration, and tight ties into AMD's broader developer stack.

"Developers rarely fit a single label," the team explains. "A single Discourse instance lets us reflect that reality: one shared identity, reputation, and search experience, with clearly defined rooms for each audience."

The team needed infrastructure built specifically for technical developer communities: allowing deep discussion, tight integration with the broader AMD developer ecosystem, and a flexible foundation for customization and gamification.

Why Discourse

AMD Developer Community Team evaluated a range of options, but the decision came down to a few core requirements: an active open-source ecosystem that could be extended and customized over time; flexible integration capabilities that would connect cleanly with the wider AMD developer ecosystem; and a product roadmap and partnership model aligned with the needs of large technical communities.

"The move to Discourse was less about chasing a new platform for its own sake, and more about giving the AMD developer community infrastructure that can grow with our ambitions," the team explains.

Discourse stood out by offering a combination of flexibility and partnership. Discourse brings a mature foundation for large technical communities, a powerful theming and plugin layer for AMD-specific branding, and a collaborative relationship with the Discourse team that felt more like a partnership than a traditional vendor engagement.AMD wanted platform-level flexibility without having to build its own stack from scratch, and Discourse delivered.

50+ categories, mapped to real developer journeys

Taxonomy is core to the experience, so AMD did most of the upfront design themselves.

The team mapped 50+ subcategories to real developer journeys (AI, ROCm, game development, hardware) and tested whether people could quickly find their place in the community before they ever touched the platform.

This structured environment now hosts 5k registered users. It successfully sustained an average of 28k monthly forum visits throughout Q2 2026

"That gave us a draft structure and naming convention before we ever touched the platform," the team explains. "Once we had that draft, we engaged the Discourse team less as designers of our taxonomy and more as expert reviewers and partners."

The balance worked: AMD owned the intent and the language, while Discourse helped make sure the structure was technically sound, maintainable, and easy to navigate as the community grows. The team expects continuous refinement as AMD's strategic priorities evolve.

The single-instance bet

 One of the initial plans under AMD’s consideration was spinning up separate communities for each audience: one for AI researchers, one for game developers using AMD FSR™ Technologies and AMD Developer Tools, one for ROCm contributors, one for enterprise customers evaluating EPYC and Instinct.

"From a community operations standpoint,  consolidating multiple categories into a single forum is much more sustainable." the team says. "Instead of duplicating moderation, governance, branding, and analytics across multiple platforms, we can invest in making one space truly excellent."

The payoff is cross-pollination. AI researchers, game developers, ROCm contributors, and enterprise users all live under the same roof, contributing to the same reputation graph and centralized knowledge base.

Branding the experience

AMD came into the build with a vision already taking shape. 

"We knew exactly what to ask the Discourse team for."

The result is heavy brand customization: dark theme, AMD color palette, category color-coding, color-coded sidebar navigation, and custom animations. Most of it already existed in the theming layer, but where it didn't, the turnaround was short.

"The Discourse team would come back with actionable updates, either adjustments we could make directly in the theming layer or small implementation tweaks on their side, so we were able to refine the branding and navigation in short, focused cycles rather than through a long, one-off build."

Gamification: rewarding the right behaviors

AMD's gamification model, introduced through integration between AI Developer Program Portal and Discourse, maps points to the behaviors they most want to encourage: onboarding, continuous learning, and ongoing engagement.

Profile completion gets a fast early win because it's essential for building a real community and personalizing content. From there, points map to the things developers actually do at scale:

• 200 points for each AMD AI Academy course completed, with milestone bonuses for sustained learning (where most people earn points fastest)
• 250 points for each AMD AI event attended (DevDay, AAI, hackathons, ADP workshops), plus 100 points for each workshop
• 5 points per comment for community participation

Eligibility for tangible rewards is tied to total points earned across these programs.

"This feature is still in an early phase," the team notes. "We're actively testing different approaches to see what resonates most with developers. A big part of that is finding the right mix of rewards, ones that feel meaningful, motivating, and genuinely fun, so participating in our community is something people look forward to rather than just another box to check."

Group permissions out of the box

For gated content within the community, Discourse's native group permissions have done the work without any custom access control.

"Discourse's native group permissions have been a massive help here, as they're incredibly easy to set up and quick to get working. We definitely plan on using them more in the future as the program grows."

Discord and Discourse, side by side

AMD also runs a Discord server with 16,500+ members - recognizing that Discord and Discourse support different moments in a developer’s journey and work best in combination rather than as either/or choices.

"Discord is centered around fast-paced collaboration and troubleshooting, real-time feedback sharing, and instant engagement," the team explains. "Discourse enables deeper technical discussions, durable and searchable knowledge in a more structured and granular format."

The team has full autonomy over the content split. Discord is where developers show up with a problem and leave with an answer. Discourse is where that answer lives permanently - searchable, referenceable, and built on over time by the community itself. Together, the two platforms create a connected loop across the developer journey – from the moment a question surfaces to the point where the answer becomes part of a shared knowledge base.

From vendor to partner

The relationship with Discourse has grown alongside the forum – and today it looks less like a client-vendor dynamic and more like genuine co-development.

"Early on, the engagement looked more 'classic vendor': we came in with a clear set of requirements (branding, taxonomy, gamification, integrations) and leaned on Discourse mainly for implementation guidance and best practices."

That changed as AMD pushed into more advanced use cases: deep branding, custom gamification, integrations with AI Academy, ROCm content, and developer workflows. The complexity of what AMD was building demanded a different kind of collaboration – one where Discourse wasn’t just executing on briefs, but helping to shape them.

"We now involve them much earlier, at the idea and design stages, not just at implementation. That shift has made a real difference – we get better solutions because Discourse understands not just what we’re asking for, but why"

A specific example is the calendar feature. Calendars exist as a Discourse plugin, but AMD needed more than what came out of the box, including advanced date selection for events, custom event features, and a connection to the Developer Portal. The AMD team regularly reviews optimization opportunities and documented these requirements in the dedicated Meta space. Within a few days, the Discourse team came back with estimates and solution proposals – a turnaround that reflects how embedded the two teams have become.

"And of course we can't forget about Jennifer (Discourse staff), who joins us on a call every week to go through our needs and keep us updated on everything happening over at Discourse. That kind of continuity means we’re never starting from zero – she knows our platform, our goals and where we’re heading"

"Discourse is very much the connective tissue.”

ROCm documentation, GPUOpen content, the Developer Cloud, and the events program all live as separate properties. Discourse pulls them into one interactive space where developers can ask questions, share experience, and move between those touchpoints without feeling like they're jumping between separate properties.

"Out of the box we get a battle-tested discussion engine, and on top of that we can add everything that's uniquely AMD: brand customization and dark theme, AMD login, and the ability to link user contributions and points directly into our AI Developer Program Portal," the team explains.

"That combination of 'solid core + real extensibility' is very hard to replicate elsewhere at the same level of maturity.”

But the platform is ultimately a means to an end. What AMD is building toward is a developer community that doesn't just consume AMD technology - it grows with it. One where a developer working on their first ROCm project and a seasoned contributor pushing the boundaries of GPU compute are both finding value, both contributing, and both moving forward. The infrastructure makes that possible. The community makes it real.

“It means we can focus on designing the AMD developer journey instead of constantly reinventing basic community infrastructure."

That journey - not the tools behind it - is what AMD is most focused on building.