Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||||||||
|
|
|
|
||||||
|
||||||
|
Notes:
|
Had Alan on the meeting with Chuck and I today. We wanted to get him in on the projects and getting a high level awareness of what is going on. We started out with the camp adilas project and where that is in the development cycle. Chuck did a demo for Alan and they went back and forth with ideas and questions. Both guys are excited to work together on the different projects. After that, we rolled into a session talking about some snow owl theme (current look and feel inside the system) changes and where that could go. We looked at some mock-ups for the classic homepage and then then into user permissions and profiles. See the screenshots for some of the new ideas. Still in concept mode but definitely coming. We are thinking of putting a facelift on a number of the high usage pages or places where it looks older or more outdated. We are trying to change up the user experience and make it better and better. We talked about user profiles, permissions, and allowing templates and presets. We talked about having tabs, vertical tabs, accordion displays (ways to show/hide additional data), floating submit buttons, putting help files and summaries under the gear icon on the side of the page, stash and go with a sock drawer type concept, and even changing the page flow to help the users. Currently, they do an action and may end up on a different page or on a success message. They then have to navigate away to another place or do some other action. Good page flow will really help. A couple of other topics were mixing tasks and skills to get a job/project done vs a full stack developer (able to go from top to bottom or point a to point z - the whole thing). We may need to help some of our developers get really good at certain tasks to help with efficiency and productivity. We also talked about light messages and helping to lightly push our users towards the newer look and feel and/or new functionality options. We know that we have to be careful there, but we will make some attempts when ready. After the meeting, Alan and I talked briefly about some of our developers and where we are headed and who could help in what regard. New note added on 1/8/20 - Danny Shuford contacted me and asked that we make the view only permissions easier to get to. I showed him some of the concepts of where we are going with user profiles and permissions and said that I would add a note to this element of time. The original idea came from Kelly Whyman and Danny brought it to us. Great idea. That may require some special code just because the view only permissions are not standalone permissions. They require the main permission and then the view only permission to limit the options. |