QASM is a single-serve web application that runs using React and Electron, with the ability to run customizable QA or labeling jobs from a local host, a packaged windows .exe, or a statically hosted S3 website.
There's a configuration file which gets used for the default build command, and that tends to get changed when adding new PRs/testing new features.
I think the following setup would probably be good:
A default configuration which showcases one of every feature/page (ideally on some data in a public test bucket for when we open source this) (alternatively, a config for every feature in a folder, or some mix that makes sense)
A warning when building the default configuration that at least requires user confirmation, or better, presents a list of available configurations
A directory of other sample configurations
A git-ignored directory for testing/user ones with a command that specifically points to those
There's a configuration file which gets used for the default build command, and that tends to get changed when adding new PRs/testing new features. I think the following setup would probably be good: