title: Best practice for specifying the routing in a big application
body: <p>I am very new to Giraffe.</p>
  
  <p>Assuming we have a big app with lots modules and pages (i.e. tens of web pages and hundreds or thousands of web api actions), what is the best way to specify the routing without creating a mess?</p>
  
  <p>As an example, we have these business modules (let's say we can map them to subfolders with the same names):</p>
  
  <ul>
  <li>HR
  
  <ul>
  <li>Employees
  
  <ul>
  <li>Display Page</li>
  <li>CRUD actions:
  
  <ul>
  <li>Add Employee</li>
  <li>Update</li>
  <li>Remove</li>
  </ul></li>
  <li>Get reference data actions</li>
  </ul></li>
  <li>Postings
  ...</li>
  </ul></li>
  <li>Payroll
  ...</li>
  <li>Admin
  ...</li>
  </ul>
  
  <p>The routing examples here are minimalistic: <a href="https://github.com/giraffe-fsharp/Giraffe/blob/master/DOCUMENTATION.md#routing" rel="nofollow noreferrer">https://github.com/giraffe-fsharp/Giraffe/blob/master/DOCUMENTATION.md#routing</a>. Usually, applications can have big routing tables. I assume that we will have to have a subroute for each module.</p>
  
  <p>Thanks</p>