Answers.Body: <p>Another idea (since that's what you asked for) might be to leverage Relationships more than Entry Types.</p>
  
  <p>I find that those administering the content have a better time with relationships than Entry Types.</p>
  
  <p>Given that your </p>
  
  <p>e.g. if Golf Pros' was a Structure (instead), which contained a <strong>required</strong> field called 'Related Location' your content admin person could logically click <strong>Entries</strong> > <strong>New Entry</strong> > <strong>Golf Pro</strong></p>
  
  <p>One area this could really help would be News. If a News article (Entry) contained the same 'Related Location' field, I think you'd have a better time templating and also provide a more logical publishing experience for your client.</p>
  
  <p>The same could apply to the other Entry Types you have beneath your Locations; About, How to find us, etc.</p>
  
  <p>As I said - it's only another approach - happy to discuss, Tom.</p>
  
  <p>Matt</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-21T16:53:51.557Z
Answers.Text: Hi Matt. Thanks for your thoughts. I like the idea of moving the relationship from the Location's Pro's page to the Pro's entry itself, much simpler as you suggest. What is the advantage of switching the Pro's Channel to a Structure though? Applying the same to the other Entry Types are you suggesting there would be an "About" Channel / Structure with multiple entries that are related to a Location? Thanks again!
Answers.UserDisplayName: Tom
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-23T16:58:14.537Z
Answers.Text: Hi Tom. No problem. I only suggested a Structure because the Section wouldn't need a dat/time stamp that a Channel would have. You could use either Channel or Structure. ... To your second question, yes an About Entry would be related to a Location. As I said, just an idea - I always try to consider the logic a content administrator will face when working in the CMS. Best.
Answers.UserDisplayName: Matt P
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-25T22:38:08.267Z
Answers.Text: Hi Matt. Sorry for the (really) delayed reply. I took this approach in the end and it worked out great. Thanks for your input. Marked your answer as correct.
Answers.UserDisplayName: Tom
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-21T15:57:25.330Z
Answers.LastActivityDate: 2017-02-21T15:57:25.330Z
Answers.UserDisplayName: Matt P
Body: <p>I'm proposing to use Craft for a company that runs multiple golf courses. Along with some general pages for the company as a whole, each location (course) is to have it's own microsite, for want of a better phrase. At the moment each location will have the same pages (but that could change in the future), along with a news section.</p>
  
  <p>I think I can achieve this with a combination of categories and structures, but I'd be keen to know if anyone has any other ideas. (Possibly "multisite" with locals?)</p>
  
  <p>My thoughts are:</p>
  
  <ul>
  <li>Homepage - Single</li>
  <li>Global About - Single</li>
  <li>Global Golf Pros - Channel</li>
  <li>Locations - Structure with individual entry types for each sub page</li>
  <li>Global Contact Us - Single</li>
  <li>News (there's no requirement for this to be global at the moment, but creating multiple news channels seems a little painful) - Channel (with category filed to scope to each location)</li>
  </ul>
  
  <p>Within the Location's channel I can then use relationships for each location's Golf Pros (from the Global Golf Pros channel) and list news articles via twig <code>craft.entries.section('news').categories('location-x')</code> and a slightly elongated Entry URL Format "locations/{location.first.slug}/news/{slug}"</p>
  
  <p>Sometimes a picture is worth a 1,000 words, so here goes.</p>
  
  <p><a href="https://i.sstatic.net/zRRnJ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/zRRnJ.png" alt="Sitemap"></a></p>
  
  <p>I feel a little like I'm mixing the use of categories and structures though.</p>
  
  <p>Any thought would be much appreciated!</p>
  
  <p>Thanks in advance,</p>
  
  <p>Tom</p>
  
Tags: <categories><structure><multi-site>
Title: Structure a site with multiple locations with categories, structure or "multisite"?
ThreadText: # Structure a site with multiple locations with categories, structure or "multisite"?
  
  (Asked by: username_0 on 2017-02-13)
  
  I'm proposing to use Craft for a company that runs multiple golf courses. Along with some general pages for the company as a whole, each location (course) is to have it's own microsite, for want of a better phrase. At the moment each location will have the same pages (but that could change in the future), along with a news section.
  
  I think I can achieve this with a combination of categories and structures, but I'd be keen to know if anyone has any other ideas. (Possibly "multisite" with locals?)
  
  My thoughts are:
  
  * Homepage - Single
  * Global About - Single
  * Global Golf Pros - Channel
  * Locations - Structure with individual entry types for each sub page
  * Global Contact Us - Single
  * News (there's no requirement for this to be global at the moment, but creating multiple news channels seems a little painful) - Channel (with category filed to scope to each location)
  
  Within the Location's channel I can then use relationships for each location's Golf Pros (from the Global Golf Pros channel) and list news articles via twig `craft.entries.section('news').categories('location-x')` and a slightly elongated Entry URL Format "locations/{location.first.slug}/news/{slug}"
  
  Sometimes a picture is worth a 1,000 words, so here goes.
  
  [![Sitemap](https://i.sstatic.net/zRRnJ.png)](https://i.sstatic.net/zRRnJ.png)
  
  I feel a little like I'm mixing the use of categories and structures though.
  
  Any thought would be much appreciated!
  
  Thanks in advance,
  
  Tom
  
  **Tags:** categories, structure, multi-site
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-02-21. Score: 1 | Accepted answer
  
  Another idea (since that's what you asked for) might be to leverage Relationships more than Entry Types.
  
  I find that those administering the content have a better time with relationships than Entry Types.
  
  Given that your
  
  e.g. if Golf Pros' was a Structure (instead), which contained a **required** field called 'Related Location' your content admin person could logically click **Entries** > **New Entry** > **Golf Pro**
  
  One area this could really help would be News. If a News article (Entry) contained the same 'Related Location' field, I think you'd have a better time templating and also provide a more logical publishing experience for your client.
  
  The same could apply to the other Entry Types you have beneath your Locations; About, How to find us, etc.
  
  As I said - it's only another approach - happy to discuss, Tom.
  
  username_1
  
  > **Comments:**
  > **username_0**: Hi username_1. Thanks for your thoughts. I like the idea of moving the relationship from the Location's Pro's page to the Pro's entry itself, much simpler as you suggest. What is the advantage of switching the Pro's Channel to a Structure though? Applying the same to the other Entry Types are you suggesting there would be an "About" Channel / Structure with multiple entries that are related to a Location? Thanks again!  
  > **username_1**: Hi Tom. No problem. I only suggested a Structure because the Section wouldn't need a dat/time stamp that a Channel would have. You could use either Channel or Structure. ... To your second question, yes an About Entry would be related to a Location. As I said, just an idea - I always try to consider the logic a content administrator will face when working in the CMS. Best.  
  > **username_0**: Hi username_1. Sorry for the (really) delayed reply. I took this approach in the end and it worked out great. Thanks for your input. Marked your answer as correct.  
  
  ---
  
  