chore(site): replace hero CTA with license link and scroll arrow by Aureliolo · Pull Request #440 · Aureliolo/synthorg

Aureliolo · 2026-03-15T12:15:16Z

Summary

Replace "See How It Works" hero button with "License & Usage Restrictions" linking to the #license-usage section — more useful for first-time visitors evaluating the project
Add a subtle bouncing chevron arrow below the CTAs as a scroll-down hint
Add id="license-usage" anchor to the License & Usage section

Test plan

Verify landing page renders correctly (preview deploy)
"License & Usage Restrictions" button scrolls to the license section
Scroll arrow bounces and links to #how-it-works
"Start Building" and GitHub Star buttons unchanged

Replace "See How It Works" button with "License & Usage Restrictions" linking to the license section — more useful for first-time visitors. Add a subtle bounce arrow below the CTAs as scroll-down hint.

github-actions · 2026-03-15T12:15:25Z

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

gemini-code-assist · 2026-03-15T12:15:28Z

Summary of Changes

Hello, 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 landing page experience by refining the primary call-to-action in the hero section to better serve first-time visitors seeking licensing information. It also improves user navigation and discoverability of content by adding a visual scroll hint and ensuring direct access to the license details via an anchor link.

Highlights

Hero CTA Update: The 'See How It Works' call-to-action button in the hero section has been replaced with a 'License & Usage Restrictions' button, which now links directly to the relevant section on the page.
Scroll Hint Added: A subtle, bouncing chevron arrow has been introduced below the main CTAs to serve as a visual cue for users to scroll down for more content.
License Section Anchor: An id="license-usage" anchor has been added to the 'License & Usage' section, enabling direct navigation to this part of the page.

Changelog

site/src/pages/index.astro
- Replaced the 'See How It Works' button with 'License & Usage Restrictions' and updated its href attribute.
- Added a new scroll hint element with an animated chevron icon below the hero CTAs.
- Assigned the id="license-usage" attribute to the 'License & Usage' section for direct linking.

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.

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

coderabbitai · 2026-03-15T12:15:34Z

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Summary by CodeRabbit

New Features
- Added a visual scroll hint below call-to-action buttons directing users to the "How It Works" section.
- Enhanced navigation to the License & Usage section with improved direct linking.
UI/UX Updates
- Updated primary call-to-action button text and navigation target for clearer user guidance.

Walkthrough

Updated the hero section's primary CTA to link to "#license-usage" instead of "#how-it-works" and changed its label accordingly. Added a new scroll hint element with a downward chevron that links to the "how-it-works" section. Added an id attribute to the LICENSE & USAGE section container to enable direct anchor linking.

Changes

Cohort / File(s)	Summary
Navigation and Anchor Updates `site/src/pages/index.astro`	Updated hero CTA link target from "#how-it-works" to "#license-usage" with label change to "License & Usage Restrictions". Added new scroll hint element below CTAs linking to "how-it-works" section. Added "license-usage" id to LICENSE & USAGE section container for direct linking support.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main changes: replacing the hero CTA with a license link and adding a scroll arrow hint.
Description check	✅ Passed	The description is well-detailed and directly related to the changeset, explaining the rationale, specific changes, and providing a test plan.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment
Commit unit tests in branch chore/landing-page-cta-update

✨ Simplify code

Create PR with simplified code
Commit simplified code in branch chore/landing-page-cta-update

📝 Coding Plan

Generate coding plan for human review comments

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

gemini-code-assist

Code Review

This pull request successfully replaces the hero call-to-action button to link to the license section and adds a new scroll-down arrow as a visual hint. The changes are implemented correctly by updating the link's href and text, adding an id to the target section, and including a new anchor link with an SVG icon. My feedback includes one suggestion to improve code maintainability by componentizing the new SVG icon, which aligns with best practices for Astro projects.

gemini-code-assist · 2026-03-15T12:16:24Z

