Provide relevant assistance and recovery paths without making people abandon their task.
Help should address the task a person is trying to complete. Start with the information or recovery action needed in the current context, then provide a route to more detailed guidance when necessary.
| Need | Starting point |
|---|---|
| A field requirement | Persistent text beside the field, associated with it programmatically |
| A short optional explanation | Inline text or a deliberately labelled Popover trigger |
| A failed operation | A nearby explanation and recovery action; see Notifications |
| A multistep task | A linked guide or tutorial with a route back to the work |
Keep information required to complete a task visible. Do not put an essential field requirement only in a hover tooltip. Optional explanations should be reachable by keyboard and touch, with a clear accessible name.
Figure in preparation
Required instructions and optional help
Compare a persistent field instruction with an optional explanation opened from a labelled help control.
Name the affected task and say what the person can do. For example, “The workspace could not be created. Your name is still entered. Try again.” is useful only when the application actually preserves that input and supports retry.
Use the same terminology as the interface. Keep raw diagnostic details separate from the explanation, and offer a reference identifier only if the product provides a way to use it. Do not claim that an error was reported automatically unless a reporting service confirms that behavior.
Let people dismiss optional help and find it again. Liquidify Popover is nonmodal: the page remains interactive, and Escape, an outside pointer interaction, or focus leaving the panel can dismiss it. It does not implement a tutorial system, determine tip eligibility, or remember which guidance someone has read. The application owns those decisions.
When help opens another route, preserve the task state where the product supports it and provide a clear way back. Test keyboard focus and dismissal in the actual composition. A tooltip or popover should not become the only way to reach a longer procedure.
Your application needs its own verified support destination and service policy. Those details remain product-specific. For a Liquidify implementation question, use FAQs and Contact us to understand the available evidence and pending contact channels.
Provide a minimal reproduction when reporting a library defect. Include expected behavior, actual behavior, source revision, and the relevant browser and component configuration. Keep credentials and private records out of examples.