On Dashboard definitions - what about this (describes how dashboards vary with a dashboard design space). https://research.tableau.com/sites/default/files/DashboardsConspiracy_final.pdf
On JavaScript - add the data as a JavaScript code block (see other idioms) then it is clickable, expandable (usable!).
As one of the objectives is to add interactivity, close integration with JS is important and you may introduce JS as a means of achieving this.
Great - maybe:
As a visualization designer / developer
I would like to who provide a broad range of visualizations for the RAMPVIS VIS infrastructure
So that RAMPVIS volunteers can see their various data sets in meaningful and informative ways.
Reading through, reminds me that these need to be accessible.
I like the bullets, but would also like a user story:
As a visualization designer / developer
I would like to who provide a broad range of visualizations for the RAMPVIS VIS infrastructure that are interactive and rendered quickly and reliably through a standard browser
So that RAMPVIS volunteers can see their various data sets in meaningful and informative ways.
I Guess this. is really about how D3 can be used in the context os similar user stories in the future. What would you recommend knowing what you know now. Or how might D3 be developed to make what you were trying to do more doable?
There are some gaps, but this is an important one and the reflection is already useful.
Please see comments and tidy up / complete.
Remove notes and unpin markdown!
Try to add scientific examples rot show application and range
Try to include colleagues in the reflection and discuss - they have a wealth of experience and valuable views.