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 where to start as clear as possible.
Based on these purposes, my two cents regarding to the issues @tqchen raised: Q1a as it has a more friendly and direct information for starters. Q2c?: I personally don't really care if API reference is on top-level or not. People always ignore the parts they don't care. Instead, I think it would be more useful to separate API reference to user APIs and developer APIs. User APIs are more like user interface/programming model, such as `relay.frontend.from_pytorch`, `relay.build`, etc. Developer APIs are internal APIs such as the generated Python API reference. Note that they don't have to be strictly separated. My point is whether pure users can find something they think useful instead of feeling frustrate when seeing tons of APIs but have no idea what's useful to them. Q3c: If a developer comes to the docs for a purpose, it is usually very specific and may cross multiple architecture components (i.e., "add a new Relay op", "add a new backend", "add a new pass", "improve CUDA codegen", etc). Embedding how-to tutorials to architecture components would make them lose if they have no idea what component they should work on for their purposes. Amount Q3a and Q3c, I'd prefer Q3c, because when developers find the tutorial they want, they can also learn which components are relevant and they should understand these components more. Q4b: Given that these sub-topics are targeting to very specific audiences, decoupling them clearly to make the main page concise seems better. --- [Visit Topic](https://discuss.tvm.apache.org/t/updated-docs-pre-rfc/10833/6) 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/95b99c7ab7796c5fb70af82cfc1251a9ec06d5a1d37f87f6b046c4da70f7ac89).
