Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create clearer UX design and release guidelines #424

Open
jmakowski1123 opened this issue Aug 15, 2022 · 0 comments
Open

Create clearer UX design and release guidelines #424

jmakowski1123 opened this issue Aug 15, 2022 · 0 comments
Labels
epic Large unit of work, consisting of multiple tasks

Comments

@jmakowski1123
Copy link

jmakowski1123 commented Aug 15, 2022

Problem

MFE authors are currently free to design UX as they see fit. Even with the use of Paragon components as building blocks, this can potentially still lead to a lack of consistency between pages.

Product/Platform Value

A consistent experience across the platform is expected of any modern application. Not having one detracts from the presentation.

Acceptance Criteria

This would include the definition and communication of a gated process where MFEs are only adopted for official release when UX cohesion is considered to be sufficient.

Related or in-progress work

Contingencies

@jmakowski1123 jmakowski1123 moved this to Backlog (in tentative prioritized order) in Frontend Working Group Aug 15, 2022
@jmakowski1123 jmakowski1123 changed the title Create clearer UX guidelines Create clearer UX design and release guidelines Aug 15, 2022
@jmakowski1123 jmakowski1123 moved this to Backlog in Open edX Roadmap Sep 20, 2022
@arbrandes arbrandes added the epic Large unit of work, consisting of multiple tasks label Oct 6, 2022
@arbrandes arbrandes moved this to Backlog in Frontend Working Group Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Large unit of work, consisting of multiple tasks
Projects
Status: Backlog
Development

No branches or pull requests

2 participants