title: How to structure nested router-outlets and style their components to make them appear in columns next to each other in Angular?
body: <p><strong>WHAT I AIM TO ACHIEVE:</strong></p>
  <p>I want to make a Single Page Application with three columns on one page. Each column is a component and should show data according to the URL (dynamic parameters). The relation between the data is hierarchical from left to right. So if the user clicks on an item of the left column, the data in the other columns has to change accordingly. The selection should be reflected in the ULR so a user can save a specific selection or send it to others. Here a quick Design to make this easier to understand:</p>
  <p><a href="https://i.stack.imgur.com/DzfRD.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/DzfRD.png" alt="enter image description here" /></a></p>
  <p><strong>PROBLEM</strong></p>
  <p>I struggle with structuring the app/template to make this work. In this StackBlitz I tried nesting the router-outlets, but I cannot style the cards properly. <a href="https://stackblitz.com/edit/angular-ivy-uh3636?file=src%2Fapp%2Flayout%2Fget-data.service.ts,src%2Fapp%2Flayout%2Flayout.component.css" rel="nofollow noreferrer">https://stackblitz.com/edit/angular-ivy-uh3636?file=src%2Fapp%2Flayout%2Fget-data.service.ts,src%2Fapp%2Flayout%2Flayout.component.css</a></p>
  <p>The result looks like this when everything is selected:
  <a href="https://i.stack.imgur.com/MriDu.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/MriDu.png" alt="enter image description here" /></a></p>
  <p>&quot;Children of selected thing&quot; should be in the middle and &quot;Detail of selected child&quot; should be on the right. When nothing is selected yet, one can see the alternative text of the second column, but without styles of the card. The third column is invisible at all until and item of the second column is selected.</p>
  <p>Also when I select a new item in the first column, the second column does not react to the changed URL parameter, but the third does.</p>
  <p>As an alternative approach, I already tried to use named router-outlets on one layout component. Although the styling worked better with this approach, I faced other and more severe problems, e.g. navigation.</p>
  <p>I would appreciate any help or tips on this.</p>