Use the documentation and a minimal reproduction to identify whether a question concerns a component, the website, or application-owned behavior. Public contact details and support services are pending verification.

Find the relevant guidance

Start with FAQs for project boundaries, the component catalog for APIs and examples, and Patterns for composition guidance. Authentication, persistence, routing, and product account policies belong to the application using Liquidify.

The library and documentation website are separate projects. A component behavior issue belongs with the library implementation; an unclear article or broken documentation link belongs with the website content. Identify that distinction in the report.

Prepare a reproducible report

Include the following information:

• The task, expected outcome, and observed behavior.
• A minimal example using supported imports, props, and the aggregate stylesheet.
• The package artifacts or source revision, React version, browser, and operating system.
• Relevant theme, viewport, input method, and reproduction steps.
• The affected URL and heading for a documentation issue.

Remove credentials, private records, and unrelated application code. Use original sample content. A screenshot can clarify a visual issue, but include the steps and configuration needed to reproduce it.

For a problem involving sensitive information, prepare a redacted summary and wait for a verified private reporting channel before sharing details. The pending contact section below is not a reporting destination.

Contact channels pending

As checked on October 21, 2026, the configured public GitHub repository, Issues, and Discussions URLs returned unavailable responses. This does not establish whether access exists through an authorized account. No public email address, private reporting channel, response timetable, or paid support service has been verified for this documentation.

Contact instructions will be added when a project channel is confirmed. Existing links elsewhere on the site should not be interpreted as a support guarantee. Do not send a report to Apple or Carbon for a Liquidify implementation issue.

Contribute a correction

If you already have authorized source access, follow the contribution overview to prepare a focused change. Include the implementation or source evidence that resolves the issue. A prepared contribution does not imply a review deadline or acceptance policy.

Further reading

• Liquidify FAQs
• Contribution checklist
• Originality and attribution