| | 1 | = !BluePrint: User Interface = |
| | 2 | [[TOC]] |
| | 3 | |
| | 4 | == Requirements == |
| | 5 | 1. Users should be able to easily navigate to their desired functionality |
| | 6 | 1. Users should be presented with the minimum possible number of navigation options / menu items (while still being able to easily navigate to their desired functionality) |
| | 7 | 1. There should be a standard layout between different "resources" |
| | 8 | 1. Page Elements which require heavy server load (Maps, Advanced Search Forms, etc) should only be loaded when they are needed |
| | 9 | 1. It should be clear to a user what a specific page is required for |
| | 10 | |
| | 11 | == Create Read Update Delete (CRUD) (+List Search) Page Layout == |
| | 12 | |
| | 13 | === Design === |
| | 14 | Some designs for improving the page layout have been documented and discussed here: |
| | 15 | https://docs.google.com/document/d/15TGk9H_iFKIz2VdTeOM6A38Sht0KTFP9aM51aqeLP30/edit |
| | 16 | |
| | 17 | === Tasks === |
| | 18 | This is a draft list of some tasks which could be implemented to improve the page layouts: |
| | 19 | ''Easy'' |
| | 20 | * List pages should be replaced with Search pages |
| | 21 | * All Search pages should have a single text search on their simple search form |
| | 22 | * There should be a button to show a (pre-loaded) create form on the search page |
| | 23 | * Records should open in read view by default |
| | 24 | * There should be a button to toggle between the read view and an edit view |
| | 25 | * When a record is saved (updated) the next page should be the read view for that record. |
| | 26 | ''Hard'' |
| | 27 | * The advanced search for should only load when it is viewed |
| | 28 | * There should be a button to toggle between the rheader and an edit form |
| | 29 | * When an item is opened from a list, it should be loaded by JS on top of the list page. When it is closed, the list should refresh to show the changes to the item (Or is there a better way to achieve this?) |
| | 30 | |
| | 31 | == Module Index Pages == |
| | 32 | === Design === |
| | 33 | There is a draft design document here https://docs.google.com/document/d/1EKt6lSs1d2kuyCfCM8hQZdeL2zfCJ2JKvPU-dm81TUQ/edit with some ideas for module page content. |
| | 34 | |
| | 35 | ===Tasks === |
| | 36 | * Predefined DIV classes to be able to create 2-5 panes in which content can be inserted |
| | 37 | * Simple Search box which doesn't display the unfiltered results by default & opens both search results &/or Advanced Search in a separate page |
| | 38 | * 'Top 5' either Actionable Items or FYI 'recently added/modified' for one or more resources (with hyperlinks to their details), with a 'More' button to see the full list |
| | 39 | * KPIs (Key Performance Indicators) |
| | 40 | * Maps only included where they add value - e.g. 'Recent Incidents' clearly adds value, whereas 'My Warehouses' far less so. |
| | 41 | |
| | 42 | === Questions === |
| | 43 | * Should the ability to search multiple resources be done as separate search boxes or a single box with a dropdown to select the resource? |
| | 44 | * Should the initial default page for a user be filtered for their Organisation (which could be their Branch, so is a reasonable default for many of both HQ & Field staff, where Branches are used) or should it be a set of New User instructions explaining the usage/terminology of the module (with perhaps a diagram) & a clear 'Personalise this Page' option which allows the user to configure the default filter settings for the page (e.g. Region/Country/Organisation/Branch/Office/Team) |
