[Resolved] Short. vs Long linkTitle
#5039
Closed
svrnm
started this conversation in
Information Architecture
Replies: 2 comments 8 replies
-
Thanks for raising this. I'd rather go with long linkTitles (though within reason). Why? Because...
Kubernets is following that path already, it seems: https://kubernetes.io/docs/setup/production-environment/tools/ |
Beta Was this translation helpful? Give feedback.
8 replies
-
Since we all agree that we are OK with longer titles to accomplish more clarity, I will close this discussion now. If we ever need to revisit this decision, let's have a new discussion |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Taking this discussion out of #4966 and #4853:
To make the new proposed information architecture successful, we need to consider to rethink our preference for short (or very short) linkTitle, which will be used in the side navigation presented to end users. One example among a few is "SDK" vs "Managing telemetry with the SDK" (see #4966 (comment)).
I expressed my concerns in this comment:
So if we go with "SDK" we have to assume that people read some of the introductions to understand what to expected when they click on it. My assumption is always that people read nothing and just look for the one thing they currently care about (e.g. "managing telemetry" or "capture telemetry"), so they will not find that if the title is "SDK" and will tell that our documentation sucks.
I'd like to understand from @open-telemetry/docs-maintainers, @open-telemetry/docs-approvers and others, what your preference is and what advantages you see between the one or the other?
We need to make a decision eventually, and then write this down in our contribution guidelines.
Beta Was this translation helpful? Give feedback.
All reactions