4 ms·

Thanks! Will do. BTW, I'm fairly certain that the "github submit a pull request" model doesn't work for UI/UX. Consistency and tone matters, as does integratin

Thanks! Will do. BTW, I'm fairly certain that the "github submit a pull request" model doesn't work for UI/UX. Consistency and tone matters, as does integrating feedback and cycling it. The idea of hitting issues piecemeal without some kind of overarching strategy feels like a recipe for failure. Unless you have unified brand guidelines, a UI component library etc, such an effort seems like an exercise in futility.

xipho 6y ago
That's a good point re PRs. One possible way of interacting would be to explore the API, and develop a proof of concept UI element with a bit of functionality, that plays off it. Perhaps in a context like this: https://github.com/jlpereira/tw_api_test https://github.com/jlpereira/tw_api_test. We do have use various semantics throughout the project, randomly documented. Contributions to how best to organize and get beyond this are also welcome, along the lines of this issue: https://github.com/SpeciesFileGroup/taxonworks/issues/85 https://github.com/SpeciesFileGroup/taxonworks/issues/85.