Ecosystem

One #[derive(Facet)] describes your type once. Everything below reads that description to do something useful — serialize it, diff it, generate a schema, build a CLI, pretty-print it. You almost never depend on these crates directly: you derive Facet, add the crate that does the job, and call it.

This page is the map. Crate names link to docs.rs; the Source column points at the repository.

Looking for which standard/third-party Rust types already implement Facet (Uuid, DateTime, Utf8PathBuf, …)? That's the Type Support page.

Core & reflection

The foundation. facet is the one crate every user depends on; the rest is the machinery it re-exports.

Data formats

Serialize and deserialize derived types. Same type, any format — pick the crate, call to_string / from_str.

The XML family

XML uses a tree (DOM) architecture rather than streaming, so it lives in its own workspace alongside formats built on top of it.

Schema & code generation

Project your Rust types into other type systems — keep a frontend, an API contract, or another language in sync from one source of truth.

See the Schema codegen guide for a full-stack workflow.

Diagnostics & derive plugins

Day-to-day ergonomics: better output, better errors, less boilerplate.

Configuration & CLI

Web & UI

Building blocks

Lower-level pieces you'll meet when writing your own format crate or tooling.

Writing a new format crate? The Extend section walks through Peek, Partial, and the format-crate architecture.

Building something facet-adjacent? Open a PR against the website and we'll add it to the map.