Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR refactors the meta tag generation and internationalization logic throughout the project while updating API endpoints for fetching event and organization data. The key changes include:
- Extraction and enhancement of meta tag generators for different pages (home, event, organization, city, and timeline).
- Replacement of API endpoints with new internal paths.
- Adjustments in layout and page components to integrate the updated meta generation functions.
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| src/utils/meta.ts | Refactored meta generators and keyword functions to support i18n. |
| src/pages/years.tsx | Updated meta usage via YearPageMeta and adjusted API endpoints. |
| src/pages/sitemap/organization.xml.ts | Updated organization API endpoint. |
| src/pages/sitemap/convention.xml.ts | Updated event API endpoint. |
| src/pages/organization.tsx | Updated meta generation and API endpoint for organization details. |
| src/pages/index.tsx | Updated home page data fetching and meta keyword generation usage. |
| src/pages/city.tsx | Updated meta for city page and API endpoint. |
| src/pages/[organization]/index.tsx | Updated meta generation, keywords, and API endpoint for organization details. |
| src/pages/[organization]/[slug].tsx | Updated meta generation, keywords, and API endpoint for event details. |
| src/components/layout/index.tsx | Updated meta tag generation with i18n integration in head component. |
| public/6fa5dfb083314d7eb7f393424ba2a89c.txt | Added a new public file. |
📦 Next.js Bundle Analysis for furry-event-chinaThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
319.01 KB (🟡 +236 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Four Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
34.5 KB |
353.51 KB | 101.00% (+/- <0.01%) |
/organization |
6.25 KB |
325.26 KB | 92.93% (+/- <0.01%) |
/sitemap/organization.xml |
425 B |
319.43 KB | 91.27% (🟢 -0.01%) |
/years |
7.6 KB |
326.61 KB | 93.32% (+/- <0.01%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
No description provided.