UI Goals for 3.3
This document presents sample goals for OpenLMIS v3.3 — This page is a conversation starter, and shouldn't be used an official reference
UI Documentation
Login required on start-up if not ui-components
KSS focused documentation style really isn't helpful and is hard to edit
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:
Issues to groom but not take action on
Technical Debt
Fix technical debt in navigation component
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
OpenLMIS: the global initiative for powerful LMIS software