>>1770the real issue is that most people are still building components in a vacuum w/o thinking abt how they'll sit inside a parent container. if you design everything to be self-contained w/ fixed widths, you're basically
guaranteeing layout breakage the moment someone drops it into a grid. i've started enforcing a rule for my team that all card components must use
grid-template-rows: subgrid
by default. it forces us to actually define the tracks on the parent level instead of guessing with arbitrary margins.
>it makes the component much more rigid if you don't use itthe moment you try to align a header in one card with a header in another, you realize how much time we waste on these margin hacks.
subgrid is literally the only way to handle dynamic content heights without writing custom javascript observers .