Skip to content

Poor v15 to v16 migration documentations #1884

@qu8n

Description

@qu8n

How can we improve the documentation?

Hey team, I'm excited for all these updates, but the experience of updating to v16 has been challenging.

The current docs is mixing up v15 and v16.

For example, the latest docs page shows v15 and the installation steps lead to users installing v15, yet some example commands are those of v16:
Image

Because v16 is a huge change, what do you think about having separate doc versions for v15 vs v16? Perhaps a navbar dropdown could let users select docs for v15 vs v16?
Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions