Find the reference that answers your next implementation question.
Use a reference for a specific question: an API shape, a state contract, a layout decision, or a source workflow. Confirm the implementation revision before copying a command or example.
| Question | Start here |
|---|---|
| Can I install and run the current library? | Developing overview |
| Which package owns an API? | Liquidify Core |
| How do I build one working interaction? | React tutorial |
| Which props and examples are available? | Component catalog |
| Who owns a control's value? | Controlled state |
| How do I configure the appearance? | Theming and Color |
| How do I investigate a regression? | Enhancing components |
The framework setup pages linked from Developing overview remain useful for integration boundaries. Their registry install commands depend on a usable release, which has not been verified for this pass.
When a description and a control disagree, inspect its installed declaration for the API, its runtime for behavior, and its stylesheet for presentation. Compare upstream source only after identifying the installed code. Record a minimal reproduction with the source revision, browser, props, and expected result.
Apple documentation explains design concepts and native behavior. It does not establish React props or browser behavior. The SwiftUI guide explains that distinction.
The website has a local read-only MCP handler; its integration documentation distinguishes that code from unverified deployment and client setup. A Web Components package and downloadable design kit remain unverified. Use the catalog and repository directly while those resources are pending.
README.md, package manifests, component source, and stories.