Starter path vs advanced path

Choose the right route through the docs depending on whether you are building your first Tulip screen or composing deeper package behavior.

Tulip should be easy to start and deep enough for heavy users.

Use the starter path when you need momentum. Use the advanced path when you need to understand boundaries, customize behavior, or compose multiple packages into a larger product system.

Starter path

Follow this path when you are new to Tulip or starting a fresh app.

Create a new app with create-tulip-app.
Read Core to understand the app foundation.
Use UI for the base component language.
Build a data screen with Query and Data Tables.
Add row or toolbar actions with Commands.
Add inline updates with Inline when users should edit without opening a form.
Add uploads with Storage or a file manager with Drive.
Add AI after your domain workflows are clear enough to expose as tools.

Recommended first docs:

Quick Start

Create a new app

Package Layers

UI

Advanced path

Follow this path when you already know what you are building and need the deeper package model.

Start with the package overview page to understand responsibilities and entry points.
Read the concepts pages before copying recipes.
Use recipes for complete product patterns.
Use reference pages for exports, types, and gotchas.
Check package boundaries before moving logic across modules.

Advanced users usually move by surface:

Tables and filters: Query plus Data Tables.
Menus and actions: Commands.
Local-first screens: Core Local, Query, and table strategies.
Files and documents: Storage, Drive, and provider-specific docs.
Assistants and tools: AI concepts, recipes, and reference.

How to choose

Situation	Path
You are evaluating Tulip	Read Introduction, then skim the package map.
You need a working app quickly	Use Create App, then Core and UI.
You are building a list/detail admin module	Use Query, Data Tables, Commands, and Inline.
You need uploads or attachments	Use Storage.
You need folders, file selection, or provider-backed documents	Use Drive.
You need AI agents that can act inside the app	Use AI after your commands and domain tools are clear.

Rule of thumb

Start with the smallest package set that matches the user workflow. Add deeper packages when the workflow needs them.

Tulip works best when each package keeps its responsibility clear and the application composes those pieces near the screen, route, or provider that uses them.