Unified Dashboard: Register existing widgets in new Content area

[tofumatt]

Feature Description

The widgets that should appear in the Content area (created in #4031):

mainDashboardContentPrimary area:

1. Top keywords widget (half-width widget) (DashboardPopularKeywordsWidget)
2. Idea Hub widget (half-width) (DashboardIdeasWidget)
3. New widget with overall page metrics (new widget, so shouldn't be registered by this issue, instead registered in New Widget: Overall Page Metrics #4122)
4. Modified most popular content widget (ModulePopularPagesWidget)

entityDashboardContentPrimary area:

1. Top keywords widget (full width) (DashboardPopularKeywordsWidget)
2. New widget with overall page metrics (new widget, so shouldn't be registered by this issue*)

---

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

Acceptance criteria

These widgets should be registered to the following areas and appear on the Main Dashboard and Entity Dashboard respectively, in this order:

mainDashboardContentPrimary area:

• Top keywords widget (half-width widget) (DashboardPopularKeywordsWidget)
• Idea Hub widget (half-width) (DashboardIdeasWidget)
• Modified most popular content widget (ModulePopularPagesWidget)

entityDashboardContentPrimary area:

• Top keywords widget (full width) (DashboardPopularKeywordsWidget)

Implementation Brief

Inside assets/js/modules/search-console/index.js:

• Import AREA_MAIN_DASHBOARD_CONTENT_PRIMARY and AREA_ENTITY_DASHBOARD_CONTENT_PRIMARY from assets/js/googlesitekit/widgets/default-areas.js
• Inside the call to widgetsAPI.registerWidget for the DashboardPopularKeywordsWidget:
  • Add AREA_MAIN_DASHBOARD_CONTENT_PRIMARY and AREA_ENTITY_DASHBOARD_CONTENT_PRIMARY to the array passed as the last argument.
  • Add WIDGET_WIDTHS.HALF and WIDGET_WIDTHS.FULL to the array passed to options.width (the options object is the second argument)

Inside assets/js/modules/idea-hub/index.js:

• Import AREA_MAIN_DASHBOARD_CONTENT_PRIMARY from assets/js/googlesitekit/widgets/default-areas.js
• Inside the call to widgetsAPI.registerWidget for the DashboardIdeasWidget:
  • Add AREA_MAIN_DASHBOARD_CONTENT_PRIMARY to the array passed as the last argument.
  • Add WIDGET_WIDTHS.HALF to the array passed to options.width

Inside assets/js/modules/analytics/index.js:

• Import AREA_MAIN_DASHBOARD_CONTENT_PRIMARY from assets/js/googlesitekit/widgets/default-areas.js
• Inside the call to widgetsAPI.registerWidget for the ModulePopularPagesWidget:
  • Add AREA_MAIN_DASHBOARD_CONTENT_PRIMARY to the array passed as the last argument.
  • Add WIDGET_WIDTHS.FULL to the array passed to options.width

Test Coverage

• No new tests required, existing tests should pass.

QA Brief

• Check that DashboardPopularKeywordsWidget, DashboardIdeasWidget, and ModulePopularPagesWidget widgets have new areas added.

Changelog entry

• Add Content Area widgets to Unified Dashboard

[eugene-manuilov]

@johnPhillips, sending this ticket back to you to make adjustments discussed in #4079

[eugene-manuilov]

Thanks, @johnPhillips. IB ✔️

[kuasha420]

QA: ⚠️

I confirmed that.

• The widgets from the AC has been registered to Main and Entity Dashboard and are showing up.
• Idea Hub Widget shows the CTA to connect and once connected, shows ideas.

Things I noticed that needs clarification:

• Padding and margin on half width DashboardPopularKeywordsWidget is off, specially the top padding seems unaligned with the idea hub module.
• If Analytics module is not connected, the ModulePopularPagesWidget shows loading skeleton forever instead of a CTA to activate analytics module. Not sure if it falls outside of the scope this ticket.

Waiting for clarification.

CC @eugene-manuilov

[eugene-manuilov]

Thanks, @kuasha420, but this is out-of-scope for this ticket since this ticket is intended to add widgets to new areas only.

Padding and margin on half width DashboardPopularKeywordsWidget is off, specially the top padding seems unaligned with the idea hub module.

I believe this issue will be addressed in a separate ticket.

If Analytics module is not connected, the ModulePopularPagesWidget shows loading skeleton forever instead of a CTA to activate analytics module. Not sure if it falls outside of the scope this ticket.

This one will be fixed with #4226.

[kuasha420]

@eugene-manuilov thanks for clarifying. This it good to go then.

QA - ✔️

[felixarntz]

During approval for this I discovered a problem with this, which is unrelated to the issue here though, more related to #4031. Since it's still behind a feature flag, I opened a new issue #4268 to fix this. cc @tofumatt