Create a Quarkus extension for dashbuilder. It should scan files from classpath with *.dash.(yaml|json) extension and render then. User can configure dashbuilder by:

• Setting up a base web context for dashboards 
• Manually mapping dashboards

Here's a sample configuration that could be done in application.properties

quarkus.dashbuilder.path=/db-custom
quarkus.dashbuilder.dashboards=dashboard,other_dashboard.dash.yaml 

 
In dev mode:
  * On dev console a link should take users to the configured dashbuilder web context

• Dashbuilder files should be registered for auto reload

 
 
Dashbuilder web content should be part of the finished Quarkus app.