I have a site I’m going to develop and I was hoping to get some guidance on the backend structure/tree.
It’s going to be a site for running; marathons and ultramarathons to begin with and then spreading to other sports: cycling, triathlons, etc. I was thinking of having the structure like:
Running
+---Americas
+---Oceania
+---Asia
+---Europe (etc)
+---France
+---Denmark
+---UK (etc)
+---Midlands
+---London
+---South East (etc)
+---Spartan Series
+---24.6 miles
+---50 miles
+---100 miles
Cycling
+---Americas
+---Oceania (etc etc etc as above)
Does this sound correct for best practice structure? With this structure it will be easy to get races in a certain sport in a country/region but I will have repetition of all the countries and regions for each sport. the other way is to list by distance, and then I can’t group a series together as they are usually different distances. In addition, sometimes races in a series are in different regions - so they will be split up anyway.
Would anyone have any guidance as how to best structure this? Everything will be tagged so that will help I guess...
Thanks!
Some thoughts...
Containers
- Rewrite rules: Using containers make it easy to build nice URLs "europe/uk/london/"
- Landing pages: Using containers means each container is a page as well.
- Back End Admin: Using containers you can locate resources faster and it’s more "client friendly"
Tags
Thanks Mr Haw, sounds like I’m on the right track then. Cheers
