This idea stems from looking at #2176 and how to combine with the later experience of a user. Tips is that. It has a starting point, that the user chooses to opt into - it doesn't force the experience but encourages along the way.

This is a dialogue, the design is strongly influenced by chat interfaces and AI. It would be great to use this as a chance for personality - Gutenberg supporting and guiding along the way.

Tips flow

• On first load you see a message that encourages you to discover more about the new experience.
• At any point the user can cancel, they click through every stage.
• Tips are user guided, the user at every point decides. This is important as we never take over the screen with a modal or wizard.

Types of tips

There are 2 types of tips:

• Discovery tips: the initial walkthrough of the new experience. This is a complete flow.

• Helping tips: these level up users with tips that go beyond simply discovering the interface. These tips make your experience using Gutenberg improved, they are also a way to encourage users along their journey.

The backend should be very usable also to non-technical people: all tips are created in a way that's easy for someone to add new tips of either type.

Tips behaviour

Tips has certain behaviours:

• Discovery tips can be picked up at any point of the flow, up until 2 weeks into using the new experience. After that the only tips available are helping tips.
• If a user wants they can turn off or force on all tips, either via UI or code (this allows for network enabling/disabling).

Note: we could explore the toggle setting here again, but in past we have found it doesn't work there.

• If a tip is dismissed, no tips will show for 24hours.

An alternative to closing could be:

• If a user goes all the way through the discovery tips flow, no helping tips appear for 24hours or twice opening the editor if the user didn't visit the site in 24hours. This is a starting point to be reviewed for the kind of trigger logic.
• Tips only appear once, there is no duplication of tips.
• Once you dismiss 2 tips in a row, all tips turn off and you can turn on again via the setting in ellipsis.
• Tips are spaced in how they appear. Nobody should see more than 1 tip every 2 hours of continuous use, for example. We need to discuss the exact behaviour here. It's important to not make tips a problem.

Design

Tips has an animation based on the one @folletto has used here:

https://codepen.io/folletto/pen/POaQNG?editors=1100

The idea will be it's a 'heartbeat' and this can be worked on. The UI is designed to look like a chat interface on purpose.

Props to @folletto, @mtias and @jasmussen for helping me work through this. I have my rough sketches here as a background for where this idea came from:

https://cldup.com/Lwec4SpPGp.pdf

Conclusion

I would like to see us look at tips and how initial implementation doesn't have to be huge on this. Let's discuss.

As a starting point let's also here start thinking about tips that would be useful for users.