title: How to handle generic routes in Angular?
body: <p>I use <a href="https://angular.io/" rel="nofollow noreferrer">Angular</a> <code>9.17</code> and have a conceptual question.</p>
  
  <p>I have implemented a login mechanism which can now be enabled for certain routes. The "home/start" page can of course be viewed logged in or logged out.</p>
  
  <p>But depending on this, the view looks a lot different. So my question is, should i have two different components reflecting these views, or one and disabling/enabling certain elements depending on the signing-in status?</p>
  
  <p>Are both approaches valid or is one of them an anti-pattern?</p>