Repository navigation
fix: lay out the Studio training setup as a grouped form - #44
Merged
Merged
Conversation
The two-column config grid was built for two controls and broke once base weights and the data list joined it. Group the controls, keep the launch button beside them, make the data list a scrollable aligned list, and stop long selects and paths from widening the page on narrow screens.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The training setup used a 2-column grid (
1.4fr 8rem) designed for two controls; base weights, the data list and notes were later added, so they landed in arbitrary cells and the panel collapsed. Batch IDs also wrapped to four lines.