githubEdit

Meeting Minutes

circle-info

Access recurring Meeting Notes here: Cardano DevEx Innvation WG Minutesarrow-up-right

Mar 4, 2026 | Cardano Developer Experience Innovation WG

Attendees:

Name

Attendance

Role/COI

Georg Link

Yes

OSC Chair

Terence ‘Tex’ McCutcheon

Yes

Lead/Secretary

Kyle Solomon

Yes

CPC Vice Chair

Bora Oben

Yes

Developer Advocate - CF

Dan Baruka

Yes

Developer Advocate Intersect

Emmanuel Titi

Yes

Developer Advocate Intersect

Harun Mwangi

Yes

Developer Advocate Intersect

Uche Obasi

Yes

Developer Advocate Intersect

Sebastian Pabon

Yes

OSC Member

Darlisa Consoni

Yes

Ecosystem Engineering - CF

Josefine Birkigt

Yes

Cardano Foundation

Robertino Martinez

Yes

Product Owner - DevEx IOG

Community/Other Attendees

  • Ahmed Kadiri

  • Ayomi Shuga

  • Darlington Wleh - LidoNation

  • Ian Njuguna

  • Luke Mahoney - MLabs

  • Samuel Leathers

  • Tevo Kask

Recording: Cardano Developer Experience Innovation WG - 2026/03/04 - Recordingarrow-up-right

Transcript: Cardano Developer Experience Innovation WG - 2026/03/04 - Transcriptarrow-up-right

Chat Transcript: DevEx Innovation WG Meeting – 2026/03/04 – Chat Transcriptarrow-up-right

Agenda 4.30.26

  • Brainstorm Problem Statements

  • Brainstorm Actions/Solutions

  • Determine single source of truth

Decisions/Actions

Decisions

  • Target Audience: The primary focus of this working group will be the developer experience, specifically developers building products and services on top of Cardano (Application Developers), and the related ‘developer journey’.

  • Single Source of Truth: The group reached a consensus to use developers.cardano.org as the primary entry point and unified knowledge base for the ecosystem. Pending external confirmation.

  • Timeline: The group committed to a fast-paced timeline of four to six weeks to implement definitive changes and improvements.

  • Communication Channel: The "Developer Advocate Water Cooler" channel in the Intersect Discord will be the central hub for ongoing communication to avoid thread fragmentation.

Actions

  • Resource Mapping: Participants are to copy viable solutions from the "Problem Statement" section of the Mural board over to the "Impact vs. Effort" matrix before the next meeting.

  • Documentation Proposal: Robertino will provide a written decision/proposal regarding the scope of documentation to allow for broader community feedback.

  • Portal Review: All members are expected to act as "users" of the Developer Portal over the next two weeks to provide front-level feedback on friction points.

  • GMC Coordination: Kyle to initiate a discussion (or involve a representative) with the Global Marketing Council regarding the implementation of retargeting tags and developer audience segmenting.

  • GitHub Engagement: Bora to monitor the developers.cardano.org repository for new issues or discussions tagged for the "Innovation Working Group."

  • Meeting Minutes Distribution: Terence to publish the meeting minutes on X (formerly Twitter) under the OSC (Open Source Committee) page.

  • Specialized Session: Bora and Terence to coordinate a dedicated sub-meeting specifically focused on the technical architecture and content migration for the Developer Portal.

Topic

Discussion

Notes

Introductions

Participants from Intersect, Cardano Foundation, and IOG introduced themselves, representing roles in Open Source, Product Management, and Developer Advocacy.

Focus is on bridging silos between founding organizations.

Target Audience

Debate occurred regarding whether to focus on "Application Developers" (building on Cardano) vs. "Core Contributors" (building the protocol).

Consensus: Primary focus is on developers building products/services on Cardano.

Documentation Gaps

Identification of a steep learning curve, unmaintained docs, and a lack of "one-click" installation tools for new developers.

Need for documentation that is "LLM-friendly" was highlighted by Robertino.

Resource Fragmentation

Multiple entry points exist (Cardano Developer Portal, Intersect DevX site, docs.cardano.org), causing confusion for new users.

Bora noted the "Developer Portal" has recently been refreshed to address this.

Single Source of Truth

Discussion on consolidating all resources into one primary domain to prevent "bouncing" and loss of developer interest.

Decision: Developers.cardano.org is the preferred primary entry point.

User Personas

Robertino suggested clear paths for different personas: Junior Devs, EVM developers migrating, and entrepreneurs.

Avoiding "noise" (like SPO info) for application developers is critical.

Developer Journey

Bora emphasized a "multi-level failover" approach: capturing attention immediately and redirecting based on intent (SDKs vs. Events).

The goal is a seamless flow from "zero to job-ready."

Tooling & Libraries

Discussion on the lack of standard libraries (e.g., CBOR serialization) and inconsistent documentation for various SDKs.

Proposal to keep high-level concepts in the central portal and deep technical specs in tool-specific repos.

Retargeting & Marketing

Kyle suggested using tracking tags and "audience buckets" to run retargeting campaigns for developers who visit the site but don't convert.

This requires coordination with the GMC (Global Marketing Council).

Incentive Mechanisms

Discussion on how to keep open-source contributors motivated to update documentation without a paid model.

Being featured on the main Developer Portal acts as a "marketing incentive" for tool builders.

Impact vs. Effort Matrix

Terence introduced a framework to prioritize solutions based on their implementation difficulty versus their benefit to the ecosystem.

High-impact, low-effort tasks will be prioritized for the next 4–6 weeks.

KPIs for Success

Bora and Sebastian debated metrics: Quantity of developers (Hackathons) vs. Quality/Retention (developers in full-time Cardano jobs).

North Star: Increasing the number of productive, long-term contributors and builders.

Next Steps

The Mural board remains open for participants to copy solutions into the "Priority/Effort" box.

A follow-up call specifically for the Developer Portal will be scheduled.

Last updated