Feature/migrations

[dylanapplegate]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dappl3-site	Ready	Preview	Comment	Nov 1, 2025 2:07am

[gemini-code-assist]

Summary of Changes

Hello @dylanapplegate, I'm Gemini Code Assist¹! 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 focuses on a series of cleanup and refactoring tasks across documentation, configuration, and testing. It rebrands an instruction file, adjusts Tailwind CSS settings related to dark mode, and removes a dedicated dark mode test suite. The overall impact is a streamlined codebase with updated documentation and a revised approach to dark mode implementation and testing.

Highlights

• Documentation Renaming and Update: The copilot-instructions.md file has been renamed to GEMINI.md and its internal title updated to reflect 'Gemini Instructions'. This change likely signifies a shift in the AI assistant being referenced or a general rebranding of the documentation.
• Typography Selector Correction: Corrections were made in the documentation to update CSS heading selectors from h1-h6 to h1-6 for accuracy.
• Git Ignore Update: The .gitignore file has been updated to include /playwright-report, ensuring that Playwright test reports are not committed to the repository.
• Tailwind CSS Configuration Adjustment: The darkMode: "class" configuration has been removed from tailwind.config.js, which might indicate a change in how dark mode is implemented or managed within the application.
• Dark Mode Test File Removal: The tests/dark-mode.spec.ts file, which contained Playwright tests for dark mode functionality, has been entirely removed. This suggests a potential deprecation of these specific tests or a complete overhaul of the dark mode testing strategy.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/pr-checks.yml

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. ↩

[gemini-code-assist]

Code Review

This pull request appears to migrate the dark mode implementation from a class-based approach (likely using next-themes) to a media-query-based approach by removing darkMode: 'class' from the Tailwind configuration. While this is a valid architectural choice, it's been accompanied by the complete removal of all end-to-end tests for dark mode, which is a critical issue that regresses test coverage for a key user-facing feature. My review focuses on the implications of this migration and strongly recommends reinstating and adapting the tests.