[P1BIGROCKS-2426](https://jira.il2.dso.mil/browse/P1BIGROCKS-2426) As resellers come on board, Big Bang will need to provide guidance on how to integrate new packages into Big Bang. This is independent of the maturity level of the application since the reseller may want to add the package on top of Big Bang, but utilize all the features as if it were part of Big Bang. This epic would document the development and deployment of a new package from start to fully integrated into Big Bang. This includes the following categories: - Selecting and syncing with an upstream Helm chart - Using BBs package and umbrella pipelines - Adding CI tests (e.g. cypress) - Adding Flux resources for GitOps - Integration with service mesh - Integration with monitoring stack - Using Big Bang to create namespaces, secrets, and default values - Enabling database configuration values, including running an internal database for CI - Enabling storage configuration values, including running Minio for CI - Enabling SSO configuration values - Adding network policies that comply with Big Bang requirements - Identifying OPA Gatekeeper violations and fixing them - Adding Big Bang documentation (e.g. Architecture, licensing, CPU/memory requirements) > The idea would be that the developer would be able to do ALL of the above in a `sandbox` repo using a 2nd helm chart for Big Bang flux resources and values. If the package were to graduate and move into Big Bang, it should be seamless to copy/paste the files into the right locations.