hogepodge opened a new pull request #9203:
URL: https://github.com/apache/tvm/pull/9203


   RFC: 
https://github.com/apache/tvm-rfcs/blob/main/rfcs/0027-formalize-documentation-organization.md
   Tracking Issue: #8987
   
   Stage 1 of the documentation refactor reorganizes the docs structure,
   moving files (without content changes) and adding new scaffolding to
   generate the proper document tree.
   
   It does not address naming, style, content, links, or other existing
   content in documents that were moved. State 2 will address fixing these
   issues with existing content.
   
   Major changes include but are not limited to:
   
   * Dividing the existing tutorials into two sections:
     * Tutorials
     * How Tos
   * Moving all of the existing tutorials out of the `/tutorial`
     directory and into the more general `/gallery` directory.
   * Breaking up how-tos into individual sections for more
     flexibility and more consistent rendering.
   * Moving content into new classifications:
     * `/docs/arch` for architecture guides
     * `/docs/reference` for API guides and other reference material
     * `/docs/topic` for topic specific guides such as microTVM and VTA
     * Restructuring `/docs/dev`
   * Adding a table of contents to the doc index
   * Adding instructions on how to install using third-party tlcpack
   
   Stage 2 of the documentation refactor fixes naming and links
   in the documentation to be consistent with the overall structure.
   
   Major changes include:
   
   * an update to how to contribute to docs.
   * several updated index pages with title changes to match
     the organization style and bring consistency to the sections
   * expanded descriptions of some page collections
   * fixed links


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to