EnxDev commented on issue #37016: URL: https://github.com/apache/superset/issues/37016#issuecomment-3760293141
> This should be put up for a DISCUSS thread... in general I love the idea, but there are some things to sort out. > > I've been wondering about an alternate universe where we REMOVE the welcome page, and replace it with a pre-rolled dashboard. Then you could see all your assets, customize the layout, use filters (edited between dates, owned by filter, etc). At the end of the day, Mine/Recent/Favorites are really just filters. > > Dashboards would need a few new features to make it COOL, but I've been wanting many of them anyway. > > At the very least Dashboard Components and Welcome Components would likely have a lot of compatible components and layout zones. I think we're converging on the same vision from different angles. What I'm calling "Homepage Builder" could really be a more generic "Utility Page Builder"; a way to create pages composed of widget-extensions (asset lists, KPIs, announcements, embedded charts, etc.). The current "homepage" is just ONE instance of such a page; perhaps a pre-configured default. This aligns with your Dashboard idea: - Dashboard = page with chart-extensions + filters - Utility Page = page with widget-extensions + filters - Both could share the same layout engine and extension system The user (or admin) simply chooses which page is their landing page. At that point, whether we "remove the homepage" or "make homepage a utility page" becomes a semantic distinction; the underlying infrastructure is the same Generic Page Builder. Should we reframe the SIP around this broader "Utility Page" concept, with the current homepage as the first use case? Also I'd like to clarify an architectural distinction that I think is important: <img width="554" height="404" alt="Image" src="https://github.com/user-attachments/assets/5474b3eb-6e0d-49ba-be45-63d0b918d6c5"; /> While I agree that Dashboard and Utility Pages could share the same underlying layout engine (Generic Page Builder), I believe they should remain conceptually separate: **Dashboard** = Superset's core: charts, slices, cross-filtering, data analysis **Utility Page** = Organizational layer: asset lists, KPIs, announcements, navigation The "Homepage Builder" I'm proposing is really a Utility Page; focused on helping users organize and navigate their Superset environment, not on data visualization. An "Embedded Chart" widget could bridge the two worlds, but the core Dashboard functionality (cross-filtering, drill-down, query caching) shouldn't be mixed with utility widgets. This separation keeps: - Dashboard focused on its strength (data viz) - Utility Pages lightweight and purpose-driven - Clear UX for users ("Am I analyzing data or organizing my workspace?") Does this distinction make sense? Happy to discuss further. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
