My navigation looks like the following.
About
- History
- Goals
- Sponsors
Our Work
- International
- Books
- Children
- Animals
- Earth
- Social
- Sport
I’m using NAVEE for managing the front end of a 3 level nested navigation but deciding on a back-end channel strategy that makes sense for the client is tough.
Some of the top level sections could be channels, but a lot of the child entries cannot be entries of that channel as they require different channel field groups, but as soon as I start placing sections in their own channels, so that I can use custom channel field groups, I start loosing structure/organization, and the whole back-end becomes a mess with some child sections being multiple entries of a channel and other child entries of the same top level section being a channel on their own.
Also some sections like books require a (general page channel field group) channel entry to manage the books landing page and multiple (books channel field group) channel entries for book data. Those 2 entries cannot be nested under the same channel, never mind being nested under our work…?
How does one structure the backend so that the client does not become confused?