I'm going through the built-in tutorial that gets shipped with Umbraco. Slide 4 of 12 of "The Content Section" shows how the website consists of the Home page and several pages under that:
But on the website itself, it just looks like a series of pages:
Why are all the pages considered "sub-pages" of the home page?
Gibran, the navigation tree is built in hierarchy so in case you create a page outside the home page tree it's url will be under home url which is the root (/) i.e page people url is /people under root.
I see that why having is ok for me in case you have many websites otherwise I choose to avoid it.
1.Child page sample url.
2.Remove child page and create one on the root.
3.Conflict when having same content name one on the root and other as child page.
Why sub-pages?
Hello,
I'm going through the built-in tutorial that gets shipped with Umbraco. Slide 4 of 12 of "The Content Section" shows how the website consists of the Home page and several pages under that:
But on the website itself, it just looks like a series of pages:
Why are all the pages considered "sub-pages" of the home page?
Gibran, the navigation tree is built in hierarchy so in case you create a page outside the home page tree it's url will be under home url which is the root (/) i.e page people url is /people under root.
I see that why having is ok for me in case you have many websites otherwise I choose to avoid it.
Hmmm... let's see if I understand.
If I click on home, the url is:
http://localhost:63776/
If I click on people, the url is:
http://localhost:63776/people/
What would the url look like if I put people at the same level as home?
Yes, Gibran
The same url http://localhost:63776/people/ unless you change the domain as mentioned in this answer.
See the following scenario:
1.Child page sample url.
2.Remove child page and create one on the root.
3.Conflict when having same content name one on the root and other as child page.
Thanks for the detailed explanation. It makes total sense.
Gibran, don't forget to select an answer.
is working on a reply...