Help people identify relevant capabilities and find a clear route to their first task.
Discovery helps people decide whether a capability is relevant and where to begin. Describe an available task in language people recognize, then provide a destination that continues the same promise.
Lead with what people can accomplish. For example, “Save a filter for later” is more useful than an unexplained feature name. Include prerequisites when they affect the decision to continue, such as access to a particular workspace or an existing collection of records.
Use examples that reflect the current implementation. Identify a preview or planned capability explicitly. A screenshot or reserved documentation route does not establish that a service is available.
Use descriptive links for destinations and buttons for actions in the current interface. Liquidify Link with an href renders navigation; without an href, it can render an action control. Supply a real destination when the intent is navigation.
Group related destinations under headings that explain their purpose. Keep names consistent between navigation, page titles, and the task itself. For large collections, use Search guidance to plan findability; the application owns indexing and results.
A destination should show the task named by its entry point. If a prerequisite blocks progress, explain what is missing and provide an appropriate next step. Avoid replacing a specific destination with a generic welcome screen.
Support entry through a direct URL as well as the main navigation. Application routing owns the destination and any return path after sign-in. Do not infer a router or access-control service from Link's appearance.
Check that people can identify the destination from its label, reach it by keyboard, and understand the page without remembering an earlier screen. Keep essential instructions visible at narrow widths. Use Learn when the task needs explanation and Try when a safe example makes it easier to evaluate.