Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The Open edX micro-frontend framework has some problems and growing pains which we’re trying to solve in a variety of ways. This is an attempt at cataloging those so we can understand which of them the frontend composability project (FC-0054) should be responsible for fixing, vs. things like the frontend plugin framework or improvements to Tutor, which are both arguably outside the scope of this work.

  • Reusable Component Consistency

  • Shared Organism (header/footer/navigation) Consistency

  • Branding/Styling Consistency

  • Dependency Consistency

  • Developer Cognitive Load

  • Operator Cognitive Load

  • Maintainer Cognitive Load

  • Build performance and efficiency

  • Runtime performance and efficiency

  • Dependency Maintenance Burden

  • Cross-MFE Composability

  • MFE Overrides

  • Limited Non-Invasive Customization

  • Adding new MFEs

  • Multi-tenancy Configuration

  • Development Resource Consumption

  • Library Development Complexity

  • Testing Standards Consistency

  • Technology Consistency

  • Documentation Consistency

  • Documentation Quality

  • Repository Proliferation

  • Deprecation Standards

  • Branding Complexity

  • No labels