You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/07/27 22:08:51 UTC

[GitHub] [superset] ktmud commented on pull request #15915: [DISCUSS] - Moves the SQL Lab menu before Charts

ktmud commented on pull request #15915:
URL: https://github.com/apache/superset/pull/15915#issuecomment-887867118


   Personally I think it'd make more sense to order by usage than workflow:
   
   1. **Most users don't need the full workflow:** even for Data Scientists, they seldom work through the whole workflow in one go---IMO having the full workflow in the right order is less important than having easiest access to the most used steps in the workflow.
   2. **Different users have different workflows:** "Data -> SQL Lab -> Chart -> Dashboard" is just _one_ workflow of _some_ Data Scientists. Some more frequent workflows are:
      1. "Chart -> Dashboard"---for Data Scientists who only use pre-configured and shared datasets (which is probably something Superset should encourage), in which case one may argue the Data tab should be hidden into "Settings" (like [Redash](https://redash.io/help/user-guide/getting-started) does).
      2. "Dashboard -> Chart -> SQL Lab"---for dashboard viewers who are also interested in how the underlying data were computed. This is somewhat similar to Looker's "Browse -> Explore -> Develop".
   3. **The order is less important in the main menu:** while having the right order is important in some places, it's not like users can return to previous steps by clicking on the main menu.
   4. **Home page already orders content by usage:** it's better be consistent than not.
   
   I went back and checked, [SIP-34](https://github.com/apache/superset/issues/8976) actually re-arranged the menu by usage order (Dashboards -> Charts -> SQL Lab -> Data). There must be some reason behind that---hope it was in line with what I described above.


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org