Skip to content

doc: reduce version selector entries and introduce archive page #1395

Description

@onefloid

Description

The current version selector includes every created version, which will soon make navigation cluttered and harder to use.

Desired behavior:

  • The version selector should only include:

    1. The previous major version (e.g. v2.x)

    2. The last three minor releases of the current major version

    3. For each minor version, only the latest patch (micro) release

  • Older versions should remain accessible but should not appear in the selector.

Additionally, there is currently no centralized overview of all available versions.


Proposed Solution

  • Filter visible versions during deployment

  • Implement version selection logic

  • Add an archive page listing all available versions

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