WheatonCS / WheatonCS/Lexos

Help Documentation

Open
#1,080 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Documentation Front End
Dominant language
Python
Stars
123
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Via the UX Design people, there is too much text and it is too overwhelming.
Solution: could include a search option so user can type and find what they need help on.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a documentation file, test, or entry point. Start by locating the help documentation and reviewing how users currently navigate it; clarify the intended search scope and UX before implementation. Done means users can search the help content and find the relevant guidance.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.