site/src/pages/index.astro

+      <a href="#how-it-works" class="mt-12 inline-block text-gray-500 hover:text-gray-300 transition-colors animate-bounce" aria-label="Scroll down for more details">
+        <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="m6 9 6 6 6-6"/></svg>
+      </a>


For better maintainability and reusability, it's a good practice to extract SVG icons into their own Astro components. This keeps the markup cleaner and makes icons easier to manage, especially if this icon or others are used elsewhere on the site.

For example, you could create a component src/components/icons/ChevronDown.astro:

// src/components/icons/ChevronDown.astro <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" {...Astro.props}> <path d="m6 9 6 6 6-6"/> </svg>

And then use it in this file:

--- import ChevronDown from '../components/icons/ChevronDown.astro'; --- <a href="#how-it-works" class="mt-12 inline-block text-gray-500 hover:text-gray-300 transition-colors animate-bounce" aria-label="Scroll down for more details"> <ChevronDown /> </a>

greptile-apps · 2026-03-15T12:16:49Z

Greptile Summary

This PR makes a focused hero-section UX update: it swaps the secondary CTA from a #how-it-works scroll link to a #license-usage anchor (more useful for evaluators of a BSL-licensed project), adds a bouncing chevron scroll hint that now fills the "scroll to how-it-works" role, and wires up the missing id="license-usage" anchor on the target section.

Secondary CTA text changed to "License & Usage Restrictions" linking to #license-usage — id="license-usage" correctly added to the target <section>.
Bouncing chevron <a href="#how-it-works"> added below CTAs with aria-label for screen readers — the #how-it-works anchor already exists on the page at line 81, so the link is valid.
All three items ("Start Building", GitHub Star, scroll arrow) are unchanged in behavior.
No structural, accessibility, or logic issues found.

Confidence Score: 5/5

