---
id: pj-onori
kind: person
title: "PJ Onori"
role: "Design systems practitioner"
org_label: "Sanity"
confidence: "sourced"
atlas_url: https://designsystems.fly.dev/nodes/pj-onori.md
---

# PJ Onori

Maintains Design System Doc Spec, whose 0.20.0 release rewrote the format around YAML entries, audience-aware sections, external source references and an executable conformance suite. Also proposed the W3C Design System Documentation Community Group and co-hosts Design System Office Hours.

## Links

- blog: https://pjonori.blog/
- linkedin: https://www.linkedin.com/in/pjonori/
- dsds: https://designsystemdocspec.org/
- repo: https://github.com/somerandomdude/design-system-documentation-schema
- proposal: https://www.w3.org/community/designsystemdocs/

## Edges

- authored -> Design System Doc Spec 0.20.0, Design System Documentation Community Group (proposed), Design system documentation is essential–as long as it’s good, I’m making a spec for design system documentation
- focus -> Adoption and mandate, Agentic governance, Compiled, not written, context, Component contracts, Deterministic spec extraction, Documentation schema, Validation loops
- works_at -> Sanity

## Sources

- https://designsystemdocspec.org/
- https://github.com/somerandomdude/design-system-documentation-schema/blob/main/CHANGELOG
- https://www.w3.org/community/blog/2026/07/30/proposed-group-design-system-documentation-community-group/