View Source

This document presents sample goals for OpenLMIS v3.3 — This page is a conversation starter, and shouldn't be used an official reference

OpenLMIS > UI Goals for 3.3 > image2018-2-12_12-39-18.png

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

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

Remaining work aside from documentation is:

- Making changes outlined in this ticket is probably a good idea (even if the v7 architecture isn't deemed valuable)

Issues to groom but not take action on

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

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