Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • rtat.net/design.gitlab.com
  • michaelgusto14/design.gitlab.com
  • DylanGriffith/design.gitlab.com
  • gitlab-org/gitlab-services/design.gitlab.com
  • jellynina/design.gitlab.com
  • ynsmroztas/design.gitlab.com
  • gtsiolis/design.gitlab.com
  • jeaster121/design.gitlab.com
  • jjlorenzo/design.gitlab.com
  • b1n/design.gitlab.com
  • katokpara/design.gitlab.com
  • evhoffmann/design.gitlab.com
  • eysz7-x-x/design.gitlab.com
  • roufique/design.gitlab.com
  • michals2/design.gitlab.com
  • snegu/design.gitlab.com
  • tinahaibodi/design.gitlab.com
  • jagan.velpuri/design.gitlab.com
  • ndingding/design.gitlab.com
  • Kzai/design.gitlab.com
  • unaheidi/design.gitlab.com
  • jnwlkr/design.gitlab.com
  • Citizen_Drain/design.gitlab.com
  • Ali123123/design.gitlab.com
  • steve12312/design.gitlab.com
  • sarahill/design.gitlab.com
  • ms_bandral/design.gitlab.com
  • tmorehouse/design.gitlab.com
  • xeious/design.gitlab.com
  • siddheshpalande/design.gitlab.com
  • allenl/design.gitlab.com
  • gtrohel/design.gitlab.com
  • dyna-dot/design.gitlab.com
  • cmarinos/design.gitlab.com
  • jeanche/design.gitlab.com
  • splattael/design.gitlab.com
  • sarakhatri/design.gitlab.com
  • deuley/design.gitlab.com
  • davo3/design.gitlab.com
  • leetickett/design.gitlab.com
  • georgibakken/design.gitlab.com
  • veethika/design.gitlab.com
  • keviyne/design.gitlab.com
  • gitlab-renovate-forks/design.gitlab.com
  • FARESELLELL/design.gitlab.com
  • rastogi_saurav/design.gitlab.com
  • usApp-stAck/design.gitlab.com
  • WebDevAdminAlpha/design.gitlab.com
  • khalidhussain/design.gitlab.com
  • joe115/design.gitlab.com
  • mtrontz/design.gitlab.com
  • GregSong/design.gitlab.com
  • pintukumarkathrotiya/design.gitlab.com
  • ajish.kbn/design.gitlab.com
  • Jokerwin/design.gitlab.com
  • marvinrr322/design.gitlab.com
  • flayestelijah/design.gitlab.com
  • englotpiotr/design.gitlab.com
  • adithyaakrishna/design.gitlab.com
  • globat190/design.gitlab.com
  • techguy.plugins/design.gitlab.com
  • yashmaheshwari/design.gitlab.com
  • yasen2/design.gitlab.com
  • mikegreiling/design.gitlab.com
  • gdoyle/design.gitlab.com
  • monica_galletto/design.gitlab.com
  • tserkes/design.gitlab.com
  • NajahSoft/design.gitlab.com
  • Monthakan/design.gitlab.com
  • zillemarco/design.gitlab.com
  • mrgrafista/design.gitlab.com
  • francescosommella980/design.gitlab.com
  • ghostshell202/design.gitlab.com
  • roperera/design.gitlab.com
  • ropereralk/design.gitlab.com
  • JiannaMasmila/design.gitlab.com
  • shubhamahuja_/design.gitlab.com
  • nova44056/design.gitlab.com
  • xuweilong321/design.gitlab.com
  • raphaellandas/design.gitlab.com
  • armbiant/gitlab-pajamas-design-system
  • ondrejkonec/design.gitlab.com
  • arpitBhalla/design.gitlab.com
  • mirosss/design.gitlab.com
  • alejandro/design.gitlab.com
  • catinbag/design.gitlab.com
  • dediacc/design.gitlab.com
  • deerajhackerone/design.gitlab.com
  • joetakata/design.gitlab.com
  • nraj0408/design.gitlab.com
  • abeldmente/design.gitlab.com
  • mle/design
  • mle/pajamas-design-system-2
  • vakzz-h1/design.gitlab.com
  • gerwitz/design.gitlab.com
  • sahadat-sk/design.gitlab.com
  • M00njuic3/pahjamjams
  • ale3oula/design.gitlab.com
  • jamesrushford/pajamas-design-system-temp
  • wriozumi/design.gitlab.com
  • bucoleary/design.gitlab.com
  • interohm/design.gitlab.com
  • Garrybrayn/design.gitlab.com
  • SimoParashi/design.gitlab.com
  • Scmili/dycf-uh
  • paula.beatty1/design.gitlab.com
  • gitlab-community/gitlab-services/design.gitlab.com
  • Mohammadreza-Sarvari/design.gitlab.com
  • ollevche/design.gitlab.com
109 results
Show changes
Commits on Source (2)
# [2.78.0](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/compare/v2.77.2...v2.78.0) (2021-10-08)
### Features
* **navigation:** Add initial guidance for in-app messaging ([b5d894a](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/commit/b5d894acfc230a0deb31b91811fc2ed41e5121e7))
## [2.77.2](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/compare/v2.77.1...v2.77.2) (2021-10-08)
......
......@@ -38,6 +38,24 @@ We do not add new top-level menu items in order to:
- Improve discoverability of new features. Instead, look for other opportunities to highlight the functionality throughout the product.
- Optimize for the potential future. We should be forward thinking without over optimizing. As features are developed and added, we can look into what changes may need to occur to support a growing feature.
#### Messaging changes to users
Continuously improving the navigation ensures the best possible user experience. To minimize disruption and properly introduce users to changes, follow these guidelines.
Use these approaches based on item usage:
- **None required:** No in-app messaging is required if an item has less than 0.025% of clicks per active user per month.
- **Subsequent:** An in-app [toast](/components/toast) with a confirm action is required after moving a top-level menu item if that item has between 0.026%-0.099% of clicks per active user per month. The toast should appear after first navigating to a screen that includes the sidebar with the navigation change. After dismissal, the toast should not reappear even when navigating to a new group or project with the navigation change.
- **Advanced:** An advanced page-level info [alert](/components/alert) is required if an item has equal to or greater than 0.1% of clicks per active user per month. Advanced notice should be in place for at least one milestone.
- **Temporary opt-in:** If more than 5 top-level navigation items are being changed that have a combined 5% of clicks per active users per month, a temporary opt-in method should be provided for at least 2 milestones. Temporary opt-in provides time to communicate major navigation overhauls while also allowing a user to preview changes.
Consider the following for all top-level menu item changes:
- All changes should be included in the release post.
- A [canary rollout](https://docs.gitlab.com/ee/user/project/canary_deployments.html) may be used to slowly roll out changes to users and get their feedback before releasing to all users.
- Documentation should always be updated in the first release the change is introduced. For canary rollouts, the change may not be available to everyone at the same time and this can be specified in the docs using the following:
> This change is being rolled out incrementally to a subset of the user base. Therefore, this change may not be available to you until it is fully enabled for all users.
#### Sub-nav groups
Each sub-nav group should be a self-contained group of functionality, for example:
......