Skip to main content

​
What onboarding does

When Aiola opens a new project for the first time, it asks for structured project context so the workspace starts with useful defaults instead of an empty shell.

​
Step 1: technical and style rules

The onboarding page collects setup information such as:
  • frontend stack
  • API style
  • CSS approach
  • UI libraries
  • animation tools
  • icon libraries
  • backend languages
  • runtime
  • services in use
  • design direction
  • backend notes
Aiola turns your selections into project rules. Expand Generated rules to preview and edit the UI/design and backend rules before saving them, or regenerate the draft from your selections. You can skip this step and continue to the project brief.

​
Step 2: project brief

The second step captures a freeform description of the app so Aiola has baseline product context for the workspace. You can skip the brief to finish onboarding without it. For a new project, enable Create the baseline app for me before submitting the brief if you want Aiola to open a setup thread and scaffold a starting app from your rules and brief.

​
Open an existing codebase

When a newly opened folder already contains code, choose I already have code. Aiola skips the manual onboarding form, creates an Analyze project thread, and opens the dashboard while the codebase analysis runs.

​
Analyze again later

Later, from the Info page, you can also ask Aiola to analyze the existing codebase and populate project context automatically.

​
When onboarding appears

Onboarding is triggered when a workspace has been created but setup has not been completed yet.