[CorCvusRamboChen]

Refs #4513

Proposed as a dedicated page. A Dashboard widget or a Boards component would be the
cheaper place to put it, but both give one widget per website, and the whole point here is
one chart with one shared axis and one metric across several websites. Running on my own
instance. Happy to move it if you disagree; the questions left open below are smaller ones.

What

Adds an Overview page that puts several websites on one chart and one table, so an instance that
hosts a family of related sites can answer "which site grew?" without opening each website page.

• src/app/(main)/overview/ — page + client component: website multi-select (defaults to every
  website the user can view), metric select (Views / Visitors / any custom event name found in the
  data), the standard DateFilter with an "All time" option, a BarChart with a chart-type toggle
  (stacked bars / lines / stacked area, one colour per website), and a totals table (views,
  visitors, one column per event name) with a column picker in the page header that is remembered
  per browser.
• src/app/api/websites/overview/route.ts — GET /api/websites/overview?ids=&startAt=&endAt=&unit=&timezone=.
  Composes the existing getPageviewStats, getSessionStats, getEventStats, getWebsiteStats
  and getWebsiteDateRange per website. Authorisation via canViewBatchWebsites, mirroring
  /api/websites/charts, plus canViewWebsiteSection per website so a share token only gets the
  sections it shares (overview/compare for views and visitors, events for event counts).
  Each website's dates go through setWebsiteDate, like the single-website routes. Forbidden or
  unknown ids are dropped, not rejected.
• SideNav.tsx / MobileNav.tsx — one entry each, reusing the existing label.overview key.

Why

Dashboard and Boards give one widget per website: independent charts with independent axes and no
stacking or totals, and no way to switch all of them to the same custom event. The Websites list's
sparkline is fixed to visitors over seven days. Comparing sites day by day currently means opening
each website in its own tab. See the linked issue for the full use case.

Open questions

• "Overview" reuses an existing label; renaming it (e.g. "Compare") would mean one more key.
• Should the column picker persist per user (database) instead of per browser (localStorage)?
• Cap of 20 websites mirrors /api/websites/charts; fine, or should it page?

Notes for review

• No migrations and no new dependencies; only @umami/react-zen and Chart.js. Four new
  i18n keys: label.metrics for the metric picker, and names for the three chart types so the
  icon-only toggle is not read out as bar / line / area. They are added to every locale with
  the English text as a placeholder, so check:messages reports nothing missing.
• Works on both Prisma and ClickHouse because the route only composes existing query functions.
• ids is capped at 20 like /api/websites/charts.
• The event-name list and the table's event columns are derived from the response, so nothing
  needs configuring per instance.
• The table's visitor total is the period-wide distinct count from getWebsiteStats, not a sum of
  the per-bucket sessions series, so it matches a single website's stats and does not change
  with the chart's time unit.
• getWebsiteStats was declared as returning WebsiteStatsData[], but every branch returns
  result?.[0]; the declared type is corrected to WebsiteStatsData.
• Rebased on current dev. tsc --noEmit and Biome are clean for the changed files; vitest run
  shows the same 3 failing tests on this branch as on dev (none in files this PR touches).

Screenshots

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[vercel]

@RamboChenUnimelb is attempting to deploy a commit to the Umami Software Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The PR adds a cross-website analytics view for users who can already access those sites.

Fix the chart's timezone mismatch before merging.

Findings

1.  Chart drops visits ▶

Summary

Adds an Overview page for comparing views, visitors, and custom events across websites.

• Overview compares the same metric across selected websites.
• The overview API returns comparable metrics for each allowed website.

The previous-review ancestry and merge-base checks did not pass, so this review used the full PR diff. All supplied previous threads were unnumbered; none require numbered ledger entries. CorCvusRamboChen acknowledged the website cap and pagination as open decisions.

_{Reviews (2) · Last reviewed commit: "fix(overview): respect share sections an..." · Reviewed by Greptile}

[CorCvusRamboChen]

Thanks for the review. All six findings are addressed in 3b9f580 (replies on each thread):

Finding	Change
Hidden events become public	canViewWebsiteSection per website: views/visitors need overview/compare, event counts need events
Date limits are bypassed	filters built per website and passed through setWebsiteDate (no shared object across Promise.all)
Visitor totals count people twice	period-wide visitors from getWebsiteStats; the table no longer sums per-bucket sessions
All time misses added history	with All time active, the page follows the combined range of the current selection
Event names select wrong metrics	custom event metric ids carry an event: prefix everywhere
New labels lack locale fallback	the four labels exist in every locale (English placeholders); check:messages is clean

Verified locally on the branch: tsc --noEmit, biome lint on the touched files and check:messages all pass. The 20-website cap and pagination remain open as noted in the description; happy to adjust either if you have a preference.

@greptileai review