DataMindDesign SystemUI/UX & Design System DocumentationNavigation, conversation context and composing are separate responsibilities. The header identifies the conversation; it does not compete with it.
Ask a question, explore your schema, or turn an insight into a dashboard.
Four production states built from the same UI Kit components, spacing rules, and type hierarchy.
A composed question is ready to send without replacing the empty-state guidance too early.
Ask a question, explore your schema, or turn an insight into a dashboard.
The question is preserved while DataMind communicates progress in plain language.
Give me the number of users
Generated SQL is reviewable and remains explicitly read-only before execution.
Give me the number of users
Counts all records in the PEOPLE table, treating each record as a user.
SELECT COUNT(*) AS total_users
FROM people
LIMIT 5000;Review the generated query before execution.
Answer, visualization, data and SQL stay together with clear next actions.
Give me the number of users
Counts all records in the PEOPLE table, treating each record as a user.
A stable 256px navigation region, with history scroll and account actions pinned to the bottom.
Conversation title and source state are enough. Secondary controls belong in the composer or contextual menus.
The same component carries prompt, source, safety state and send action across empty and active chats.