List view

• Move away from userConfigs

  Config files are great. Until they're not. And I think dashwise may have reached that state where you have to choose one over the other in order to move forward. A more decisive approach is to use pageConfigs. Users can have multiple pages. A page (config) should: - use a template - not be used as a replacement for a database

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• Integrations makeover

  Currently, integrations are hard-coded. As a way to declare them dynamically, declarative yaml files should allow for declarative usage and development of integrations. For example, when an integration wants to publish a widget, it advertises the widget by using a widget template and filling it with data from the integration's endpoints.

  No due date

  •0/1 issues closed
  0% complete1 open0 closed

• News page

  No due date

  •2/7 issues closed
  28% complete5 open2 closed