You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A developer from company X pointed out that opening https://docs.lightstreams.network/ and clicking on "install" takes the user to Leth installation instructions.
Expected behaviour
Default installation instructions should navigate to Lightchain (not leth)
[my idea] Opening https://docs.lightstreams.network should also give a visual option/path for developer to choose which Lightstreams product documentation developer can check Lightchain/Leth/X etc
Additional notes from chat:
What do you think if the docs would be splited per product? Would that make sense? https://docs.lightstreams.network because opening docs right now, and clicking on HTTP API actually takes me to Leth which is bit confusing. The same with "cli docs" normally developers want to choose which product they are interested in and then click on some specific guide/doc/HTTP API/CLI doc, I don't think someone will want to click on "cli docs" and then browse all CLI docs of all products.
A developer from company X pointed out that opening https://docs.lightstreams.network/ and clicking on "install" takes the user to Leth installation instructions.
Expected behaviour
Additional notes from chat:
What do you think if the docs would be splited per product? Would that make sense? https://docs.lightstreams.network because opening docs right now, and clicking on HTTP API actually takes me to Leth which is bit confusing. The same with "cli docs" normally developers want to choose which product they are interested in and then click on some specific guide/doc/HTTP API/CLI doc, I don't think someone will want to click on "cli docs" and then browse all CLI docs of all products.
IDK, just thinking loud. WDYT @azappella / @ggarrido ?
having some visual boxes to choose from right at the beginning and then stay in that context would be sweet imo
The text was updated successfully, but these errors were encountered: