feat: change default width to 90 rem

[kowyo]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @kowyo, 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 broadens the default content display area by adjusting the page and footer widths to 90rem. Concurrently, it refines the user experience by simplifying the width transition handling, removing redundant CSS and JavaScript, and updates the visual cue for width switching with a new, more descriptive icon.

Highlights

• Default Width Increased: The default content width for pages and footers has been increased from 80rem to 90rem, providing a wider layout for content.
• Transition Logic Streamlined: CSS rules and corresponding JavaScript logic for temporarily disabling width transitions have been removed, simplifying the width adjustment mechanism.
• Width Switcher Icon Updated: A new gallery-horizontal SVG icon has been added and is now used as the default icon for the width switcher component.

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

[cloudflare-workers-and-pages]

Deploying hoa-moe with    Cloudflare Pages

Latest commit:	e990e75
Status:	✅  Deploy successful!
Preview URL:	https://6627578a.hitsz-open-auto-github-io.pages.dev
Branch Preview URL:	https://feat-default-width.hitsz-open-auto-github-io.pages.dev

View logs

[gemini-code-assist]

Code Review

This pull request updates the default page width from 80rem to 90rem. The changes are consistently applied across the configuration, JavaScript, and HTML partials. A new icon is also introduced for the width switcher. My main concern is the removal of the logic that prevented width transitions on initial page load. This may introduce an undesirable animation or layout shift when a page first renders. I've left a specific comment with more details.

[gemini-code-assist]

The logic to prevent width transitions on initial page load has been removed from both this file and assets/css/custom.css. This will likely cause an unwanted animation or layout shift when a page is first loaded.

The previous implementation, which used the hoa-width-no-transition class to temporarily disable transitions, is a standard technique to ensure a smooth initial render. Unless this was an intentional change, I'd recommend restoring this logic to avoid a visual glitch for users.

[cubic-dev-ai]

No issues found across 5 files