This should resolve everything in the first milestone. Chiefly, it resolves #3.
As @Wright4TheJob the job and I discussed, this is more of a "gesture" towards the salient data points the dashboard is meant to represent and how to order the visual hierarchy, not really a "mockup" in the truest sense. But it did help, even in just structuring the markup, to think through some of those choices, what data should be prioritized, how certain things should be grouped, etc. It also really drove home the fact, for me at least, how badly we need to get some graphic/UX designers on board to help w/ this kind of stuff.
In addition to what David & I worked on yesterday, I spent a little time last week and today updating the README to resolve issues #1 and #9, but I bumped #4 back to the second milestone. It would be great to think about ways to integrate some of this documentation into the main website, too, together with the info in the Open Design Workshops repo. I feel like that could help for long-term reuse of some of this boiler-plate, as well as make it more navigable for farmers and other people less familiar with GitHub, all of whom I hope we can start inviting to these workshops as soon as possible.
I'll probably go ahead and merge stuff today or tomorrow, but @pterygaphykion and @paul121, let either of us know if you'd like a chance to review the specific changes and decisions here.
This should resolve everything in the first milestone. Chiefly, it resolves #3.
As @Wright4TheJob the job and I discussed, this is more of a "gesture" towards the salient data points the dashboard is meant to represent and how to order the visual hierarchy, not really a "mockup" in the truest sense. But it did help, even in just structuring the markup, to think through some of those choices, what data should be prioritized, how certain things should be grouped, etc. It also really drove home the fact, for me at least, how badly we need to get some graphic/UX designers on board to help w/ this kind of stuff.
In addition to what David & I worked on yesterday, I spent a little time last week and today updating the README to resolve issues #1 and #9, but I bumped #4 back to the second milestone. It would be great to think about ways to integrate some of this documentation into the main website, too, together with the info in the Open Design Workshops repo. I feel like that could help for long-term reuse of some of this boiler-plate, as well as make it more navigable for farmers and other people less familiar with GitHub, all of whom I hope we can start inviting to these workshops as soon as possible.
I'll probably go ahead and merge stuff today or tomorrow, but @pterygaphykion and @paul121, let either of us know if you'd like a chance to review the specific changes and decisions here.