Add library level docs

[tt-rkim]

Docs:

Get started TT-metal (GOOD: host, kernel apis, prog ex, Graykull; DELETE: Prog Model; TO ADD: paper) Libraries

• ttDNN - OP APIs (python)
• Tensor - API (python)

Frameworks

• TT-Dispatch Framework
  • Overview (100 words, it dispatches, uses ttDNN & Tensor libs. point to model zoo tests)
  • Model Zoo - maybe just a list of models and their status

[tt-rkim]

@jvasilje Checked new pages into main

1. When buliding, don't forget to a full make build then a full make all inside docs. Pybindings docs are built into code now, like our other docs
2. First version of Tensor lib + Op lib (ttdnn) under "Libraries" > "ttmetal Python API (will become ttDNN)". Combined for now, but will split out into appropriate places once dir reorg is done
3. TT-Dispatch stub under "Frameworks"
4. Deleted unwanted docs + ready to add paper

Should be ready for review + use by David's team, if that's still the plan

[tt-rkim]

@abhullar-tt @coffeeandcheesecake @DrJessop Hey guys, per this issue, we now have docs for pybinded code. Right now, a good chunk of the device and tensor modules have docstrings. They're embedded directly into the pybindings code, and you can reference them with a automodule directive in Sphinx.

As part of future development processes, please add docstrings with argument tables if needed and add them into the docs.

[tt-rkim]

Must write examples/explanations in libraries docs in response to questions here: https://tenstorrent.sharepoint.com/:x:/r/sites/Jasmina/_layouts/15/Doc.aspx?sourcedoc=%7B5[…]action=editnew&cid=c78df972-bd33-4d07-b81d-045d36ff51a8

Per @jvasilje 's feedback from early users

[tt-rkim]

Closing this as initial version of docs is complete, and now future versions are iterative. ttDNN and Tensor libs will eventually be split out into separate ones once #182 is complete

[jvasilje]

[jvasilje]

our current doc hierarchy is this:

• Getting Started
• Hardware
• TT-Metal APIs -- host apis -- kernel apis
• Programming examples -- dram loopback -- eltwise binary
• Libraries -- ttmetal python api
• Frameworks -- tt-dispatch
• debug tools
• performance measurement tools
• Release
• Developer onboarding

Docs hierarchy needs to be changed to this:

• Getting Started

• TT-Metal -- APIs --- Host APIs --- Kernel APIs -- Programming examples -- dram loopback -- eltwise binary -- Tools
  --- debug tools --- performance measurement tools

• Libraries -- Tensor ---Overview --- APIs -- ttDNN --- Overview --- APIs

• Frameworks -- TT-Dispatch --- Overview

[jvasilje]

the indents got flattened. should look like this:

[tt-rkim]

@jvasilje Done pls review. some points to keep in mind

• Developers onboarding will stay as is - it's needed
• Added overview section to libraries and move them around to fit what you wanted
• Any docs you specifically requested to not show up will be moved to sandbox otherwise they cause red warnings during build (ex. hardware, release notes which should be transferred to github release notes etc). Can't be hidden using directives
• Recall until we refactor the ttmetal pybindings build, "Tensor" and "ttDNN" are still one python module despite our future narrative push of labelling them two separate libraries