[Dashboard] [Home] Welcome Module
See original GitHub issueThe original idea was to have 4 different states:
- First time using the new dashboard user.
- User with a notification from admin.
- User with other notifications (eg: a product update)
- Returning user with no notifications.
Designs are available here: https://projects.invisionapp.com/share/J7OPHL18HUR#/screens/336549667
Some of these states are easier than other.
1. First time using the new dashboard user.
The /me
endpoint has some flags (eg show_builder_activated_message
) to determine whether some messages should be displayed or not. I guess we would need to do something similar so that the frontend can know if the user is seeing the dashboard for the first time. What do you think @gonzaloriestra?
The problem I see with this is that someone might signup and not pay attention to the welcome message the first time. If we provide a link with some useful info about the new Dashboard, they might not see it. Perhaps we should show it until the user has performed some action (eg: click on the link to learn more or discard this “notification”). @kukukaka what do you think?
2. User with a notification from admin.
It should be easy to detect when there’s one or more unread notifications and invite the user to view all notifications.
3. User with other notifications (eg: a product update).
The main challenges here are:
- Deciding which notifications we will display to users. Right now we’re sending emails to users based on some actions / account usage that could be helpful in the UI as well.
- We don’t a system in place to do this. Ideally we would want to send notifications to users and make sure they see them / discard them. Right now only admins can send notifications to users.
An idea here is to push these notifications as any other notification instead of using the welcome module.
4. Returning user with no notifications.
Easy one too. If the user has already worked with the new dashboard and has no notifications, we display and compacted view of the welcome message.
In summary, 3. requires more work and it’s kind of blocking this so I suggest we go with 1., 2. and .4 until we have a more clear idea of how we want to notify users of important things happening on their accounts.
@kukukaka what do you think?
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (10 by maintainers)
Top GitHub Comments
Good to know! Thank you @gonzaloriestra!
I have one doubt about the actions for the different type of users. Should we put the same actions no matter if it is the first time they visit the new dashboard or not?