[ONNX 1] Add Backend section to the left page of Tutorials layout page

[thiagocrepaldi]

This PR adds a Backends section to the left menu which initially will have a placeholder for the series of ONNX export tutorials based on Torch Dynamo backend

A table of content tree page will have static URL https://pytorch.org/tutorials/beginner/onnx/intro_onnx.html that will be referenced on PyTorch user document for torch.onnx module

Following is a screenshot of the resulting page

Preview page: https://docs-preview.pytorch.org/pytorch/tutorials/2550/beginner/onnx/intro_onnx.html

Fixes: #2552

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/2550

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit f90ef02 with merge base 587c62a ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[thiagocrepaldi]

#2541 will be added to this page as soon as it can be merged

[thiagocrepaldi]

@msaroufim FYI

[msaroufim]

I'm generally OK with having a tutorials/onnx index page but having onnx be a in the left hand navigation is not something I'm as excited about since I'd then have to also be OK with other compiler vendors doing the same

Is there any way we can roll this content in to the deployment tab?

[thiagocrepaldi]

I'm generally OK with having a tutorials/onnx index page but having onnx be a in the left hand navigation is not something I'm as excited about since I'd then have to also be OK with other compiler vendors doing the same

Is there any way we can roll this content in to the deployment tab?

If we could have submenus under Deploying PyTorch Models in Production menu, that probably would help already, but I think this is not a trivial task by quickly going through the code. That is why we proposed a ONNX menu on its own.

We do understand the duality of ONNX, especially after pytorch 2.x series. On one hand, torch.onnx is within pytorch project under the github.com/pytorch umbrella, like torchvision, torchtext, and torchaudio. Each of these other pytorch components have a menu on their own. From this point of view, ONNX module as pytorch's component could have a menu on its own. On the other hand, after pt 2.0 the concept of dynamo backends got generalized and vendors started implementing theirs and adding all of them might be tricky.

Also, because we introduced a new ONNX exporter based on Dynamo (torch.onnx.dynamo_export) but we still support the older one based on TorchScript (torch.onnx.export), we plan in having tutorials helping on the decision-making process of which one to use, which wouldn't be a "deployment" tutorial per se, but very related. Other related but not exactly deployment might be 1) migration process from the TorchScript to the Dynamo based exporter and 2) working around limitations of the exporter, helping users to fix their model for successful export. There is a whole bunch of ONNX-related tutorials to cover lack of documentation of the previous exporter that we plan that may not fit directly into the "deployment" umbrella and having them sprinkled in different menus would be a bit messy

I hope that helps making our case :)

[thiagocrepaldi]

Changed the left menu to Backends instead of ONNX as per offline discussion with @svekars

[msaroufim]

Ping me when the doc renders I still don't see the most recent changes

[thiagocrepaldi]

Ping me when the doc renders I still don't see the most recent changes

ping

[msaroufim]

ok just stamped thanks! @svekars what's the convention for merging things in tutorials I forget what the policy is, do you tag things as 2.1 and wait until core does that upgrade to merge?

[svekars]

Thanks! I will do an editorial pass. We will merge all 2.1 tutorials on the day of the release.

[svekars]

LGTM, just a couple of nits.

[thiagocrepaldi]

LGTM, just a couple of nits.

nits fixed