Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Technical Terminology In-Context #282

Open
DenicaGo opened this issue Feb 4, 2025 · 0 comments
Open

Clarify Technical Terminology In-Context #282

DenicaGo opened this issue Feb 4, 2025 · 0 comments

Comments

@DenicaGo
Copy link

DenicaGo commented Feb 4, 2025

Description

Context: The onboarding process for new implementers has proven to be challenging so user research was done with early implementers to address any obstacles by identifying and analysing areas for improvement within the onboarding experience.

Research finding: A number of participants struggled with the use of technical or domain specific jargon throughout the documentation. Clear definitions or links to glossaries would make the content more accessible and improve comprehension.

User story: As a user, I want technical terms to be clearly defined in-context within the documentation or through tooltips, so that I can fully understand the content without needing external explanations.

Acceptance Criteria

  • All technical or domain-specific terms are clearly defined within the documentation where they first appear.
  • Definitions should be concise, non-technical, and provide practical context.
  • Each technical term should be linked to a central glossary that provides a more detailed explanation if needed.
  • The glossary should be easily accessible from the main navigation and searchable.
  • Defined terms should be visually distinct (e.g., underlined, bolded, or marked with an info icon) for easy identification.
  • A standardised approach should be used across all documentation pages.
  • Definitions and tooltips should be easy to update when terminology evolves.
  • A process should be in place to identify and address unclear terms based on user feedback.

Tooltip Support (If Feasible):

  • Hovering over a technical term displays a short, inline definition in a tooltip.
  • Tooltips should not disrupt reading and must follow accessibility best practices (keyboard and screen reader compatible).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant