I've got a single structure menu for my entire site which consists of a title and a single related entry. I use that to output the main menu, which uses this code:
<section class="top-bar-section">
<ul class="right">
{% nav link in craft.entries.section('menu') %}
<li class="...
Why don't use use the structure for the content also? I don't see the benefits of using a bunch of singles and then have to manage the structure of them in a separate structure section using entries fields.
with "top level pages" you meant the singles, related to a top level entry from your structure, right?
Practically every page on the site has a different layout - and as far as I can tell it's not possible to set different templates for entries in a Structure channel
It looks like Structure is designed to handle "sections" of content, like in the example, it doesn't seem appropriate to use one structure channel for the whole site
Yes, fine. I am also still on my first site using this approach. But I think it's very nice to have it all in one place. The content and the structure of it.
If the {% nav %} tag doesn't give you enough control over the output, you can always replicate the behavior with custom loops and the getChildren() method. Just nest them as far as your navigation hierarchy possibly gets.
Edit:
Here an example code on how you'd dynamically call getChildren() on...
The question is not very good (as far as I remember), but I listed links to some other Q/As on that topic.
If the {% nav %} tag doesn't give you enough control over the output, you can always replicate the behavior with custom loops and the getChildren() method. Just nest them as far as your navigation hierarchy possibly gets.
Edit:
Here an example code on how you'd dynamically call getChildren() on...
Discussion between codeknight and carlcs
Discussion between codeknight and carlcs