You are raising a very important question that MUST be considered. Unfortunately I am not surprised that no one has followed up on this post - we keep forgetting how important fallback is.
Eye-candy wise dTree is a pure pleasure and it gives the visitor a pleasant, time-saving navigation, but a fallback-method should be the first thing to consider in projects like this.
Anyone done this already?
Anyone having different views on this?
Let me know how this goes allermand!
Sorry, I haven't found time to actually look at your code yet - too many project to finish before X-mas : /
But I found a simple solution that works - For each dTree main-function you enable, also make use of the corresponding WordPress default.
Say you enable the WP-dTree Pages functionallity from the Widgets page, you add the default WordPress Pages right below.
One lovely thing about WordPress (ok, theres a few) - you have classes everywhere. Every tiny little thing can be caught from anywhere, which luckily goes for the blocks in the sidebar as well - they all have their own id's or classes, which you can make use of in the stylesheet (...or is that stylecheat =)
In your stylesheet add following to make the page SEO-friendly and obtain the great dTree-candy:
Voila! ces't tout - and the same can be done with categories etc.
I still would very much like to dive into your dTree-code to see if I can find and suggest a more appropriate way for this that does not demand further action when enabling the dTree main functions. Unfortunately time is a bitch and I can't say when this will be.
Happy coding all!
Speaking of SEO (and not gracefull degradation) - I'm no expert but I've always called the archives in the header, for spiders and bots to index but not for browsers to display. Am I doing it wrong™?
Ok, I was not aware of the rel-links nor that they were added by wp-dtree. I guess that will help posts getting indexed, but what about pages?
If/when I make any progress I'll share.
This topic has been closed to new replies.