Location aware bullet menu
Posted: Sat Feb 12, 2005 8:53 am
What would it take to make a location aware bullet menu, one that knew where it was and displayed the children?
i.e.
Say this is the site layout.
1 home
2 about us
2.1 mission statement
2.2 vision statement
2.3 Disclaimer
3 contact us
On the about us page I would like a smarty tag {awarebullet -displayhome="yes"}
This would display on whatever page it is put exactly what the bullet menu does now with the starting level set to '2' only instead it already knows where it is. Optionally displayhome="no" would omit the page you are on from displaying on the menu.
I possibly have a client with a HUGE site and a HUGE archive of newsletters in html. These archives are a main page and 3 children. I would put this location aware tag in the template and just start dumping in the html. Then it would auto generate ALL of the structure of links from the parent/child structure of the site.
Tell me what you think.
btw... does anyone have a site with 650+ urls? (i.e. static content, pdfs and other links, likely 70% or more are content pages) That is the size site I am talking about. Likely I would seperate the archive in a subdomain with it's own database and maintain it seperately.
i.e.
Say this is the site layout.
1 home
2 about us
2.1 mission statement
2.2 vision statement
2.3 Disclaimer
3 contact us
On the about us page I would like a smarty tag {awarebullet -displayhome="yes"}
This would display on whatever page it is put exactly what the bullet menu does now with the starting level set to '2' only instead it already knows where it is. Optionally displayhome="no" would omit the page you are on from displaying on the menu.
I possibly have a client with a HUGE site and a HUGE archive of newsletters in html. These archives are a main page and 3 children. I would put this location aware tag in the template and just start dumping in the html. Then it would auto generate ALL of the structure of links from the parent/child structure of the site.
Tell me what you think.
btw... does anyone have a site with 650+ urls? (i.e. static content, pdfs and other links, likely 70% or more are content pages) That is the size site I am talking about. Likely I would seperate the archive in a subdomain with it's own database and maintain it seperately.