STAC API + dashboard configuration discussion recap

[leothomas]

Some notes from this morning's discussion on the dashboard evolution project's configuration:

Having identified the need for the dashboard to be dataset agnostic, @danielfdsilva will put together a proposal detailing a configuration repository (github) which will contain dashboard content (stories, thematic areas, titles, etc) as markdown. Metadata relating to how to display datasets will be stored here.

As we move forward with the implementation of a STAC API, in order to make temporal and geographic extent discoverable, @anayeaye will put together some issues/roadmap for setting up a prototype in order for dashboard development to test against.

@abarciauskas-bgse has been working a prototype that exemplified how the dashboard might interact directly with the STAC API.

Next steps:

• Develop ADR(s) + Issues for STAC API instance
• Decide on namespace for code repo and scaffold:
• Frontend repo
• Config repo
• Decide on backend configuration: should tiling API, STAC API, and ingestion pipeline be in the same repo, organized as microservices? or 3 separate repos?
• Add documentation for how to setup and use the config repo + setup prototype