Questions we should ask

[alexeyraspopov]

Q: What the main purpose of creating yet another boilerplate?
A: We want to have a set of reusable and reliable configs and tools that will improve our development process and speed up bootstrap phase.

Q: What this boilerplate suppose to create?
A: Initial structure, set of configs and templates for developing single-page application.

Q: What external libraries/tools will be used to do so?
A: Obvious decision of 2016 (minimal stack): React, React Router, Babel, ESLint. Still, they should be discussed and the decision should be well explained.

Q: How we're going to maintain this project?
A: At least there should a monitoring system that will check dependencies updates.

Q: How we're going to monitor dependency updates/pulse?
A: We can use services like BitHound.

Q: What types of tests should be covered by the boilerplate?
A: Minimal requirements: unit, functional and UI tests.

1. What user scenarios this boilerplate will cover?
2. How actual projects can be updated once boilerplate will be changed?
3. Should this boilerplate be opinionated or agnostic in questions about project structure?
4. Should this boilerplate cover project deployment?
5. How the process of library/tools promoting should look like?
6. What existent tools/bootstrap should be reviewed if we want to get the best set of features and not to make the same mistakes.