Additional info for stakeholder

Currently web map displays are achieved through the webmap.config file which only applies for the admin panel. We have to make the decision where the additional info on a stakeholder is stored. (ie. About us, Vision, Logo URL, Hero image URL, etc)
1. in the stakeholder table
+ obviously fast querying and simple structure
- not much flexibility
2. in an extra config table
+ benefits of many different parameters possible
+ maps and custom views could be created (treating stakeholders like an object rather which means even a custom map view could be a stakeholder
- slower queries and more complex structure (seems to not be an argument since most will be served by the API)

We would need additional UX to be able to cater for that. Each stakeholder object should be able to be customizable.


Start by reviewing webmap.config and the admin panel context, then resolve whether stakeholder information belongs in the stakeholder table or an extra config table. Define the required customizable fields and UX before implementation; done means the storage approach and stakeholder customization behavior are agreed.

Written by the indexing model from the issue text.