JuanCodeAtATime
commented
3 years ago The codertheme example looks great! I’ll put together two mockups. One for desktop view and another for mobile or tablet view.
Also, in our effort to make the system responsive/mobile-friendly, how small of a viewport do we want to support?
Specifically, are we expecting users to use mGis on devices no smaller than a tablet or do we want to make the responsiveness support viewports as small as iPhones or Androids?
Because of the purpose of this system, I would lean toward making the responsiveness support viewports no smaller than tablets (ie, iPad).
bluenevus
The Dashboard tab will be the default landing page and all users will have that page as a minimum. This presents the general stats of the project. If filters are applied, those filters must be clear as to what was applied in terms of criteria to result on this page in plain English. There should be NO scroll bars so it needs to all go on the page and dynamically resize
the timeline from onwatch will go here
Number of Facility Groups Number of Facilities Number of Facilities Active Number of Facilities Inactive Number of Assigned Users Number of Users with Tasks Assigned vs Not assigned Number of Users with Issues Assigned vs Not assigned Project Status Count (enumerations) Percentage Project Complete Number of Tasks Number of Tasks Complete vs Incomplete Percentage Task Complete vs Incomplete Percentage of Task Overdue vs On Schedule Overdue Task Completion Percentage Milestone Task Count (enumerations with milestones that have data) Milestone Percentage Complete Number of Issues Number of Issues Complete vs Incomplete Percentage Issue Complete vs Incomplete Percentage of Issue Overdue vs On Schedule Overdue completion Percentage Issue Type Count (enumerations with issue types that have data) Issue Type Completion Percentage
burndown chart on completed tasks and tasks remaining https://en.wikipedia.org/wiki/Burn_down_chart https://en.wikipedia.org/wiki/Burn_down_chart#/media/File:SampleBurndownChart.svg this will take the time period of what is filtered (like what would show on the gantt) y axis is number of tasks. x axis is timeline. this gives a visual of how quickly we are closing tasks
bar chart on task count based on percentages y axis is number of tasks. x axis percentage complete in 25% intervals. 0, 1%-25%, 26%-50%, 51%-75%, 76%=99% , 100% this gives a visual of how many tasks fall into these completion buckets.
Burndown chart on completed issues and issue remaining https://en.wikipedia.org/wiki/Burn_down_chart https://en.wikipedia.org/wiki/Burn_down_chart#/media/File:SampleBurndownChart.svg this will take the time period of what is filtered (like what would show on the gantt) y axis is number of tasks. x axis is timeline. this gives a visual of how quickly we are closing issues
bar chart on issue count based on percentages y axis is number of issues. x axis percentage complete in 25% intervals. 0, 1%-25%, 26%-50%, 51%-75%, 76%=99% , 100% this gives a visual of how many tasks fall into these completion buckets.
I would imagine some of the vs being pie charts, the percentages being speed gauges, other hard numbers being like you see in the link above, the enumerations being a horizontal bar chart, burn down charts of task and issues https://www.projectmanager.com/blog/burndown-chart-what-is-it etc etc. Eye candy in a report
I would imagine this page looking something like this https://coderthemes.com/hyper/saas/index.html
Though all of these are available by default, the user should be able to hide or show these as their preference and on login that preference remain to view only those they choose to be part of their dashboard