Skip to content

[Internal]: CCR Compatibility Matrix is hard to see and has readability issues once expanded #2889

Open

Description

@geekpete

Description

In the CCR docs, there's a matrix to show which stack versions are CCR compatible with which other versions.

The first problem is that this is fairly obscure and hidden so easily skimmed over or unnoticed.

Image

Once you find it to expand, the table doesn't fit in one view and you have to clue onto the horizontal bar at the bottom of the table to realise there's more content/versions listed to the right of what you can see.
Making things worse is that the last column you can see is for 7.0 which might be misread as 7.0+ if it's misunderstood as the last column in the matrix.

Image

The summary is that the readability of the matrix could be improved if it was all in one view.

Copying the table from the docs page into a google sheet shows it can be easily displayed in full in a more compact form if the column widths weren't so extreme with wasted whitespace.

Image Image

The ask would be to improve the formatting to avoid needing to scroll primarily, and make the compatibility matrix more easily discovered either by not collapsing it and showing the whole table on initial load or by increasing the visibility of the matrix dropdown or linking to a separate page for it.

Resources

The path the file/page in question is deploy-manage/tools/cross-cluster-replication.md:
https://github.com/elastic/docs-content/blob/main/deploy-manage/tools/cross-cluster-replication.md?plain=1

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

N/A

What release is this request related to?

N/A

Serverless release

N/A

Collaboration model

The documentation team

Point of contact.

Main contact: @geekpete

Stakeholders: @kvesthy

Activity

  1. geekpete commented on Sep 10, 2025

    @geekpete
    Author

    Possibly related:

  2. added
    Team:AdminIssues owned by the Admin Docs Team
    Team:DeveloperIssues owned by the Developer Docs Team
    on Sep 10, 2025
  3. added
    Impact: 3Meaningful improvement or harm
    Reach: 3Common task or moderate surface
    on Oct 12, 2026
  4. georgewallace commented on Oct 26, 2026

    @georgewallace
    Contributor

    Take a look at this compatibility chart similar to what you looked at for the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Confidence: 0.8Mostly clear; minor unknownsEffort: 0.1~1-2 hours (0.1 week)Impact: 3Meaningful improvement or harmReach: 3Common task or moderate surfaceTeam:AdminIssues owned by the Admin Docs Team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions