1. Nested lists (flat list vs. nested/tree) and different proof types -- iff, induction, etc. how do we indicate the different scaffolding for this?
2. Use syntax hint to set up a non-empty starting point.
2. Use syntax hint to set up a non-empty starting point.
3. Create templates from the start for different proof types
Later
Later
1. Nested lists (flat list vs. nested/tree) and different proof types -- iff, induction, etc. how do we indicate the different scaffolding for this?
1. Restrict blocks to fixed number of steps
2. Create templates from the start for different proof types
2. Allow student to select proof style (e.g. iff, contradiction) and pre-structure answer list accordingly
3. Restrict blocks to fixed number of steps
3. Allow some strings in the correct answer to be optional. Allow authors to input a weight for each item and use weighted D-L distance, e.g., weight of 0 indicates that a step is not required, but will not be considered incorrect if included.
4. Allow student to select proof style (e.g. iff, contradiction) and pre-structure answer list accordingly
4. Making use of third item in other ways? Hover over a proof step to reveal more information (e.g., this could come from the third item in the list and give a hint/definition)
5. Allow some strings in the correct answer to be optional. Allow authors to input a weight for each item and use weighted D-L distance, e.g., weight of 0 indicates that a step is not required, but will not be considered incorrect if included.
5. Allow students to mark items (e.g. as used or unneeded) or tick used items
6. Making use of third item in other ways? Hover over a proof step to reveal more information (e.g., this could come from the third item in the list and give a hint/definition)
6. Confirmation for delete all?
7. Allow students to mark items (e.g. as used or unneeded) or tick used items
7. Alternative styling/signalling for clone mode?
8. Confirmation for delete all?
8. Better support (and documentation) for bespoke grading functions.
9. Alternative styling/signalling for clone mode?
9. Hashing keys
10. Better support (and documentation) for bespoke grading functions.
10. Check sortable for keyboard accessibility (SM: Not built-in to Sortable currently: https://github.com/SortableJS/Sortable/issues/1951; however, it looks like it is do-able with some work https://robbymacdonell.medium.com/refactoring-a-sortable-list-for-keyboard-accessibility-2176b34a07f4)
11. Hashing keys
12. Check sortable for keyboard accessibility (SM: Not built-in to Sortable currently: https://github.com/SortableJS/Sortable/issues/1951; however, it looks like it is do-able with some work https://robbymacdonell.medium.com/refactoring-a-sortable-list-for-keyboard-accessibility-2176b34a07f4)
