Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

style: Hero Section Updates and ContainerScroll Refactor #177

Merged
merged 1 commit into from
Dec 11, 2024

Conversation

berry-13
Copy link
Member

This pull request includes several updates to the components/home/Hero.tsx and components/ui/container-scroll-animation.tsx files to enhance the user interface and improve code flexibility. The most important changes include adding new images for different themes and devices, updating the layout and styling of the hero section, and refactoring the ContainerScroll component to accept additional class names.

Enhancements to the Hero Section:

  • Added new images for light and dark themes, as well as mobile and desktop versions, to improve visual appeal (components/home/Hero.tsx).
  • Updated the layout and styling of the hero description and links to be more responsive and visually consistent across different screen sizes (components/home/Hero.tsx). [1] [2] [3]

Code Refactoring:

  • Refactored the ContainerScroll component to accept an optional className prop, allowing for more flexible styling (components/ui/container-scroll-animation.tsx). [1] [2]

Copy link

vercel bot commented Dec 11, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
librechat-ai ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 11, 2024 4:09pm

Copy link

📦 Next.js Bundle Analysis for librechat.ai

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page Size (compressed)
global 293.88 KB (🟡 +253 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!

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page Size (compressed) First Load % of Budget (350 KB)
/ 39.14 KB 333.01 KB 95.15% (🟡 +0.12%)
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.

@danny-avila danny-avila merged commit d1e6596 into main Dec 11, 2024
3 checks passed
@danny-avila danny-avila deleted the ui-update branch December 11, 2024 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants