derek
March 2, 2026, 2:30pm
3
Totally agree that 4 inputs is too tight.
One option that might read more clearly is a 2x2 grouping. Move I/O costs to the first row, with caching costs grouped together on the second.
On mobile we can stack everything into a single column and group them once there’s enough space. It won’t be perfect for every translation, but it should give the layout more breathing room.
main ← ux-llm-config-input-styles
merged 04:44PM - 02 Mar 26 UTC
This PR tidies up AI LLM config inputs to give longer translated labels more roo… m and reduce spacing issues.
- On mobile each input is shown on its own line
- On larger screens inputs are grouped into a 2x2 layout
<img width="386" height="633" alt="Screenshot 2026-03-02 at 7 21 50 AM" src="https://github.com/user-attachments/assets/240e8b88-691b-45f8-b440-886575bebffc" />
<img width="1036" height="691" alt="Screenshot 2026-03-02 at 7 21 31 AM" src="https://github.com/user-attachments/assets/935f2e53-0827-4e83-9ae8-c1bf5160b65c" />
### Before
<img width="826" height="121" alt="image (9)" src="https://github.com/user-attachments/assets/57fdd468-a6ab-4ffc-9a34-66ef1d8f01e3" />
<img width="1123" height="121" alt="image (10)" src="https://github.com/user-attachments/assets/e808733b-205d-430e-b5ce-4377fcff9ba9" />
https://meta.discourse.org/t/field-alignment-issues-in-llm-cost-configuration-in-german/396948
3 Likes
