List view
Dashwise is almost a year old at this point. The idea has been around for even longer than that. It was always the goal to integrate with as many external services as possible. Ever since starting to work on Dashwise, I've only imrproved my coding skills. The next big version should finally get closer to achieving the vision by allowing dynamic yaml-based integration declarations. In addition to that I'm expecting a performance boost due to the ongoing migration from Nextjs to React/Hono. This should also reduce resource usage. Dashwise will eventually become more than a dashboard. News and Notifications were only the beginning. Thanks for being interested in the project.
No due date•1/4 issues closedConfig 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•1/1 issues closedCurrently, 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- No due date•4/7 issues closed