UI Goals for 3.3

UI Documentation

• Login required on start-up if not ui-components
• KSS focused documentation style really isn't helpful and is hard to edit
  • Would remove KSS
  • Move content to markdown files
• Add "generic workflow" documentation page to UI-Styleguide (would use standardized terms)
• Incorporate JSDocs into same styleguide
• Change page loading structure, so code examples are "run-able" using the Javascript framework of the UI
• Make JSDocs Components pages have executable examples, so UI components can be debugged/demo'd outside of business logic in screens

UI Extension

• Move OpenLMIS branding to reference-ui — which will then act as demo for implementers about how to extend the OpenLMIS-UI

v7 Architecture

Remaining work aside from documentation is:

• OLMIS-3799 - Getting issue details... STATUS
  • Making changes outlined in this ticket is probably a good idea (even if the v7 architecture isn't deemed valuable)
• OLMIS-3800 - Getting issue details... STATUS
• OLMIS-3801 - Getting issue details... STATUS
• OLMIS-2443 - Getting issue details... STATUS
• OLMIS-3802 - Getting issue details... STATUS  

Issues to groom but not take action on

Technical Debt

• Fix technical debt in navigation component
  • Issue is navigation component implementation is flawed
    • Auth built into navigation
    • Navigation only shows top level
    • Need for menu content customization
  • This is important because being able to add new tabs is currently done by manually updating HTML — where as dynamically creating navigation menus is much better for extendability
• Remove code that uses local storage — replace with PouchDB
• Remove/Deprecate openlmis-ui-layout repository since v7 architecture shows separation of presentation and logic

Batch Requisition Screen

This feature is currently really badly designed and created. Here are some changes that need to be made

• Use period & district to select requisitions to approve
• Figure out horizontal virtual scroll