openedx / openedx/frontend-app-authoring

Think through kebab menu on Studio Outline page to reduce redundancies with the sidebar functions

Open
#3,002 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
17
Forks
218
Avg merge
9d 20h
Merged PRs (30d)
20

Description

Now that we give users the power to perform a lot of functions and view a lot of information in the Studio sidebar, we'll need to think through if there are redundancies elsewhere in studio and make sure we only repeat functions where it makes sense to do so, so that we don't have too much information and/or calls to action in one place where they're not needed twice.

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 reviewing the Studio Outline page and its sidebar functions, then inventory the actions and information exposed in both locations. Done means identifying which kebab-menu items are redundant and deciding where each function should remain, but the issue does not name files, tests, or a concrete implementation scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
design, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.