This page outlines improvements and technical debt that needs to happen to the OpenLMIS-UI. Tickets listed on this page are may not be ready for work, and can actively be picked up once placed on a backlog grooming page.
Bootstrap Resources
When working on OpenLMIS design or user interface issues, please consult the following resources.
- OpenLMIS design documentation outlines OpenLMIS recommended workflows, form layout, and writing guidelines. Individual designs may break these rules, but the OpenLMIS community recommends against this.
- Wire-frame template library which should be used to start mocks-up and quickly work through content designs.
- OpenLMIS Reference-UI Styleguide which illustrates basic UI styles, layouts, and components - along with the working code to generate them. Use this resource if creating hi-fidelity mockups or working OpenLMIS-UI code.
- UI/UX WTF is a place to catalog inconsistencies that are not ready to become a JIRA ticket
UI Github Repositories
Features Backlog
Tech Debt & Bugs
Consistency
(NR: OLMIS-1354 & OLMIS-2510 might intersect with this, but doing some work across all services here would be good)
It is too easy to click off the modal in the add screen of stock management and loose all the work the user has done
Design
Performance
- Establish data budget
- Sonar to track application size - vendor libraries, html, translation strings, image sizes
- Sonar to track download time on 3g connection
- Sonar unit test coverage
- Sonar module dependency tracking
Offline Support
- App Cache update detect and notification
- OfflineService component to simplify offline development
- Less frequent offline status check (reduce UI bandwidth)
Extensibility
Important before 3rd party starts working with codebase
Development Tools
- Set up Javascript linter
- Set up Sass linter
- Dgeni-example JSDoc and KSS toolset
- Cordova Android application compiler