It could easily fit into the getting started section, a “Documentation Guide”
which lays out the organization and motivation, as well as how to contribute.
---
[Visit Topic](https://discuss.tvm.apache.org/t/updated-docs-pre-rfc/10833/23)
to respond.
You are receiving this because you enab
Thanks @hogepodge .
Placing higher-level tour into Getting started would indeed help us incorporate
elements from L2 into this framework and combines the concern of M0 and M1. As
a result, we could start with L3 and continue to improve our docs.
As part of the docs, it would be great to capt
In reviewing the feedback, it appears that there is a preference for including
easier access for some specialized pages, and ordering the layout in a way that
moves through the user and developer journey of beginner to expert. I've
refined the discussion into a new structure that attempts to a
Just read through this and providing my own opinions. I'm a huge fan of L2 -
Tour Style here, and I appreciate that it blends topics such as TVM and
microTVM in the beginning rather than treating them as separate; it makes a lot
of sense to me to use this to ensure we make all of TVM approacha
Before I address the questions and options individually, I want to return to
one of the motivating factors for why I feel like the proposed model will be
effective. Please take the time to review t[his talk about the documentation
system](https://www.youtube.com/watch?v=t4vKPhjcMZg) or the [si
IMHO, the docs should serve for two major purposes:
1. For pure users who don't care how TVM is implemented but just want to
achieve high performance, we need to let them hands on as convenient as
possible.
2. For new developers who want to improve something with TVM, we need to let
them know
Thanks, @hogepodge. It's a good opportunity for us to enhance TVM documentation
and tutorials together. I want to share some of my thoughts on it.
## A Separated Developer Documentation
Users(who will use TVM as a tool to compile models on supported models and
backends and won't change much of
Thanks @hogepodge for the RFC. It would be great for us as a community to
converge on a documentation system that we can all collaborate together.
Based on the current proposals, I find that it might be helpful to dissect the
possible choices here to facilitate the discussion(since we might wa
I would prefer L2 in terms of more precise section titles. Sometimes it is
really hard to distinguish "User Guide" and "Developer Guide", and L2 replaces
them with more explicit terms "Tutorials by example", "Architectural guide by
each component of TVM system". The only thing missing here is
CC @jroesch @tqchen @zhiics @ziheng @yzhliu @masahi @thierry @haichen @Laurawly
@merrymercy @comaniac @FrozenGene @jcf94
As we are pushing for major doc refactoring work, we would love to hear more
from the community on the desirable doc structure, which is vital for our
community in terms o
# Summary
Last year [an RFC was
proposed](https://discuss.tvm.apache.org/t/rfc-tvm-documentation-refactor/7456)
to address the organization and structure of the TVM Documentation. After
discussion, a first pass was made at the documentation updates following a
[formal documentation method de
11 matches
Mail list logo
