title: Route and view naming conventions
body: <p>I am looking for some input regarding the naming conventions I use for route names and view directory structures. </p>
  
  <p>Say I have the following routes:</p>
  
  <pre><code>Route::get('/teams/choose', 'ChooseTeamController@index')-&gt;name('teams.choose.index');
  
  Route::post('/teams/choose', 'ChooseTeamController@choose')-&gt;name('teams.choose');
  
  Route::get('/teams/{team}/manage', 'ManageTeamController@index')-&gt;name('teams.team.manage.index');
  </code></pre>
  
  <p>For the <code>get</code> routes, I would nornally put the views in a directory structure matching the route name. E.g. <code>resources/views/teams/team/manage/index.blade.php</code>. However, I feel that this is way too verbose. </p>
  
  <p>I feel that it would be confusing all round (to myself and other developers) if I was to use a view directory structure like so, rather than the last example: <code>resources/views/team/manage/index.blade.php</code>- the plural of <code>team</code> is not used, so when I have other views, like so (using the original examples convention): <code>resources/views/teams/choose.index</code> they dont visually have the relationship intended. I.e. they have a differing 'root' directory- <code>teams</code> vs <code>team</code>.</p>
  
  <p>Any input or advice would be appreciated. </p>