Unit Publish Details Card

Open
#2,814 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the linked Figma design and the existing Unit page's right-pane section. Trace how unit publication, visibility, draft, and release-date data are currently exposed, then verify the replacement cards cover the listed status and visibility states, metadata, actions, and settings-tab navigation.

Written by the indexing model from the issue text.

Description

Design

Figma link

published unpublished changes Staff Only Scheduled
Image Image Image Image

Specs

Unit Publish Details cards replaces the section on the right pane of the Unit page. The cards have:

  • top border indicating status:
    • if the unit is visible to staff only, top border is always primary-700
    • Brown draft color if the unit has unpublished changes or has never been published (exception: visible to staff only is always primary-700)
    • Blue (info-500) if the unit is published but not yet released (scheduled for a later date)
    • Green (success-500) if the unit is published and live
  • If the unit has any unpublished changes, there is a publish/ cancel button
  • Any unsaved drafts have the author, date, and time that created the last changes resulting in draft status
Image
  • Any published unit (whether or not it has drafts) has the "LAST PUBLISHED" section with author, date, and time of last publish
Image
  • Units show their release date along with where the date is set (course, section, or subsection)
Image

"Visible to" has multiple states:

All learners and staff Staff Only Component Restrictions Only Group Gated
Image Image Image Image
  • If the edit icon is clicked on the "VISIBLE TO" section, the sidebar changes to the Unit Info Settings Tab
Dominant language
TypeScript
Stars
17
Forks
218
Avg merge
9d 20h
Merged PRs (30d)
20

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.

More from openedx/frontend-app-authoring

All issues in openedx/frontend-app-authoring

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.