updated wording to match free plan / verified HIW component

[iHildy]

updated wording to match free plan / verified how it works section / updated disclaimer

This pull request updates the landing page and related components to reflect the correct Jules free tier limits, clarify setup instructions, and improve attribution. The most important changes include updating the displayed task and concurrency limits from previous values to match the free tier, refining the setup instructions for clarity, and enhancing footer attribution.

Jules Free Tier Limit Updates:

• Changed all references to the daily task limit from "60" to "15" and concurrent limit from "5" to "3" in cta-section.tsx, problem-section.tsx, and success-state.tsx to accurately reflect the free tier limits. [1] [2] [3] [4]
• Added a disclaimer note specifying that all Jules limits stated are based on the free tier in disclaimer.tsx.

Setup Instructions and UI Improvements:

• Updated setup steps in how-it-works.tsx to clarify that users need to create a GitHub app and set up a webhook secret, and changed the third step to "Watch It Work" with a description of auto-retry behavior. [1] [2]
• Added estimated setup times to the "Hosted" and "Self-Hosted" tabs and improved tab styling for better emphasis.
• Hid the link to hosted setup instructions by making the container invisible in how-it-works.tsx.

Attribution and Labeling:

• Updated footer attribution to credit "iHildy" with a link to their GitHub profile, instead of generic community attribution, in footer.tsx.
• Changed the status and label for completed tasks from "completed" to "jules-done" in the mock dashboard for consistency.

Minor Copy Tweaks:

• Slightly adjusted copy for automation benefits in the problem section for clarity.

[gemini-code-assist]

Summary of Changes

Hello @iHildy, 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 updating the landing page and related components to accurately reflect the current Jules free tier limits, enhance the clarity of setup instructions, and improve attribution. The changes ensure that users are presented with correct information regarding task and concurrency limits, clearer guidance on how to get started, and proper credit for contributions.

Highlights

• Jules Free Tier Limits Update: The daily task limit was updated from 60 to 15, and the concurrent limit from 5 to 3, across various landing page components to accurately reflect the Jules free tier.
• New Free Tier Disclaimer: A new disclaimer was added to clarify that all stated Jules limits are based on the free tier.
• Setup Instructions Clarification: Setup instructions were refined for clarity, including specifying the need to create a GitHub app and setting up a webhook secret. The third setup step was also updated to "Watch It Work" with a description of auto-retry behavior.
• UI/UX Enhancements for Setup: Estimated setup times (1min for Hosted, 15min for Self-Hosted) were added to the respective tabs, and tab styling was improved for better emphasis.
• Attribution Update: The footer attribution was updated to specifically credit "iHildy" with a link to their GitHub profile, moving from a generic community attribution.
• Task Status Labeling Consistency: The status and label for completed tasks in the mock dashboard were changed from "completed" to "jules-done" to ensure consistency.
• Copy Refinement: Minor adjustments were made to the copy describing automation benefits in the problem section for improved clarity.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 updates the wording on the landing page to reflect the new free tier limits for Jules, clarifies some setup instructions, and updates attribution. The changes are mostly straightforward content updates. I've found a couple of areas for improvement regarding accessibility and semantic HTML. Specifically, I've suggested using the hidden class instead of invisible for better accessibility when hiding elements, and using paragraph tags with margins instead of <br /> tags for better semantic structure in the disclaimer.

[gemini-code-assist]

Using <br /> tags for spacing is generally discouraged in favor of CSS for layout and styling. For better semantic structure and maintainability, you could wrap the new disclaimer text in a <p> tag and use a margin utility for spacing. Since the parent AlertDescription component renders as a div, this is semantically correct and will be styled appropriately.

            <p className="mt-4">* All Jules limits stated are based on the free tier.</p>

[gemini-code-assist]

Using the invisible class here makes the link visually hidden, but it still occupies space in the layout and might remain focusable by keyboard navigation. This can lead to a confusing experience for users of assistive technologies. For better accessibility, it's recommended to use the hidden class, which sets display: none and removes the element from both the visual layout and the accessibility tree.

            <div className="text-center mt-8 hidden">