I realized that the user can use the link field to link to individual entries but not to entire sections. But that's a feature that I need. That made me realize that in my templates I also link to a section's index page statically like <a href="/blog">Blog</a> because I don't know of a more programmatic way to do so. That made me think...

What if sections (or basically channels and structures) had an index URL and index template just like they do have an entry URL and entry template? That would give us multiple benefits:

1. You can link to entire channel index pages with the link field.
2. You can get a channels index page URL programmatically in your templates like this: {{ section.url }}.
3. The index templates could receive a section variable just like entry templates receive an entry variable. It would make accessing a sections URL, name, entries, and other things a bit easier. I don't know, would craft\models\Section be a suitable type for this? It would need a new property or function to access the new URL. And is there currently a way to query a section object itself? I know of {{ craft.entries().section(name) }}, but that doesn't work here because it just returns a list of entries. Instead there should be something like {{ craft.section(name) }}, unless there's already an API that I don't know yet.
4. That section variable from point 3 could have a cpEditUrl variable. Now, sections already have such a variable but they link to the settings page that's meant to be used by admins (Settings > Sections > Some Section), while entries have the same variable which links to the edit page that's meant to be used by editors (Entries > Some Section > Some Entry). I currently need to manually construct the URL that leads to the section edit page for editors (Entries > Some Section) like this: '/admin/entries/' ~ currentSection.handle ~ '?source=section%3A' ~ currentSection.uid, all while using custom Twig functions to actually get the currentSection variable.

In general, this would reduce some repetition in your templates when it comes to a section itself which also reduces the amount of work in a refactoring. E.g.: {{ craft.entries().section('blog').all() }} would become {{ craft.entries().section(section).all() }} (EDIT: or maybe even {{ section.entries().all() }}).

EDIT:

• Add 4th benefit