General Guidelines

Adhere to the principles

1. Always think about configurations

As we built Navida Pro with the configurability in mind, while design and develop the software components , keep your thoughts clear on how to externalize the configurations. As a thumb rule

a) All backend configurations should be part of the application.properties and the values should be able to overridden by the helm chart values. These configurations should be also tackled in way that, it should be properly documented, and fine tuned for the further environments. Keep in mind that the pre-prod env and the production env are managed via helm chart deliveries.

b) All FE configurations should be part of the plugin configuration file / AOK configurations that can be dynamically changed in CMS.

For example : If you want to keep a URL, even if that is not going to change per AOK / or based on env , it is always better to keep that in the plugin/AOK configurations in CMS . This will give additional control and customisation capabalities to the platform .