...
Actor | Use Case | Proposed By | Notes |
|---|---|---|---|
Deployers | almost every customer wants to modify the footer content (often also the header) | eduNEXT | |
Deployers | online academies (gathering from our saas offering) very often ask us to add additional fields to the Authn registration page. | eduNEXT | |
Deployers | online academies offering need to present the same additional fields from the Authn registration to the account settings page. | eduNEXT | Isn’t there already a basic mechanism for doing this? How does it fall short? |
Deployers | University of Michigan wants to make redirections from the learner dashboard to a custom policy acknowledgment/acceptance page. (published in the issues of the mfe) | eduNEXT | |
Deployers | Spanish universities want add more filtering options to the course emails page (frontend-app-communications) | eduNEXT | I’m not sure what this means. Is there a reason why their choices wouldn’t be desirable by everyone using the app? |
Deployers | Spanish universities authors want to add more buttons to the html editor (tinyMCE) to make iframe and other embeddings easier. | eduNEXT | |
Deployers | Spanish universities want to add an extra component to each block in the course content to gather feedback on the quality of the component. | eduNEXT | This feature feels like a cross between something that should be core, but currently is not and the ability to extend the platform. Perhaps the mechanism for plugging a feedback mechanism into every block should exist. Perhaps this should just be a platform feature. |
Deployers | Pearson uses a side navbar block that want to add to the learning MFE so learners have easy access to the course navigation tree. | eduNEXT | |
Deployers | Organizations would like to add custom tools to courses and have both the tool and it’s configuration be installed optionally. | This use case is captured based on Braden’s work to demonstrate his plugin proposal. | |
Developers | As a developer I want to package a modern frontend with customizations to the Open edX platform backend. | Glib Glugovskiy capturing this in relation to the work you are doing to redesign the video block to use a React-based front end. | |
Deployers | As a deployer, I want to be able to hide items from frontend views that are not relevant to my deployment. Some examples from the Learner MFE:
| Summarizing a request that came from Meredith Davies at MIT. | |
“Learning Assistant” | |||
Zendesk | https://github.com/openedx/frontend-app-learner-dashboard/tree/master/src/components/ZendeskFab | ||
DeployersDevelopers | As a developer, I want to only deploy and maintain the frontend plugin that my team has ownership of, while another team/developer is responsible for the Host MFE they have ownership of. | ||
Developers | As a developer, I want to be able to replace any default content (main branch content) of a host MFE with my frontend plugin. |
Proposed Schedule
...
Attribute | Poor | Decent | Solid |
Maintainability | Requires maintaining a substantial fork | Better with notable flaws | Requires only Installing and enabling custom plugins |
Flexibility | Restrictive, fixed options. Easy to hide things, but hard to add or change existing things | Better with notable flaws | High degree of control. Can add, update and delete components |
Approachability | Off the beaten track, surprising, steep ramp | Better with notable flaws | Simple and familiar patterns, reasonably easy to grok, few surprises. |
Security | Introduces new attack vectors. | Better with notable flaws | Meets our existing security patterns and requirements |
Performance | Significant performance tradeoffs, difficult to cache, large apps, poor sharing of libraries | Better with notable flaws | Optimized app sizes, maximal sharing of libraries, high-level of cachability at edge and client. |
Accessibility | Hard to implement our standards for a11y, i18n, and l11n. | Better with notable flaws | Standards achieved via existing patterns |
Operability | Must release to change any component. Customizations are statically delivered | Better with notable flaws | Individual components are independently updatable. Runtime configuration is available. Split tests are possible. |