# Field alignment issues in LLM cost configuration in German

**URL:** https://meta.discourse.org/t/field-alignment-issues-in-llm-cost-configuration-in-german/396948
**Category:** UX
**Tags:** ai
**Created:** [February 24, 2026, 10:33pm UTC](https://meta.discourse.org/t/field-alignment-issues-in-llm-cost-configuration-in-german/396948 "2026-02-24T22:33:16Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![derek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/derek/32/458751_2.png) [@derek](https://meta.discourse.org/u/derek)
#### Post date: [March 2, 2026, 2:30pm UTC](https://meta.discourse.org/t/field-alignment-issues-in-llm-cost-configuration-in-german/396948/3 "2026-03-02T14:30:26Z")

</div>

> [@sam](#):
>
> Feels more natural cause 4 side by side just ends up leaving us with no space.

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.

 ![Screenshot 2026-03-02 at 7.21.50 AM](https://global.discourse-cdn.com/meta/original/4X/f/6/c/f6c6efb3f694fa6e4458fe45db32fed0e859c603.png)

 ![Screenshot 2026-03-02 at 7.21.31 AM](https://global.discourse-cdn.com/meta/original/4X/8/b/7/8b7e7f8a853899cda302cb5bdcfd3ca2b8d56e85.png)

[https://github.com/discourse/discourse/pull/38149](https://github.com/discourse/discourse/pull/38149)

---

_[View the full topic](https://meta.discourse.org/t/field-alignment-issues-in-llm-cost-configuration-in-german/396948)._