feat: improve landing section #833
Conversation
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
…tle` prop typing.
…ies into common modules.
…for year data and path isolation, and component verification.
…ng a pseudo-element and adjust content z-index.
…erform general site maintenance.
… imports, and remove unused styling.
… components and tests.
…SLint fix progress report.
…icit types in tests, components, and web vitals reporting.
…and perform minor formatting cleanup.
The import/order rule was too strict and tedious to maintain. Disabling it globally to improve developer experience.
Use @views alias instead of relative path to fix unresolved import error. This achieves zero ESLint errors in the codebase.
… code style and configuration updates.
…data` component, replacing `useDocumentTitleUpdater` in home wrappers and adding related documentation.
…on to optimize resource loading in `App.tsx`.
…lude them, and remove the SonarCloud CI workflow.
…phy, and refactor imports to use aliases.
✅ Deploy Preview for dev-bcn ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Summary of ChangesHello @anyulled, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request delivers a substantial update to the project, primarily driven by an upgrade to React 19. The changes encompass a modernized ESLint setup for better code quality, the introduction of native React 19 features for SEO and performance (metadata and resource preloading), and significant refactoring to ensure robust data and routing isolation across different conference years. Additionally, it addresses the recovery of critical 2025 CFP committee data and enhances the visual appeal of the landing page. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This is an impressive and extensive pull request that introduces significant improvements across the board. The upgrade to React 19, the adoption of a modern ESLint flat configuration, and the introduction of new features like the PageMetadata and ResourcePreloader components are excellent steps towards modernizing the codebase and improving performance and SEO. The refactoring to isolate year-specific data and components is also a huge win for maintainability. Overall, the changes make the codebase cleaner, more organized, and more robust. I have a few suggestions to further enhance type safety and long-term code consistency.
No description provided.