This PR is safe to merge — it is a self-contained, purely cosmetic hero-section update with no logic, data, or security implications.
Both anchor targets (#license-usage and #how-it-works) exist in the page. The scroll-hint element is accessible, correctly positioned, and uses standard Tailwind utilities. No existing functionality is broken.
No files require special attention.

Important Files Changed

Filename	Overview
site/src/pages/index.astro	Replaces the "See How It Works" CTA with a "License & Usage Restrictions" anchor link, adds a bouncing scroll-hint chevron pointing to `#how-it-works`, and adds `id="license-usage"` to the license section. Both anchor targets exist and are valid; accessibility is handled with `aria-label` on the scroll hint.

_{Last reviewed commit: fefbf41}

🤖 I have created a release *beep* *boop* --- ## [0.2.4](v0.2.3...v0.2.4) (2026-03-15) ### Bug Fixes * attach cosign signatures and provenance bundle to release assets ([#438](#438)) ([f191a4d](f191a4d)) * create git tag explicitly for draft releases ([#432](#432)) ([1f5120e](1f5120e)) * docker healthcheck, CI optimization, and container hardening ([#436](#436)) ([4d32bca](4d32bca)) * ensure security headers on all HTTP responses ([#437](#437)) ([837f2fc](837f2fc)) * make install scripts usable immediately without terminal restart ([#433](#433)) ([b45533c](b45533c)) * migrate pids_limit to deploy.resources.limits.pids ([#439](#439)) ([66b94fd](66b94fd)) ### Refactoring * redesign release notes layout ([#434](#434)) ([239aaf7](239aaf7)) ### Maintenance * **site:** replace hero CTA with license link and scroll arrow ([#440](#440)) ([56af41c](56af41c)) * **web:** adopt @vue/tsconfig preset ([#435](#435)) ([7d4b214](7d4b214)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).

🤖 I have created a release *beep* *boop* --- ## [0.2.4](v0.2.3...v0.2.4) (2026-03-15) ### Bug Fixes * attach cosign signatures and provenance bundle to release assets ([#438](#438)) ([f191a4d](f191a4d)) * create git tag explicitly for draft releases ([#432](#432)) ([1f5120e](1f5120e)) * docker healthcheck, CI optimization, and container hardening ([#436](#436)) ([4d32bca](4d32bca)) * ensure security headers on all HTTP responses ([#437](#437)) ([837f2fc](837f2fc)) * make install scripts usable immediately without terminal restart ([#433](#433)) ([b45533c](b45533c)) * migrate pids_limit to deploy.resources.limits.pids ([#439](#439)) ([66b94fd](66b94fd)) * use cosign --bundle flag for checksums signing ([#443](#443)) ([19735b9](19735b9)) ### Refactoring * redesign release notes layout ([#434](#434)) ([239aaf7](239aaf7)) ### Maintenance * **main:** release 0.2.4 ([#431](#431)) ([63b03c4](63b03c4)) * remove stale v0.2.4 changelog section from failed release ([#446](#446)) ([769de10](769de10)) * reset version to 0.2.3 for re-release ([#444](#444)) ([8579993](8579993)) * **site:** replace hero CTA with license link and scroll arrow ([#440](#440)) ([56af41c](56af41c)) * **web:** adopt @vue/tsconfig preset ([#435](#435)) ([7d4b214](7d4b214)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).

chore(site): replace hero CTA with license link and scroll arrow

fefbf41

Replace "See How It Works" button with "License & Usage Restrictions" linking to the license section — more useful for first-time visitors. Add a subtle bounce arrow below the CTAs as scroll-down hint.

Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 12:16 — with GitHub Actions Inactive

gemini-code-assist bot reviewed Mar 15, 2026

View reviewed changes

Aureliolo merged commit 56af41c into main Mar 15, 2026
26 of 27 checks passed

Aureliolo deleted the chore/landing-page-cta-update branch March 15, 2026 12:18

Aureliolo temporarily deployed to cloudflare-preview March 15, 2026 12:18 — with GitHub Actions Inactive

Aureliolo mentioned this pull request Mar 15, 2026

chore(main): release 0.2.4 #431

Merged

This was referenced Mar 15, 2026

chore(main): release 0.2.0 #442

Closed

chore(main): release 0.2.4 #445

Merged

This was referenced Mar 15, 2026

chore(main): release 0.2.5 #447

Merged

chore(main): release 0.2.0 #460

Closed

coderabbitai bot mentioned this pull request Mar 15, 2026

feat(site): add SEO essentials, contact form, and early-access disclaimer #466

Closed

10 tasks

Aureliolo mentioned this pull request Mar 15, 2026

chore(main): release 0.2.0 #471

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(site): replace hero CTA with license link and scroll arrow#440

chore(site): replace hero CTA with license link and scroll arrow#440
Aureliolo merged 1 commit intomainfrom
chore/landing-page-cta-update

Aureliolo commented Mar 15, 2026

Uh oh!

github-actions bot commented Mar 15, 2026

Uh oh!

gemini-code-assist bot commented Mar 15, 2026

Uh oh!

coderabbitai bot commented Mar 15, 2026 •

edited

Loading

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Uh oh!

gemini-code-assist bot left a comment

Uh oh!

gemini-code-assist bot Mar 15, 2026

Uh oh!

greptile-apps bot commented Mar 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Aureliolo commented Mar 15, 2026

Summary

Test plan

Uh oh!

github-actions bot commented Mar 15, 2026

Dependency Review

Scanned Files

Uh oh!

gemini-code-assist bot commented Mar 15, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

coderabbitai bot commented Mar 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review failed

Summary by CodeRabbit

Walkthrough

Changes

Estimated code review effort

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist bot Mar 15, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot commented Mar 15, 2026

Greptile Summary

Confidence Score: 5/5

Important Files Changed

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

coderabbitai bot commented Mar 15, 2026 •

edited

Loading