17

It seems that currently if you want to avoid the main "about" page at the top of an "about" structure having a slug of /about/about/ then the approach people seem to take is to create an About page as a single, and a separate structure for subpages.

An alternative approach that occurred to me is to give the structure section a URL of just {slug} and then make everything a child of the "About" entry. Is there any particular disadvantage to doing this though?

I can see that it potentially allows URLs from different structures to clash (if someone creates a new top-level entry in a structure), but my feeling is that if I have to choose, the possibility for users to mess up the structure seems less bad than the probability that the "separate single + structure" approach will be confusing for users. Is there some other disadvantage that I'm overlooking here, though?

Improve this question

1 Answer 1

Reset to default
9

I recently setup a structure which contains (almost) every page of my site. When I set it up, I specified only {slug} as the URL.

So far, it's working fantastically! And that's with about 30-40 pages created in the structure (some nested within others).

Improve this answer
7
  • Thanks, that's good to know. Have you tried this with multiple structures at all? I'm wondering whether there are any potential pitfalls with having multiple sections that all use the base URL of {slug}
    – Nick F
    Jun 17, 2014 at 17:12
  • I contemplated doing it with multiple structures, but then I decided it was better to use one master structure. If your structures are based on "which nav the link appears in", there's no guarantee that you may or may not add that page to a different nav. And you definitely don't want to have to move your page data between structures, or get creative with how your nav displays.
    – Lindsey D
    Jun 17, 2014 at 17:15
  • The docs on "How to create a nav for my Structure section" were incredibly helpful... It's good to know that your generated nav doesn't need to start at the root level.
    – Lindsey D
    Jun 17, 2014 at 17:20
  • Hmm. That's definitely a possibility - I think it's less confusing than the "single for top page / structure for sub-pages" approach - but I'm pretty keen to keep sections separate if at all possible, rather than lumping them all together...
    – Nick F
    Jun 17, 2014 at 17:35
  • Curious, what are the distinctions between your structures? I thought about having a main "parent" structure, then several key "children" sub-structures... Each child sub-structure would serve the purpose of individual structures. Haven't tested it yet though. Big benefit... You can easily share Entry Types anywhere within the overarching structure.
    – Lindsey D
    Jun 17, 2014 at 17:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.