Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@Aarebecca
Copy link
Contributor

@Aarebecca Aarebecca commented Jan 9, 2026

  • Generate individual html for each examples
  • Create llms.txt and llms-full.txt after build site
  • Optimize site page
image image

llms.txt

image

llms-full.txt

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @Aarebecca, 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 significantly improves the SEO capabilities of the gallery section by refactoring the detail pages to use dynamic routing and Static Site Generation (SSG). Each gallery example now has its own pre-rendered HTML page, making its content more discoverable by search engines. Additionally, the code content within these pages is made explicitly available to crawlers through a hidden HTML element.

Highlights

  • SEO Support for Gallery Pages: The primary goal of this pull request is to enhance Search Engine Optimization (SEO) for individual gallery example pages by ensuring each example has its own dedicated, crawlable HTML page.
  • Dynamic Routing Implementation: The routing for gallery detail pages has been updated from a query parameter-based approach (/gallery/example?template=<id>) to a cleaner, dynamic route (/gallery/<id>), which is crucial for static generation.
  • Static Site Generation (SSG): A new dynamic page site/src/pages/gallery/[template].tsx has been introduced, leveraging Next.js's getStaticPaths and getStaticProps to pre-render each gallery example as a static HTML file at build time.
  • Hidden Content for SEO: A hidden <pre> tag has been added to DetailPage.tsx to embed the code content directly into the HTML. This makes the code accessible to search engine crawlers even though it's visually hidden from users, improving content discoverability.
  • Refactored DetailPage Component: The DetailPage component now accepts a templateId prop, allowing it to be directly used by the statically generated pages. Its state initialization logic has also been adjusted to correctly set the initial code based on the provided template.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the gallery example pages to use static generation with dynamic routes, which is a great improvement for SEO. The implementation correctly uses getStaticPaths and getStaticProps to generate individual pages for each template. My review includes a couple of suggestions for the new dynamic route page ([template].tsx) to improve robustness and add support for internationalization. Overall, this is a solid refactor that achieves its goal. Addressing the feedback will make the implementation more robust and maintainable.

@Aarebecca
Copy link
Contributor Author

/gemini review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request is a great step towards improving SEO for the gallery pages by generating individual static pages for each example. The addition of a script to generate content for LLMs is also a nice touch. My review focuses on a few key areas to enhance the implementation. I've identified a potential issue with how duplicate URLs are handled in the new generation script, a non-optimal SEO practice for hiding content, and an opportunity to improve the script's performance by using asynchronous I/O. My detailed feedback is in the comments below.

@Aarebecca Aarebecca merged commit b8734c0 into main Jan 9, 2026
2 checks passed
@Aarebecca Aarebecca deleted the refactor/knowledge branch January 9, 2026 02:59
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.

3 participants