Include site sections on mobile sidenav

[parlough]

Also renames "User Guides" to just "Guides" as we prefer "Developers" over "Users" and the title case is inconsistent with what we use elsewhere.

Fixes #13084

[gemini-code-assist]

Summary of Changes

Hello @parlough, 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 enhances the user experience on the website by ensuring key navigation sections are always accessible in the mobile sidenav. It also refines the site's terminology by standardizing 'User Guides' to 'Guides' for better consistency and clarity, impacting both navigation elements and documentation. These changes aim to improve discoverability and maintain a cohesive brand voice.

Highlights

• Mobile Sidenav Visibility: The top-level navigation items in the mobile sidenav are now always visible, removing the previous conditional rendering that only showed them when the 'Learn' section was active.
• Navigation Label Renaming: The 'User Guides' navigation label has been consistently renamed to 'Guides' across the header, sidenav, and relevant documentation to align with preferred terminology and consistent casing.
• Style Hash Reset: The generatedStylesHash constant has been cleared, likely indicating a refresh or invalidation of cached styles.

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

Changelog

• site/lib/src/components/layout/header.dart
  • Renamed 'User Guides' navigation item to 'Guides'.
• site/lib/src/components/layout/sidenav.dart
  • Removed conditional rendering for the top navigation items, making them always visible.
  • Updated the 'Home' navigation label to 'Guides'.
• site/lib/src/style_hash.dart
  • Reset the generatedStylesHash value.
• src/content/release/whats-new.md
  • Updated documentation to reflect the new 'Guides' label.

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 introduces two key improvements. Firstly, it makes the main site sections ('Guides', 'Learn', 'Reference') consistently visible on the mobile sidenav, which previously only appeared on 'Learn' pages. This enhances user navigation. Secondly, it standardizes the term 'User Guides' to 'Guides' throughout the site for consistency, as detailed in the description. This change is reflected in the header, sidenav, and release notes. The code changes are clear, correct, and effectively achieve the stated goals. I have no further suggestions.

[flutter-website-bot]

Visit the preview URL for this PR (updated for commit ee11d0a):

https://flutter-docs-prod--pr13085-fix-13084-1q60s0in.web.app

[sfshaza2]

lgtm

[sfshaza2]

Yeah, I was tempted to change "User Guides" to "User guides", but this is better.