Put Xet Spec in TOC, rename Storage Backends to Storage Backend - Xet

[rajatarya]

Attempt to reorganize Xet content so:

• Storage Backends -> Storage Backend - Xet
• Xet Protocol sections are subsections of Xet documentation
• Set up docs for more visuals added to sections, make Xet more top-level visible in Hub docs.

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[rajatarya]

The TOC doesn't seem to render well when it is 3 levels deep with longer subsection headers.

But this I believe is organized how Hub docs work - there are many small pages instead of larger ones - so I reorganized the main Storage Backends page into sections, and a TOC in the main page. The TOC can have deep links and then the navigation at the footer correctly goes to the next page in the section of docs.

[jsulz]

I agree that the navigation is far improved, but the lack of margin-left on the final level in the TOC tree is kind of distracting.

What if we just removed the Open Source Xet Protocol and moved Building a client library for Xet storage and Overall Xet architecture one level up?

[julien-c]

Ok i'm going to contradict myself from what i said in #1952 but probably makes more sense to keep the protocol in its own doc (/docs/xet) – given there are quite a number of pages and probably more in the future if some community-driven third party tools or implementations arise – while renaming the current Hub "entry point" page from /docs/hub/storage-backends to /docs/hub/xet.

WDYT?

[julien-c]

Suggested change

	- [Storage Backend - Xet](./storage-backends)
	- [Storage Backend (Xet)](./xet)

maybe we take this opportunity to just rename that entry point page to /docs/hub/xet

[julien-c]

Suggested change

	# Xet Storage
	# Xet: our Storage Backend