I'm admittedly a little uncomfortable with this approach. It doesn't fundamentally fix the issue, and reverts a documentation structure that was arrived at through consultation with a number of stakeholders and docs team members.

That said, since I can't be more closely involved in the day-to-day of docs work at this point, I won't put up too big a fight. I think it's incredibly disappointing that we can't more easily control/improve our own documentation site, but that's a discussion for another day.

@chrisvanpatten yeh, its not an ideal setup, and I wasn't trying to subvert any past decision. I just noticed every time trying to navigate to the tutorials it's not easy. I thought moving them up would be better, especially for new developers browsing the handbook.

I'll break this into two PRs, with this first one just adding a link on the index page. I'll create a new PR leave the table of contents change to be discussed.

I personally fully agree that this is a good proposal to temporarily improve the discoverability of tutorials until the menu gets improved. How about we land it as is and change it back later when the way menu works is fixed? By thw way, I strongly believe that tutorials should be in their own section visibly highlighted in the handbook. It might be even linked in the header orvsth like that.

I strongly believe that tutorials should be in their own section visibly highlighted in the handbook

That was my initial thought too, moving them to the top level, but thought that might of been too much. I believe people learn best by trying the tutorials and then when they get stuck and or want to advance further then reading the deeper documentation.