Answers.Body: <p>There is probably no best answer. There are a number of ways to structure craft to support this, and any answer is going to be highly subjective. A lot will depend on the relationships between the elements, and what the requirements of the different elements are (i.e. how complex, etc).</p>
  
  <p>One option to get the desired uri pattern (i.e. <code>/sermons/series-name/sermon-name</code>) would be to do something like this:</p>
  
  <ul>
  <li>Create a single called <code>sermons</code> that would be the landing page for the sermons section.</li>
  <li>In the <code>sermons</code> template you would display the sermons overview content, and retrieve and display the 'series' (perhaps ordered by date, or category, or whatever).</li>
  <li>Create a structure to house 'series', with at least 2 levels, with the series collection at the root and the individual series items (a.k.a. sermons), beneath. The series collection and series items would each have a different <code>Entry Type</code> so that fields could be unique for collection vs. items, and you can display a different template depending on the Entry Type.</li>
  <li>Set the uri for the 'series' structure to be 'sermons/{slug}' and for nested entries to be <code>{parent.uri}/{slug}</code>.</li>
  <li>You could also create additional levels for video, artwork, etc. which would get added to the uri automatically (where each level or type of content might get assigned its own Entry Type based on the type of content your working with) (i.e. <code>/sermons/series-name/sermon-name/videos/video-name</code>).</li>
  </ul>
  
  <p>There are lots of other options and considerations also, but this might be an easier one to deal with, without having to create your own custom routes to get the uri pattern you are looking for.</p>
  
  <p>This assumes of course that an individual series item (or sermon) belongs to only one series. If not, then you may want to consider other options, such as creating a channel for 'series' and a channel for 'sermons' and then relate the two using an <code>entries</code> FieldType.</p>
  
  <p>You can even take the structure concept further and map the whole site using a single structure, with different entry types for the different types of pages. This makes the nav very easy to build and the sections/pages can all be moved around easily. And you can always pull in other content into those pages from other channels as needed. OR create a structure for the rest of the site and structure for the series, where the uri's match up nicely.</p>
  
  <p>Basically. Lot's of options.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-28T01:18:41.930Z
Answers.Text: Even though there seems to be a lot of different options, this really gives me a lot to go on. I just had no idea where to start. I'm going to look into building a structure for them and see where that takes me. Thank you for the response!
Answers.UserDisplayName: misteroptimist
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-28T08:35:51.577Z
Answers.Text: Douglas, I think you're wrong. There's one best answer and it's the one you gave here! It covers all relevant options and you explain them so good. :)
Answers.UserDisplayName: carlcs
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-28T00:13:33.120Z
Answers.LastActivityDate: 2014-10-28T00:13:33.120Z
Answers.UserDisplayName: Douglas McDonald
Body: <p>I'm currently working on a website for a church and I thought that Craft would be perfect for the project and a great way to learn it. However, I'm having a hard time wrapping my head around how to structurally build sermons into a craft cms site. </p>
  
  <p>I want it to look something like this.</p>
  
  <p>Sermons > Series > Series Title, Series Artwork, Series Bio, Message Title, Date, short Bio, artwork, links to watch, links to listen, social links, </p>
  
  <p>Similar to this website. <a href="https://newspring.cc/sermons" rel="nofollow">https://newspring.cc/sermons</a></p>
  
  <p>Could anyone provide any insight into what ways they'd build this? I guess I'm getting hung up on if I have to create 2 channels to make this work? One for Sermons, and one for each series?</p>
  
  <p>Edit: I want to be able to add a sermon series as and entry. And then go in and add each week's message as a separate entry under that particular sermon series. Does that make sense?</p>
  
Tags: <structure><channels>
Title: Help with understanding how to structurally build a sermon catalogue
ThreadText: # Help with understanding how to structurally build a sermon catalogue
  
  (Asked by: username_0 on 2014-10-27)
  
  I'm currently working on a website for a church and I thought that Craft would be perfect for the project and a great way to learn it. However, I'm having a hard time wrapping my head around how to structurally build sermons into a craft cms site.
  
  I want it to look something like this.
  
  Sermons > Series > Series Title, Series Artwork, Series Bio, Message Title, Date, short Bio, artwork, links to watch, links to listen, social links,
  
  Similar to this website. <https://newspring.cc/sermons>
  
  Could anyone provide any insight into what ways they'd build this? I guess I'm getting hung up on if I have to create 2 channels to make this work? One for Sermons, and one for each series?
  
  Edit: I want to be able to add a sermon series as and entry. And then go in and add each week's message as a separate entry under that particular sermon series. Does that make sense?
  
  **Tags:** structure, channels
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-10-28. Score: 7
  
  There is probably no best answer. There are a number of ways to structure craft to support this, and any answer is going to be highly subjective. A lot will depend on the relationships between the elements, and what the requirements of the different elements are (i.e. how complex, etc).
  
  One option to get the desired uri pattern (i.e. `/sermons/series-name/sermon-name`) would be to do something like this:
  
  * Create a single called `sermons` that would be the landing page for the sermons section.
  * In the `sermons` template you would display the sermons overview content, and retrieve and display the 'series' (perhaps ordered by date, or category, or whatever).
  * Create a structure to house 'series', with at least 2 levels, with the series collection at the root and the individual series items (a.k.a. sermons), beneath. The series collection and series items would each have a different `Entry Type` so that fields could be unique for collection vs. items, and you can display a different template depending on the Entry Type.
  * Set the uri for the 'series' structure to be 'sermons/{slug}' and for nested entries to be `{parent.uri}/{slug}`.
  * You could also create additional levels for video, artwork, etc. which would get added to the uri automatically (where each level or type of content might get assigned its own Entry Type based on the type of content your working with) (i.e. `/sermons/series-name/sermon-name/videos/video-name`).
  
  There are lots of other options and considerations also, but this might be an easier one to deal with, without having to create your own custom routes to get the uri pattern you are looking for.
  
  This assumes of course that an individual series item (or sermon) belongs to only one series. If not, then you may want to consider other options, such as creating a channel for 'series' and a channel for 'sermons' and then relate the two using an `entries` FieldType.
  
  You can even take the structure concept further and map the whole site using a single structure, with different entry types for the different types of pages. This makes the nav very easy to build and the sections/pages can all be moved around easily. And you can always pull in other content into those pages from other channels as needed. OR create a structure for the rest of the site and structure for the series, where the uri's match up nicely.
  
  Basically. Lot's of options.
  
  > **Comments:**
  > **username_0**: Even though there seems to be a lot of different options, this really gives me a lot to go on. I just had no idea where to start. I'm going to look into building a structure for them and see where that takes me. Thank you for the response!  
  > **username_2**: username_1, I think you're wrong. There's one best answer and it's the one you gave here! It covers all relevant options and you explain them so good. :)  
  
  ---
  
  