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 approachable and as
exposed as possible to potential users. As such the starting point of a quick
Tutorial and How Tos for core user journeys makes a lot of sense to minimise
friction. Keeping a clear divide is important here, as the core Tutorial
provides the introduction whilst the How Tos provide "ok here's your use case
and what buttons to press" (I believe this is Q0a + Q1a).
As a user following this my next point of call would be to try and find a
matching How To to a more exact use case, or decide to read some Explanation of
that concept - which I believe the Architectural Guide does well (Q3b?).
I think this is essentially:
* Getting Started
* Tutorial
* How To
* Tutorials
* Tutorial
* How To
* Specific Things
* Topic
* Explanation
* How To
* Reference
This collects Topics under the Specific Things section so you don't have two
places to look to find details on a specific topic - at the cost of one level
of nesting.
[quote="hogepodge, post:1, topic:10833"]
It recognizes that while in most communities there is a distinct divide between
the user and the developer communities, there can be significant overlap given
the nature of TVM as an optimizing compiler.
[/quote]
I understand your sentiment here, but I would expect that divide to occur as
efforts like this make TVM more approach-able and I would therefore plan for
TVM being usable by a broad spectrum of users.
[quote="hogepodge, post:1, topic:10833"]
The TVM community is unique in that frequently users will need to extend TVM to
accomplish some goal, for example adding a new backend for code generation.
[/quote]
Following from the above, I'd question whether this is actually how we want to
consider users, once the groundwork is in I would expect users to simply run
`tvmc` or a python script against a number of developer created backends
similar to how a user would use any other ML framework (without knowing the
intricacies of its operation). I would agree with keeping the docs together
though, the L2 - Tour Style would then let you go as deep as you need to get
your model optimised.
Overall, I'm in favour of the formalisation to allow us to have discussions
regarding placement and I think this provides a huge improvement in clarity.
---
[Visit Topic](https://discuss.tvm.apache.org/t/updated-docs-pre-rfc/10833/8) to
respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click
here](https://discuss.tvm.apache.org/email/unsubscribe/e34072187122b7644a27921dcc859c13bd311fb552a53ae0163181e90b9b4bf5).
