Redesign how we present troubleshooting information #1270
Labels
stale
All issues that are marked as stale due to inactivity
Comments
1 task
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
@tomkerkhove , we could include this as part of next round of work from CNCF? |
JorTurFer
removed
the
stale
|
Goal is to have it yet, project is associated |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
tomkerkhove
removed
the
stale
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
This issue has been automatically closed due to inactivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, troubleshooting information is a bit fragmented across different pages:
Although all of them look as versioned, only the last one (scaler pages) is versioned, so we have different paged for serving the troubleshooting versions, some of them versioned, other not versioned...
I think that we should rethink this section to make it more usable and user friendly. IMHO it's a high value change because if the FAQ/troubleshooting information is easily discoverable, we can reduce the overhead answering to user questions and users will be more happy because they can solve the issues by themself.
My proposal is generating a troubleshooting section with all this information available and and in page search to look for info by keywords. This section can contain some subsections/pages:
The text was updated successfully, but these errors were encountered: