Skip to content

Surface the auto-updates CTA notice in the hub #13323

Closed

Description

@techanvil

Feature Description

The hub can only ever offer features up to the version of Site Kit that's installed, so keeping the plugin current is exactly what keeps What's new? worth visiting. The tab therefore opens with the prompt to enable auto-updates for Site Kit.

Site Kit already has this notice, and the flow behind it, on the dashboard. This issue surfaces the same notice in the hub and updates its copy to the design. The copy change is made to the notice itself rather than to a hub-specific copy of it, so the dashboard's notice picks up the new copy too.

It's shown in a notification area of the tab's own, above the feature list, holding one notice at a time. The auto-updates notice is the only thing shown there for now, but it's the hub's place for a notice that speaks to the whole list rather than to a single feature, and later notices will take their turn in it.

For reference, see the Auto-updates CTA notice section in the design doc, and the design in Figma.


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

  • The What's new? tab (Build the "What's new?" tab #13321) carries a notification area above the feature list, which holds one notice at a time.
  • Site Kit's existing auto-updates notice is shown in that area, so the tab opens with it above the feature list.
  • The notice's copy is updated to the title "Unlock the latest Site Kit features!" and the body "We regularly release new features and improvements to help you track your site's success. Enable auto-updates for Site Kit so you never miss the latest enhancements.", followed by its existing Learn more link. Its call to action reads Enable auto-updates and its dismiss reads No thanks.
  • That copy is changed on the notice itself, so it also changes where the notice already appears on the dashboard.
  • Everything else about the notice is unchanged: enabling auto-updates from the hub does what it does from the dashboard, its success and error states are unchanged, and dismissing it is permanent for that user.
  • As today, the notice isn't shown to a user who can't change plugin auto-update settings, or on a site where auto-updates for Site Kit are already enabled, or are forced on or off.
  • The notice isn't shown on the All services and features tab.

Implementation Brief

  • In assets/js/googlesitekit/notifications/constants.js:
    • Add FEATURE_DISCOVERY_WHATS_NEW_TOP: 'notification-area-feature-discovery-whats-new-top' to NOTIFICATION_AREAS.
  • In assets/js/googlesitekit/notifications/datastore/constants.js:
    • Add VIEW_CONTEXT_FEATURE_DISCOVERY to NOTIFICATION_VIEW_CONTEXTS.
  • In assets/js/components/notifications/EnableAutoUpdateBannerNotification.js, update the CTA variation only, leaving the success and error variations as they are:
    • Title: Unlock the latest Site Kit features!
    • Description: We regularly release new features and improvements to help you track your site’s success. Enable auto-updates for Site Kit so you never miss the latest enhancements. followed by a LearnMoreLink, composed with createInterpolateElement and resolved from select( CORE_SITE ).getDocumentationLinkURL( 'auto-updates' ).
    • Dismiss label: No thanks.
    • Export a second slug alongside ENABLE_AUTO_UPDATES_BANNER_SLUG, e.g. FEATURE_DISCOVERY_AUTO_UPDATES_BANNER_SLUG = 'feature-discovery-auto-update-cta', for the hub registration below.
  • In assets/js/googlesitekit/notifications/register-defaults.js, register the same component a second time for the hub, leaving the existing auto-update-cta registration untouched:
    • Component: EnableAutoUpdateBannerNotification, areaSlug: NOTIFICATION_AREAS.FEATURE_DISCOVERY_WHATS_NEW_TOP, viewContexts: [ VIEW_CONTEXT_FEATURE_DISCOVERY ], groupID: NOTIFICATION_GROUPS.SETUP_CTAS, priority: PRIORITY.SETUP_CTA_LOW, isDismissible: true.
    • checkRequirements: asyncRequireAll( requireCapability( PERMISSION_UPDATE_PLUGINS ), requireCanChangePluginAutoUpdates(), asyncRequire( false, requireSiteKitAutoUpdatesEnabled() ) ). Leave out the requireInitialSetupSuccess() branch: it keys off notification=authentication_success, which never appears on the hub URL.
  • In assets/js/components/feature-discovery/whats-new/WhatsNewTab.tsx (Build the "What's new?" tab #13321):
    • Above the feature list, render <Notifications areaSlug={ NOTIFICATION_AREAS.FEATURE_DISCOVERY_WHATS_NEW_TOP } groupID={ NOTIFICATION_GROUPS.SETUP_CTAS } /> in a wrapper element of its own, outside the empty-state fragment so it still renders when nothing is listed.
  • Keep the notice off All services and features: register it for FEATURE_DISCOVERY_WHATS_NEW_TOP only, and mount that area only in WhatsNewTab. AllServicesTab (Build the "All services and features" tab + goal groups #13328) mounts no notification area.
  • In assets/sass/components/feature-discovery/_googlesitekit-whats-new.scss (Build the "What's new?" tab #13321, creating it if that issue didn’t):
    • Style the wrapper, canceling the Grid/Cell padding NoticeNotification adds so the notice lines up with the list and the tab bar above it (--googlesitekit-feature-discovery-padding-*).

Test Coverage

  • Add coverage for the hub registration, testing that it is queued in the hub view context and not on the dashboard.
  • Add coverage for EnableAutoUpdateBannerNotification, testing the new copy and the Learn more link.
  • Add coverage for WhatsNewTab, testing that the notice renders above the feature list, including when it is empty.
  • Add a story for the What’s new? tab with the notice shown with VRT scenarios.

QA Brief

  1. Make sure featureDiscoveryHub feature flag is enabled in tester plugin.
  2. Make sure that auto-update is disabled for Site Kit plugin in Plugins > Installed plugins menu.
  3. Go to Site Kit > Add features > What's new tab.
  4. Make sure that the auto-update CTA notification is visible and matches the Figma design.
  5. Switch to All services and features tab and the CTA should not be visible here.
  6. When auto update is enabled using CTA, Thanks for enabling auto-updates success notification is shown.
  7. Clicking the No thanks would dismiss the notification.

Changelog entry

  • Update the auto-updates CTA notice, and show it on the "What's new?" tab in the Feature Discovery Hub.

Activity

  1. self-assigned this
    on Aug 23, 2026
  2. removed their assignment
    on Sep 15, 2026
  3. self-assigned this
    on Sep 16, 2026
  4. techanvil commented on Sep 16, 2026

    @techanvil
    CollaboratorAuthor

    Hi @hussain-t, thanks for drafting this IB, which is looking good. A couple of points:

    • Confirm the slug: no auto-updates documentation slug exists yet, and the page may need to be created.

    Consider the slug confirmed, I've flagged this with @adamdunnage on Asana.

    I might be missing something, but it doesn't look like the IB for 13356 addresses this. It's not clearly defined as an AC point for that issue either, so I think it would be better to flesh this out here.

  5. hussain-t commented on Sep 17, 2026

    @hussain-t
    Collaborator

    Thanks, @techanvil! I've updated the IB accordingly.

  6. 24 remaining items

  7. removed their assignment
    on Oct 6, 2026
  8. removed their assignment
    on Oct 6, 2026
  9. self-assigned this
    on Oct 7, 2026
  10. mohitwp commented on Oct 7, 2026

    @mohitwp
    Collaborator

    QA Update ⚠️

    Tested the auto-updates CTA changes with the featureDiscoveryHub feature flag enabled.

    @ankitrox

    Clarification
    For the AC case where the notice should not be shown to a user who cannot change plugin auto-update settings: standard non-admin Site Kit users only have access to the view-only dashboard and do not have access to the Add features hub.

    Should this scenario be tested using a custom capability/role setup, or is the standard view-only behaviour sufficient for this AC?

    Verified

    • The auto-updates CTA is displayed under Add features → What’s new when Site Kit auto-updates are disabled.
    • The CTA is displayed above the feature list and the updated copy/actions are shown as expected.
    • The Learn more link works as expected.
    • The CTA is not displayed under All services and features.
    • Clicking Enable auto-updates from the What’s new tab enables auto-updates successfully and shows the existing success notification.
    • Once auto-updates are enabled from the What’s new tab, the corresponding auto-update notice is also hidden on the Site Kit Dashboard.
    • Enabling auto-updates from the Site Kit Dashboard also hides the CTA under Add features → What’s new.
    • Clicking No thanks dismisses the CTA, and the dismissal persists for that user.
    • The dismissal is user-specific: dismissing the CTA for one admin does not dismiss it for another admin while auto-updates remain disabled.
    • Auto-update state is shared across admins: if Admin B enables auto-updates, the CTA is also hidden for Admin A.
    • Existing dashboard auto-update CTA copy/behaviour was regression checked.

    What's new Tab

    Details Image Image

    Main Dashboard

    Details Image Image

    Learn More link

    Details
    Recording.3483.mp4

    No thanks CTA

    Details
    Recording.3484.mp4

    Enable Auto Update CTA

    Details
    Recording.3485.mp4

    Enabling auto-updates from the Site Kit Dashboard

    Details
    Recording.3486.mp4

    Enabling auto-updates from the Another Admin

    Details
    Recording.3487.mp4
  11. ankitrox commented on Oct 8, 2026

    @ankitrox
    Collaborator

    Thank you @mohitwp for testing the issue.
    The standard view only behaviour is sufficient in this case.

    Please let me know in case of any question.

  12. removed their assignment
    on Oct 8, 2026
  13. mohitwp commented on Oct 8, 2026

    @mohitwp
    Collaborator

    QA Update ✅

    Tested the auto-updates CTA changes with the featureDiscoveryHub feature flag enabled.

    Verified

    • The auto-updates CTA is displayed under Add features → What’s new when Site Kit auto-updates are disabled.
    • The CTA is displayed above the feature list and the updated copy/actions are shown as expected.
    • The Learn more link works as expected.
    • The CTA is not displayed under All services and features.
    • Clicking Enable auto-updates from the What’s new tab enables auto-updates successfully and shows the existing success notification.
    • Once auto-updates are enabled from the What’s new tab, the corresponding auto-update notice is also hidden on the Site Kit Dashboard.
    • Enabling auto-updates from the Site Kit Dashboard also hides the CTA under Add features → What’s new.
    • Clicking No thanks dismisses the CTA, and the dismissal persists for that user.
    • The dismissal is user-specific: dismissing the CTA for one admin does not dismiss it for another admin while auto-updates remain disabled.
    • Auto-update state is shared across admins: if Admin B enables auto-updates, the CTA is also hidden for Admin A.
    • Existing dashboard auto-update CTA copy/behaviour was regression checked.

    What's new Tab

    Details Image Image

    Main Dashboard

    Details Image Image

    Learn More link

    Details
    Recording.3483.mp4

    No thanks CTA

    Details
    Recording.3484.mp4

    Enable Auto Update CTA

    Details
    Recording.3485.mp4

    Enabling auto-updates from the Site Kit Dashboard

    Details
    Recording.3486.mp4

    Enabling auto-updates from the Another Admin

    Details
    Recording.3487.mp4
  14. removed their assignment
    on Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0High priorityTeam MIssues for Squad 2Type: EnhancementImprovement of an existing feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions