<p>I would make this decision based on what makes the most sense for the client. You can realize both solutions on a technical level, so it's really just a question about the preferable CP user experience.</p>

<p>For me this sounds like "Big News" and "Small News" are quite similar, so I'd probably like to have them combined in a single channel. And your template conditional is a good way to handle the manually (accidential?) typed in URLs.</p>

<p>You could even add a dedicated source for the entry index views by making use of the <code>modifyEntrySources</code> hook and some lines of custom plugin code. See this Stack Exchange Q&amp;A for how to do this: <a href="https://craftcms.stackexchange.com/q/11791/125">Filter entries by entry type in the CP?</a></p>

CC BY-SA 3.0
2016-02-03T10:40:48.100Z
Thanks. I'll go with the 404 conditional then. I prefer a simple and easy CP for my clients.
KSPR
CC BY-SA 3.0
2016-02-03T09:49:46.943Z
2016-02-03T09:49:46.943Z
2017-04-13T12:51:00.253Z
carlcs
<p>Example: I have content which could be separated into <code>Big News</code> and <code>Small News</code>.</p>

<p>The Big News has much text (which would need a link to its own entry). The Small News has only one text block (so it wouldn't need a separate page for each news).</p>

<p>Whats the best way of handling this? Two separate channels?</p>

<p>One channel with two entry types and a template with a conditional:</p>

<p><code>{% if entry.type == 'SmallNews' %}{% exit 404 %}{% endif %}</code></p>

<p>How do you handle this? I guess it is not possible to add <code>These entries have their own URLs</code> based on entry types, right?</p>

<url><entry-type><channels>
Channel with URLs based on entry type
# Channel with URLs based on entry type

(Asked by: username_0 on 2016-02-03)

Example: I have content which could be separated into `Big News` and `Small News`.

The Big News has much text (which would need a link to its own entry). The Small News has only one text block (so it wouldn't need a separate page for each news).

Whats the best way of handling this? Two separate channels?

One channel with two entry types and a template with a conditional:

`{% if entry.type == 'SmallNews' %}{% exit 404 %}{% endif %}`

How do you handle this? I guess it is not possible to add `These entries have their own URLs` based on entry types, right?

**Tags:** url, entry-type, channels

---

## 1 answers

### Answer by username_1 on 2016-02-03. Score: 2 | Accepted answer

I would make this decision based on what makes the most sense for the client. You can realize both solutions on a technical level, so it's really just a question about the preferable CP user experience.

For me this sounds like "Big News" and "Small News" are quite similar, so I'd probably like to have them combined in a single channel. And your template conditional is a good way to handle the manually (accidential?) typed in URLs.

You could even add a dedicated source for the entry index views by making use of the `modifyEntrySources` hook and some lines of custom plugin code. See this Stack Exchange Q&A for how to do this: [Filter entries by entry type in the CP?](https://craftcms.stackexchange.com/q/11791/125)

> **Comments:**
> **username_0**: Thanks. I'll go with the 404 conditional then. I prefer a simple and easy CP for my clients.  

---

