# Container Width/Height Labels

**URL:** <https://forums.realmacsoftware.com/t/container-width-height-labels/46795>\
**Category:** RapidWeaver Elements\
**Created:** [March 19, 2025, 11:02pm UTC](https://forums.realmacsoftware.com/t/container-width-height-labels/46795 "2025-03-19T23:02:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bill](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/bill/32/107_2.png) [@Bill](https://forums.realmacsoftware.com/u/Bill)\
**Post date:** [March 19, 2025, 11:02pm UTC](https://forums.realmacsoftware.com/t/container-width-height-labels/46795/1 "2025-03-19T23:02:32Z")

</div>

@dan  
I was looking at the container width/height labels in Content Layout and those are not user-friendly.

 ![container_wd_ht_labels](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/3/0/30403f263bc870995281dfdcdc8ab242684be941.png)

May I suggest:  
Full to **Fill Parent Width**  
Screen to **Fill Device Width**  
Breakpoint to **‘Wd’ or ‘Ht’ at Breakpoint Sizing**  
Theme Spacing - I’m assuming it’s set in theme, but containers will probably be set at different sizes based on users needs and won’t need a general size so why not eliminate this and just use Wd/Ht at Breakpoint Sizing?

And in Sizing same changes and Theme Spacing to **Custom**

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [March 20, 2025, 10:29am UTC](https://forums.realmacsoftware.com/t/container-width-height-labels/46795/2 "2025-03-20T10:29:12Z")

</div>

> [@Bill](#):
>
> Full to **Fill Parent Width**  
> Screen to **Fill Device Width**

We’re using Tailwind’s syntax here, this makes it easier to understand and work with, especially if you’re already familiar with Tailwind. Instead of creating custom abstractions, which could add unnecessary complexity, we’re sticking with Tailwind’s conventions.

> [@Bill](#):
>
> And in Sizing same changes and Theme Spacing to **Custom**

Those values are based on the ones you setup or configure in the Theme Studio.

By keeping things close to Tailwind’s native syntax, we ensure better consistency, maintainability, and flexibility when styling layouts. Hope that helps! 😊