Martin Dougiamas

Thanks for getting engaged even at this very late stage guys.

As this is an MUA project (that they defined and funded) we're primarily engaging with them on this over at moodleassociation.org 

Of course, feedback from all stakeholders is also welcome on the tracker, although, as usual, a bunch of opinions on user interface are very difficult to weight and synthesise there.   This was one of the whole points of the MUA as a body, and our UX design process from some months ago,  to help define the specs that we've been working to address.

The team are working hard now on addressing new issues being raised.  Helen posted a good description of the phase we are in.

Well, it's in 3.2 now! 

You can look at moodle.org/demo (the demo link at the top of this page) for some demo sites.

Ah well no problem then, because MUA-26 is itself just a block and that's how it gets on the dashboard.  

This is possible at any context level (site, category, course) using the "addinstance" capabilities for each activity and block.

https://docs.moodle.org/32/en/Managing_activities#Reducing_the_number_of_activities_listed_in_the_activity_chooser

You could change them for the role everywhere in the site, or use overrides at any context level.

The starting point is that Moodle must integrate well with these systems, because a lot of places are coming to depend on them and both Google and Microsoft have products called Classroom that aim to replace Moodle's richness with a dumbed-down idea of an LMS and online learning.

The second point is that the existing integrations out there (partly because of the plugin constraints) are not very good at all, and currently make Moodle look like a poor option.