This is actually two components in one: a container and a split-view. Both are independent components, but they can be applied to the same element without issues. In plain HTML you'd do this:
<section class="l-container--fixed-200 l-container--pad-i l-container--pad-b c-split-view">.Expressing this kind of composition with components is impossible or very clunky (as can be seen here). That's how we get a lot of subpar markup on web apps. And Tailwind makes this problem even worse because it actively uses this architecture to achieve reusability and composition. Look at any Tailwind website and you will see a lot of nested tags that wouldn't even need to be nested since their styles wouldn't clash. This is why.
