Next steps

After your first admin screen works, choose the next docs section by the user workflow you are building.

If you need real data

Start with Query and Data Tables.

Use Query for the input contract: filters, sorting, pagination, schemas, and URL-backed state.

Use Data Tables for the table provider, columns, loading strategies, toolbar, and rendered table.

If users need actions

Start with Commands.

Use commands for row actions, toolbar actions, bulk actions, context menus, permissions, visibility, disabled state, and mutation side effects.

If users need faster editing

Start with Inline.

Use inline editing when users should update values inside detail pages or table cells without opening a full form.

If records need files

Start with Storage for attachments and uploaded assets. Start with Drive for folders, file managers, provider-backed trees, and file picker workflows.

If users need rich text

Start with Editor.

Use the editor package for rich-text fields and editor storage helpers.

If assistants need to act inside the app

Start with AI after your domain actions are clear.

AI works best when your app already has typed tools, commands, and workflows that an assistant can call safely.

Starter path recap

1. Create the app.
2. Confirm the root layout and admin layout.
3. Add one static admin page.
4. Add the page to the sidebar.
5. Add Query and Data Tables when the page needs real records.
6. Add Commands, Inline, Storage, Drive, Editor, or AI when the workflow needs them.

Keep going