Building complex layouts often results in nested structures – div inside div, group inside group, etc.
CardContainer
, HeaderWrapper
). A long chain of unnamed “Frame 23 > Frame 24 > Frame 25” is confusing. By naming, you (and your devs) can understand the purpose of each container. Remember, these names can also reflect in code (as classnames or even component names if they become one).overflow: hidden
or a fixed size) that hinders your layout. Through the inspector, you can identify which element in the nest is causing the issue. Then you know exactly which layer in Shaper to adjust.