UI DESIGN DOC

Requirements
    - Responsive but favoring larger screens primarily
        - Smaller screens will be able to do everything but the layout is not the primary one
        - Service techs have an ipad or notebook
        - Anticipate a list of things each role needs immediately in front of them and try for that
    - componentized UI elements so can re-use and mix and even support customizing with user defined layout
        - So for example a customer list is a self contained subset of a list widget and can be plunked down anywhere required
        - This will save me time so identify the "types" of ui elements (picklist, filterable data list, entry form etc)
            - Then can build specific versions of the types identified like a client list is a specialized filterable data list etc.
                - If a list then it also knows which element is selected or a list of selected elements so other widgets can operate on it
            - A menu or command widget that can be inserted into another widget, i.e. a part picker for a workorder part list widget or elsewhere a part is required
            - This way I'm only making a few UI objects, not a new one for every single element.
                - Kind of making the pallet first of all required objects then I can "paint" with them on to the UI without getting bogged down in minute details every time I make a form
            - UI elements should be responsive and generic enough to work for many different use cases
            - they should be rights aware and mode aware (editable, read only) enough to handle all that without recoding again and again
            - the page or shell or whatever that holds the widgets should be end user customizable from a widget pallet.
            - The more self contained the widget the more useful

    - Most people seem to prefer WBI over RI and the reason always seems to be RI is too simple or requires too many clicks
    - So plan on the bigger screen layout being the main UI and smaller screen secondary    
    - I want things to be simpler and cleaner than it seems many people do so beware of that tendency
        - People don't want to have to open sub screens any more than absolutely necessary
        - Make sure a screen contains as much as possible to complete it on one screen
    - Clean interface with good negative space but not dumbed down too much
    - Pro-marketing style, stuff that makes it easier to sell
        - emphasize simple fonts with good contrast
        - Blue is a good colour, no purple or pastels
    - DAshboard / customizable UI
        - Ideally people can see as much detail as they want or remove unused ui widget elements
        - So, for example on the dashboard they can customize by plunking down a client list widget, adding a "My workorders" widget for a tech
        - or for a Ops person they can plunk down on their dashboard a current server status widget or active jobs widget etc


Graphics and themes for AyaNova
    - No bitmap graphics, vector only!!
    - I like material design but it will remain to be seen for the front end.
    - For the manual and docs will use material theme with MKDOCS generator.


LOGO
    - Need to standardize on a logo and stick to it from now on
    - Simple and clean (script AyaNova used for RI is maybe out)
    - Single colour canucks blue with green contrast if absolutely necessary (don't make it necessary)
    
COLOURS
    - Canucks colours of course, Blue primary and green secondary. RI already uses them, get the hex codes there.
    - No indigo or pastels