-
Improvement
-
Resolution: Fixed
-
Minor
-
3.9
-
MOODLE_39_STABLE
-
MOODLE_39_STABLE
-
MDL-67264-review-squashed -
-
3
-
Activity Sprint 6
Redesign/restructure the activity chooser to fit the current design mock-ups
User stories
Story | Approach |
---|---|
As a teacher, when I click on the activity choose link(the link), I then see the activity picker(the modal), I can then see the activities/resources(the elements) in a grid format and I should not see any tabs(the tabs) in the modal. | |
As a teacher when there are lots of elements in the modal, I can scroll down in the modal to view them. | Allow scrolling |
As a teacher I can find out more information about the elements in the modal. | Click the 'i' icon and be taken to another page with more information. |
As a teacher I should be able to add an element once I have read the detailed information. | A button to add the activity should be present on this page. |
As a teacher I can select and configure an activity. | Click the activity icon and jumps immediately to the activity settings page |
Acceptance criteria
- All visible activities are listed in the modal.
- Activities are to be displayed in a grid as per the prototype.
- Third party activities are listed in the modal when installed (and visible).
- When there are more activities than will fit in the modal, scrolling down will display them.
- Clicking on the 'i' (information) icon shows the information about the module.
- Clicking the i results in a page sliding in from the right to show the information (The same as the activity chooser in H5P).
- A button to add the activity should be available from the information page.
- A single click of an activity icon will redirect to the mod_edit page for configuration.
- Activities can show additional items in the activity chooser.
- Adding activities works using Jaws and NVDA.
- Keyboard navigation is possible.
- Current behat tests should still work.
- Behat tests are created to cover new functionality (showing information, adding activities from the information page)
- If new methods / functions are added they are covered by unit tests.
- blocks
-
MDL-67321 Support categories/tabs in the activity chooser
- Closed
-
MDL-67261 Ability to star activities within the activity chooser
- Closed
-
MDL-67262 Add admin page for recommending activities
- Closed
-
MDL-67263 Ability to search in the activity chooser
- Closed
-
MDL-67585 New API for extending the activity chooser and implementation of favouriting
- Closed
- is blocked by
-
MDL-67286 Create unit tests for the base activity chooser - Sub task of MDL-67264
- Closed
-
MDL-67287 Create behat tests for the base activity chooser - Sub task of MDL-67264
- Closed
-
MDL-67288 Accessibility implementation & audit of activity chooser - Sub task of MDL-67264
- Closed
-
MDL-67289 Create a modal and templates - Sub task of MDL-67264
- Closed
-
MDL-67291 Create backend code to retrieve activities - Sub task of MDL-67264
- Closed
- Testing discovered
-
MDL-67965 Subsystems with named selectors should be overridable by themes
- Closed