Put Xet Spec in TOC, rename Storage Backends to Storage Backend - Xet #1956
Conversation
|
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. |
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. |
|
I agree that the navigation is far improved, but the lack of What if we just removed the |
Co-authored-by: Wauplin <[email protected]>
There was a problem hiding this comment.
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?
Updated rate limits for Team, Enterprise, and Enterprise Plus organizations.
Co-authored-by: Wauplin <[email protected]>
* doc: add zai as inference provider doc * update * generate z.ai * rerun zai docs * tip formatting --------- Co-authored-by: SBrandeis <[email protected]> Co-authored-by: Wauplin <[email protected]>
Co-authored-by: Wauplin <[email protected]>
* xet protocol file and CI setup * xet-protocol -> xet
Co-authored-by: Wauplin <[email protected]>
Co-authored-by: Wauplin <[email protected]>
rajatarya
force-pushed
the
rajat/storage-backend-xet
branch
from
b826967 to
51eab75
Compare
|
Argh, closing this PR and will create a new one - this one picked up too many changes in my attempts to rebase against main. |
Attempt to reorganize Xet content so: