Skip to content

feat(studio): make migration home a single-column workspace - #1133

Merged
warm-wm merged 2 commits into
mainfrom
feat/studio-migration-home-layout
Sep 18, 2026
Merged

warm-wm merged 2 commits into
mainfrom
feat/studio-migration-home-layout

Conversation

@wujiaming-ai

Copy link
Copy Markdown
Collaborator

Replace the migration side navigation with one page-level top bar and a single-column body, so the home page is the upload entry followed by recent migrations and "已迁移项目" becomes a top-bar entry.

  • home: upload panel plus recent migrations (five by default, expandable in place, expired environments offered as view-only)
  • task view and saved-project library share the same top bar and never stop a running migration when navigating away
  • load capabilities and migration sessions independently so a session-list failure keeps the upload entry usable, with a retry on each failure path
  • keep the recent-migration action column wide enough for its labels and align the empty state with the section heading

Replace the migration side navigation with one page-level top bar and a
single-column body, so the home page is the upload entry followed by recent
migrations and "已迁移项目" becomes a top-bar entry.

- home: upload panel plus recent migrations (five by default, expandable in
  place, expired environments offered as view-only)
- task view and saved-project library share the same top bar and never stop a
  running migration when navigating away
- load capabilities and migration sessions independently so a session-list
  failure keeps the upload entry usable, with a retry on each failure path
- keep the recent-migration action column wide enough for its labels and align
  the empty state with the section heading
@wujiaming-ai
wujiaming-ai force-pushed the feat/studio-migration-home-layout branch from 7f69271 to 9530445 Compare September 18, 2026 06:51
The confirmation card stacked label-above controls in one full-width
column, so the Agent name input stretched across the whole card while the
two selects stayed 190px wide.

Lay each field out as a label/control row capped at 640px with a 112px
label column and a 512px control column, render the select labels outside
the control, and put the consent note and the primary action on one
footer row separated by a hairline. Narrow screens stack the label above
the control.
@warm-wm
warm-wm merged commit adcdfdc into main Sep 18, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants