Skip to content

Reorder landing page sections for clearer user flow#404

Merged
zz-plant merged 1 commit into
mainfrom
codex/rethink-information-ordering-for-users
Jan 15, 2026
Merged

Reorder landing page sections for clearer user flow#404
zz-plant merged 1 commit into
mainfrom
codex/rethink-information-ordering-for-users

Conversation

@zz-plant

Copy link
Copy Markdown
Owner

Motivation

  • Improve information ordering so visitors can quickly pick the right path from any landing page by surfacing audience and framing guidance earlier.
  • Reduce cognitive load by showing framing and quick-start guidance before artifact previews on the Start Here page.

Description

  • Move the SectionBlock with id="audience" earlier in src/pages/index.astro so the audience selector appears before outputs and workflow sections.
  • Reorder src/pages/start-here/index.astro to render the framing block before routes and to move the artifacts previews after the quick-start section.
  • Update src/content/start-here.json to reorder the anchorLinks to match the new section order.
  • Remove the previous duplicate placements so each section appears only in its new, intended location.

Testing

  • Ran bun run typecheck and it passed.
  • Ran bun run astro:check and it passed.
  • Ran bun run check (includes lint, unit tests, typecheck, Astro check, and content validations) and all checks passed.

Codex Task

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @zz-plant, 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 user experience on the landing and 'Start Here' pages by strategically reordering content sections. The changes aim to guide visitors more effectively by presenting crucial information like audience selection, framing, and quick-start options earlier in the flow, thereby reducing cognitive load and enabling quicker navigation to relevant content.

Highlights

  • Landing Page Reordering: The main landing page (src/pages/index.astro) has been reordered to surface the 'Audience selector' section earlier, improving initial user guidance.
  • Start Here Page Content Flow: The 'Start Here' page (src/pages/start-here/index.astro) now presents 'framing' and 'quick-start' guidance before 'artifact previews', reducing cognitive load and streamlining the user journey.
  • Anchor Link Synchronization: The anchorLinks in src/content/start-here.json have been updated to reflect the new section order on the 'Start Here' page, ensuring navigation consistency.
  • Redundant Section Removal: Duplicate placements of sections have been removed across the affected pages, ensuring each content block appears only once in its new, intended location.
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.

@zz-plant zz-plant merged commit 4686f5a into main Jan 15, 2026
1 of 2 checks passed

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

Copy link
Copy Markdown
Contributor

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 effectively reorders sections on the landing and 'start-here' pages to create a more logical user flow. The changes are consistently applied across the Astro components and the corresponding JSON content file. The code is clean and the changes align well with the stated motivation. I have one suggestion to improve accessibility by removing a redundant aria-label attribute.

<a
class="button primary button--compact"
href={preview.href}
aria-label={preview.label}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The aria-label attribute here is redundant because its value is the same as the link's text content. When link text is already descriptive, an aria-label is not necessary. Screen readers will prioritize the aria-label, so while this doesn't cause a functional issue, removing it simplifies the code and adheres to accessibility best practices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant