I have been using Umbraco for a while now and always created my sites with the following structure:
Home - Page 1 - Page 2 -Subpage 1 - Page 3 Global Settings (this is where I would put things like sidebars that appear on all pages)
This setup has always seemed to work ok for me although I'm not sure if it is considered best practise however I am in the process of creating multiple sites in one Umbraco instance so I really want it setup as follows:
Website 1 (Mange hostnames setup on this node) - Pages - Home - Page 1 - Page 2 - Settings Website 2 (Manage hostnames setup on this node) - Pages - Home - Page 1 - Settings Global Settings
First of all is this the best way to do things? Secondly how do I make it so that my Home page is in fact my homepage rather than it trying to go to Website 1 node when going to the URL?
What I usually do is creating my content tree like this:
- Content (the default top most node in the Content section) - Homepage 1 (This is my homepage on site 1 URL: / and Manage hostnames setup on this node) - Page 1 - Page 2 - Page 3 - Homepage 2 (This is my homepage on site 2 URL: / and Manage hostnames setup on this node) - Page 1 - Page 2 - Page 3 - Global Settings
If you create this structure, then you won't have any problems with redirecting to "/", as this is actually your real frontpage. Also, the build in XSLT templates (eg. the navigation tempalte etc.) is based on this structure, and so is the starter kits (Runway etc.). So I think this is the best way of building the structure. No need for nodes that aren't used at the first couple of levels.
Just wanted to let you know that Sebastiaan Janssen has written a new blogpost about how he usually structures his content nodes. You can find it here.
Don't know if you already got you question answered (??), or still are looking for some best practise for structuring content in Umbraco, but now you have another ressource.
Making child page the homepage
Hi all,
I have been using Umbraco for a while now and always created my sites with the following structure:
Home
- Page 1
- Page 2
-Subpage 1
- Page 3
Global Settings (this is where I would put things like sidebars that appear on all pages)
This setup has always seemed to work ok for me although I'm not sure if it is considered best practise however I am in the process of creating multiple sites in one Umbraco instance so I really want it setup as follows:
Website 1 (Mange hostnames setup on this node)
- Pages
- Home
- Page 1
- Page 2
- Settings
Website 2 (Manage hostnames setup on this node)
- Pages
- Home
- Page 1
- Settings
Global Settings
First of all is this the best way to do things? Secondly how do I make it so that my Home page is in fact my homepage rather than it trying to go to Website 1 node when going to the URL?
What I usually do is creating my content tree like this:
- Content (the default top most node in the Content section)
- Homepage 1 (This is my homepage on site 1 URL: / and Manage hostnames setup on this node)
- Page 1
- Page 2
- Page 3
- Homepage 2 (This is my homepage on site 2 URL: / and Manage hostnames setup on this node)
- Page 1
- Page 2
- Page 3
- Global Settings
If you create this structure, then you won't have any problems with redirecting to "/", as this is actually your real frontpage. Also, the build in XSLT templates (eg. the navigation tempalte etc.) is based on this structure, and so is the starter kits (Runway etc.). So I think this is the best way of building the structure. No need for nodes that aren't used at the first couple of levels.
/Kim A
Hi again
Just wanted to let you know that Sebastiaan Janssen has written a new blogpost about how he usually structures his content nodes. You can find it here.
Don't know if you already got you question answered (??), or still are looking for some best practise for structuring content in Umbraco, but now you have another ressource.
/Kim A
is working on a reply...