Roadmap to a beta
The idea of a roadmap for the VF came up today, so I wanted to sketch out some ideas for that.
(nB: I think we can only roadmap until a beta, because after that we'll be getting some serious feedback and much could change -- or nothing could change: job done.)
What do we need for a beta?
Before we can make the roadmap, we need to know what we need in the beta.
- Documentation
- Public facing site
- Initial docs
- Boilerplate pages
- Contribution guidance
- Browser support guidance
- Document our governance
- Migration guidance from EBI VF
- Note on how EMBL VF differs from EBI VF
- Core VF CSS + JS
- EMBL.org instance
- EBI instance
- Demo EBI service instance (Interpro?)
- Demo 3rd party instance (Uniprot?)
- Tests
- Visual regression test
- Others? Browser testing?
- Initial acceptance testing (ux, stakeholders, developer ux, etc.)
- Integrating with the Content Hub (this might be super simple)
- Host virtual and/or physical outreach
- Add to npm
- Proof of concept for in-browser linting tool
- Integration tests (with Angular, Bootstrap, et al)
- ALL THE (mvp) PATTERNS
- Some support for react, angular
- Have a method for adding more patterns after release (v2.0.X)
- Have (and document) a method to add your own patterns
- Pattern generation tool
Notes:
- Icons will be a separate repo, I think?
- We need to consider UX guidance