Revamp the curriculum UI

[mahesh-krishnakumar]

Draft plan

The curriculum UI will be rebuilt in multiple phases:

Phase 1 - Detach student course progress from levels.

• Allow grouping a set of targets into a milestone.
• Remove milestone property from target group.
• Update progress in the student report based on percentage completion of each milestone.
• Student distribution bar in students page and organizations page will change to number of students who have completed a set of milestones and not level.
• Remove association of students to level.
• Remove manual level up logic.
• Remove level progress from all UIs, such as check mark in level dropdown in curriculum.
• Cleanup all course progression services based on levels.

Phase 2 - Move assignments out of target content.

• Create assignment blocks similar to content blocks. These have no association with the target
• Extract the current details' editor as an independent assignment editor.
• Create assignments list in the student's UI, grouped by milestones.
• Cleanup submissions section from target content.
• Create data migration to generate assignments and group them into milestones.
• Remove grouping of targets into milestones created in Phase 1

Phase 3 - Pages editor and student view

• Cleanup levels
• Create migration from existing targets to pages in the backend
• Implement full UI based on - https://www.figma.com/file/5rjyHEdkjMPmkOWv6PHN9p/curriculum-UI?node-id=415-7060&t=IEg8unURVS2l2JsY-0
• Drop targets, levels

[harigopal]

Concerns about phase 1 plan

Let's turn the issue into a detailed RFC on the repo discussions section, adding rough visuals for how changed elements are supposed to look.

Allow grouping a set of targets into a milestone.

We'll want these to be ordered milestones.

Update progress in the student report based on percentage completion of each milestone.

Both report pages - student report shown to coaches/org admins, and own report shown to a student will need to change, right? Also, is it enough for the completion percentage to be shown to the student in a separate report page? The plan also says...

Remove level progress from all UIs, such as check mark in level dropdown in curriculum.

Is there a better/quicker way to for the students to see their own progress?

Missing items in phase 1 plan

• Create and invoke services to cache a student's milestone completion when targets are completed.
• Update course completion timestamping to mark itself when all milestones in a course are completed.

Concerns about phase 2 plan

Title: Move assignments out of target content.

That seems weirdly titled. I think you meant to say something like Move assignment details outside of the targets table.

 > Create assignment blocks similar to content blocks. These have no association with the target

How can these have no association with the target? They still need to be presented with the target, same as in phase 1, right? I'm assuming that an Assignment will, similar to a ContentBlock, have a target_id column in this phase. Probably not a target_version_id, though (which content_blocks have), since the assignment isn't a part of the ordered & versioned block structure yet.

Remove grouping of targets into milestones created in Phase 1

This should probably say Group assignments into milestones instead of targets.

Missing items in phase 2 plan

Cleanup submissions section from target content.

This is okay, but this needs to be coupled with the addition of a link from student's view of target content to the assignment's page which, I'm guessing the list of assignments shown to students. I'm also guessing that all interaction with the assignment moves into this page if it has got a form or a quiz.

It's possible this will mean an Assignment being rendered on the target content page, which links out to Assignment#show when required.

Create data migration to generate assignments and group them into milestones.

Coupled with this, we'll also need to set up prerequisites between assignments based on the existing level structure.

Concerns about phase 3

This needs quite a bit more detail.

Create migration from existing targets to pages in the backend

This is an epic item all on its own.

Off-topic

Would it now be possible to link calendar events to a milestone or an assignment? To allow the calendar to act as a visible deadline for students in the UI? This could be quite useful.

[mahesh-krishnakumar]

Updated as a new RFC after incorporating the above comments to : #1264