This content has been marked as final. Show 5 replies
I am very pleased with the majority of the 'doc site' improvements taht were introduced with the 11gR1 docs.
So for what it's worth, I second Daniel's comment.
Indeed, I'd love to get the following variations as a 'challenge' for future upgrades:
- Cookie-based hide/show, so I can set it as a preference for all sessions
- Have the book-search/nav user-switchable from the current back to the master tree nav found on the main page
- Add a 'Home' to the Main categories (the Master Book list and Master Index are both in the Nav section and the Nav links at top of page, but Home is only at top of page.)
But in general, Kudos to the web team for the layout, and to the writers for the improvements in content, especially 11gR2 (noticably DB Concepts and DBA)
I asked someone in the doc organization who is very familiar with this area, and this was the response:
The site is working as designed. If we decide we want it to work differently, we'll need to scope the work. Regarding the nav bar, the thread makes four suggestions:
* Add a Home link in the navbar. We can consider adding a home link, but -- as the poster acknowledges -- the Home link already appears at the top and bottom of every page.
* Make the navbar be able to switch between showing the current book contents (as it does currently) and also optionally showing the library contents. This would be a lot of work, so we have to decide on priorities.
* Disable the navbar altogether. Yes, if you delete or rename doccd.js the navbar is permanently gone. This is a good solution for people who don't want the navbar at all and who don't even want the interactive choice of whether or not to show it.
This trick of deleting a local js file does not work with all the products.
Instead, you can use adblock in Firefox to block the offensive code
I suspect someone involved with the documentation group thinks that he (she?) knows better than I do how I want to use the documentation.
Perhaps they want to spy on the use of the docs by associating the requester IP address with the script access request in the HTTP server logs
The spying is mildly irritating, the trying to override my usability really irks.
You can always revert to the pdf docs - they look prettier but don't bookmark as nicely as the HTML version.