Danny Salman

Content and knowledge architecture as quality infrastructure

In platforms where contributor output is the product, documentation and structured content are part of the quality mechanism. How clear the specs and guides are determines whether contributors can meet standards; how the knowledge layer is organized determines whether capabilities stay consistent and discoverable. I treat content and knowledge architecture as core infrastructure: specs, API references, developer guides, and machine-readable metadata, so that experience design and the knowledge layer work as one discipline.

Verification designed as progression

Quality-dependent platforms require friction that contributors willingly engage with. Reputation tiers, validation requirements, and staking commitments can function as compliance gates or as a skill ladder where increased access and responsibility follow from demonstrated capability. I design these systems so that moving through quality requirements mirrors the experience of developing expertise, with each stage unlocking meaningful new access as a natural consequence of getting better at the work.

Multi-audience ecosystem design

The platforms I work on serve contributors performing tasks, engineers integrating APIs, validators reviewing output, and enterprise teams configuring workflows, each with fundamentally different needs from the same underlying infrastructure. I design experience architectures where these audiences share a coherent platform language while encountering surfaces purpose-built for how they actually work, treating the ecosystem itself as the unit of design rather than any single product within it.