IanMayo
commented
6 years ago Thoughts on parts to cover:
- introduction to intention
- tech demonstrator:
- use of browser storage
- ReactJS performance with large datasets
- browser-based export to PDF
- offline-first client-side only application (no server component)
- benefits
- future proof
- versatile, reconfigurable event library
- safe (nothing is "installed" on client PC), app has no direct access to local storage.
- tech demonstrator:
- overview of layout
- left-hand diary
- entries broken down into groups
- adding an entry
- fill in, validation, accept
- adding via widget (mast movement)
- auto-complete to generate entry
- editing existing entries
- resize diary, for review
- double-click to edit
- exploiting data
- filtering list
- display of course speed
- exporting data
- data persistence
- open new tab? Will that work with PouchDB?
- customizable UI. Link to doc that uses other UI template?
- what's next?
- seek endorsement, then formalise project
- identify stakeholders
- formal requirements collection
- gap analysis
A walkthrough would quickly demonstrate the app's capabilities to interested parties.
Ian to produce script.
@Morphexe could start choosing a lib to use. One constraint on the walkthrough is that we'd like the user to be able to interact with the app during the walkthrough - such as type ctrl-G
We used Shepherd for Lesco. It seems ok: https://github.com/HubSpot/shepherd
Once Ian has produced the script, @Morphexe can check it's covering all of the features we've implemented.