hierarchy of "required" in the "Scrub" page

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
design, frontend

Research direction

The issue identifies only the Scrub page and UX/Design feedback; it names no files, tests, or entry points to inspect. Clarify which sections should be more prominent, how the hierarchy should work, and what completed behavior should look like before starting.

Written by the indexing model from the issue text.

Description

Front End

via the UX/Design people, they said that we should consider creating a hierarchy of sections in the "scrub" page to make somethings more prominent and more "required" in a way.

Dominant language
Python
Stars
123
Forks
20
No merged PRs in 30d

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.

More from WheatonCS/Lexos

All issues in WheatonCS/Lexos

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.