microsoft / microsoft/pxt

Improve tutorial experience on short screens.

Open
#10,362 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
641
Avg merge
12h 4m
Merged PRs (30d)
57

Description

Is your feature request related to a problem? Please describe.
Tutorial content gets cut off on short screens, both in the modal and in the upper portion of the editor. At Forward Education workshops it's a recurring issue that our customers can't find the next button. I recall personally experiencing this at first too.

Describe the solution you'd like
A prominent scroll bar would cue the user that there is more content that they can scroll to. Currently the scroll bar only shows on hover. Moving or reworking the navigation could avoid scenarios where all of the tutorial content is or seems to be present with the navigation being hidden. For example, just taking what is now at the bottom and moving it to the top could be an improvement. Or have it always present like it is for the modal.

Describe alternatives you've considered
A prominent scrollbar could be enough on it's own to prevent confusion .

Additional context
https://makecode.microbit.org/#tutorial:https://github.com/climate-action-kits/pxt-fwd-edu/ms-aquaticgarbage-use

Image

Image

Contributor guide

Open the contributing guide

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

Start by opening the linked tutorial and reproducing the issue on a short screen, checking both the modal and the upper portion of the editor. The work is done when tutorial content and navigation remain discoverable, with a prominent scrollbar or an equivalent navigation arrangement that lets users find the next button.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.