Kuwait Theme: Map View Styling

[FaithDaka]

PR Checklist

• PR title descriptive (can be used in release notes)

Description

• Styling support added for a curved map path

Author Notes

• The Kuwait map design has paths that wind a lot more than the wavy variant accommodates. A new variant, curved, is added in this update to support curvier paths.
• The task card now includes an additional attribute, locked_image_asset, to accommodate the locked icon that appears on top of the module.

Attributes added to sheet:

• variant: "curved"
• locked_image_asset

Git Issues

Closes #2667

Screenshots

To visualise the map path, the color stroke here is dark

Otherwise the map path is a light color to contrast with the proposed background image

A completed module is highlighted with a blue border while an in_progress module is highlighted with a yellow border

[FaithDaka]

For your review @jfmcquade @esmeetewinkel

[jfmcquade]

The new path style looks nice. However, it doesn't reflect the design and so won't line up with the background image in the same way. I think that will have to be addressed in the future as a follow-up, appreciate this could be quite difficult to implement.

I've tidied and clarified some of the logic with b7263f4.

Additionally, I think we'll need to handle the "locked" status differently. @esmeetewinkel – currently, this PR sets the "locked" status through the same logic that determines the completion status of the task group: namely, if the task group is "not started" (i.e. none of its constituent tasks are completed), then the task group is considered "locked". However, this doesn't allow us to handle unlocking task groups. If the task group is not clickable when it is locked, then there I don't believe there is a way for the user to begin that task group. If the task group is clickable when locked, then the "locked" status is misleading. So I think we need to handle the "locked" status via a dedicated parameter, and handle the logic elsewhere (e.g. in a dedicated locked column that gets updated through template logic). Does that sound right to you @esmeetewinkel? If so, I can update this PR. I think if we need to rush something in the short-term, we could leave the code as-is which would mean that a locked task-group could still be clicked on to enter that module.

[esmeetewinkel]

(e.g. in a dedicated locked column that gets updated through template logic). Does that sound right to you @esmeetewinkel?

Yes that sounds right

[jfmcquade]

OK @esmeetewinkel, I've updated to expose an explicit locked param. See final example in updated comp_progress_path template