V2 preview #446
Open
V2 preview #446
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Refactor button styles in DownloadButton and AuthButton to use consistent height, padding, and font properties. Update header layout and styling, including the logo and navigation menu, to improve visual coherence. Adjust SVG colors and navigation menu trigger styles for better alignment with the design system.
Removed unused components such as Tooltip, HeaderBadge, GridIllustration, IntegrationBox, and ExpandableCards. Simplified the Hero, Features, and DesktopFeatures components to improve maintainability and reduce complexity. Updated video data to reflect current product features. These changes streamline the codebase and enhance UI consistency.
…ayout Refactor the video section components to improve maintainability and consistency. Renamed `Features.tsx` to `DesktopVideoSection.tsx` and `MobileFeatures.tsx` to `MobileVideoSection.tsx` for clarity. Updated the feature layout in `Features.tsx` to include new sections like PearAI Creator, Agent, Login, and Launch. Added new SVG assets for visual enhancements.
Adjust video durations in data.ts, add PearWhiteLogo.svg, and refine layout and styling in Features.tsx, footer.tsx, and showcase.tsx. Changes include padding adjustments, color updates, and improved responsiveness to enhance user experience and visual consistency.
…styling Extracted the CTA section from showcase.tsx into a reusable component and updated styling across multiple components including header, authbutton, footer, and faq. Simplified FAQ content and improved consistency in layout and design.
…component - Remove redundant hover class from footer button - Replace ChevronDown with ChevronRight in accordion and adjust rotation - Enhance FAQ component with rounded borders, padding, and updated text styles
Added two new SVG files, PearAIRouterVector.svg and PearAIChatVector.svg, to the public/images directory. These assets will be used for UI components in the application.
Updated the pricing page to streamline the layout, removed redundant tabs, and improved the visual hierarchy. Adjusted the pricing tiers to be more concise and added new UI components for better user interaction. Also, added new SVG assets for enhanced visual appeal and improved the download button functionality.
…UI consistency Update various components to improve responsiveness and layout consistency across different screen sizes. Adjust padding, margins, and breakpoints to ensure a seamless user experience on both mobile and desktop views. Simplify video section logic and enhance progress animations for mobile video playback.
Remove unused imports like `AnimatePresence` from `MobileVideoSection.tsx` and clean up class names in `footer.tsx`, `hero.tsx`, `showcase.tsx`, and `cta.tsx`. Update video URLs in `data.ts` and remove unused icons from `icons.tsx` to improve code maintainability and readability.
- Adjust text colors, spacing, and layout in various components - Remove unused DarkModeToggle component - Enhance mobile responsiveness and touch interactions - Update hero section animation and image display
…ntributor pages Updated the styling and structure of the beta tester signup form, FAQ, and OSS contributor pages to improve consistency and readability. Moved FAQ data to the top of the file for better organization and adjusted class names for a more cohesive design. Also, simplified the beta page layout and removed unnecessary state management.
Simplify the layout of the TopUpPage component to enhance readability and responsiveness. The changes include reorganizing the header and card sections, adjusting spacing, and improving the overall user experience.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Changes requested ❌
Reviewed everything up to 8a88669 in 4 minutes and 21 seconds. Click for details.
- Reviewed
4863lines of code in37files - Skipped
16files when reviewing. - Skipped posting
14draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. app/programs/beta-tester/page.tsx:72
- Draft comment:
Consider using a more robust method than a hard-coded 100ms delay to ensure the target element is fully rendered before scrolling. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% While the comment identifies a potential improvement area, it doesn't provide specific alternatives. The current setTimeout approach, while not ideal, is a common pattern in React for handling post-render operations. The comment suggests there's a problem but doesn't offer a clear solution. The current code likely works fine for most cases. The comment could be valid - using MutationObserver or ResizeObserver might be more reliable. The current approach might fail if the page takes longer than 100ms to load. While there are more robust solutions, this is a minor optimization for an edge case. The current solution is simple and likely works well enough for the use case. Delete the comment as it points out a theoretical issue without providing clear actionable guidance, and the current solution is likely sufficient for the use case.
2. components/header.tsx:84
- Draft comment:
The 'handleSignOut' function uses a 'use server' directive within a client component. Verify if this pattern is supported, or consider moving sign-out logic to a dedicated server route. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
3. components/pricing.tsx:62
- Draft comment:
The OS detection useEffect uses separate if statements without else-if, which can lead to multiple assignments. Consider using mutually exclusive conditions. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% The comment has a valid point - theoretically a user agent string could contain both "Win" and "Linux" which would cause multiple assignments. However, in practice, browser user agent strings are standardized and won't contain multiple OS identifiers. The current code is actually more maintainable and readable than a complex if-else chain. The theoretical issue is unlikely to cause real problems. I could be wrong about user agent strings - there may be edge cases I'm not aware of where they do contain multiple OS identifiers. The current code could be made more robust. While the code could be made more robust, the current implementation is clear and handles the standard cases well. The theoretical edge case is unlikely enough that it doesn't justify complicating the code. This comment identifies a theoretical issue but the current implementation is pragmatic and unlikely to cause real problems. The comment should be removed as it doesn't identify a clear issue requiring changes.
4. components/ui/downloadbutton.tsx:18
- Draft comment:
Ensure the getOS() utility returns an object with a 'download' property, and consider adding error handling if OS detection fails. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
5. components/ui/mobile-menu.tsx:212
- Draft comment:
For better accessibility, add an aria-label to the theme toggle button. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
6. components/Features.tsx:27
- Draft comment:
Consider changing 'get the best on market' to 'get the best on the market' for clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While technically correct grammatically, this is an extremely minor copy change. The meaning is perfectly clear either way. This feels more like a personal preference than a real issue. Marketing copy often intentionally uses slightly informal language. The rules say not to make comments that are obvious or unimportant. The missing "the" could be considered grammatically incorrect in formal English. Some might argue that maintaining proper grammar is important for professionalism. However, this is marketing copy where informal language is common and often intentional. The meaning is completely clear either way, making this an unimportant stylistic suggestion rather than a real issue. This comment should be deleted as it's too minor and doesn't highlight a real issue that needs fixing.
7. components/Features.tsx:42
- Draft comment:
The text 'GPT-4o' appears to have an extra 'o'. If this is not intentional, consider updating it to 'GPT-4'. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% This appears to be a UI/marketing page showing AI model comparisons. The "o" in "GPT-4o" could be intentional - it might be a specific variant or version of GPT-4. Without deeper knowledge of the AI models being referenced, we can't assume it's a typo. We should be especially careful about UI/marketing content where names are often intentionally chosen. The comment assumes knowledge about AI model naming that we don't have. The "o" suffix could be meaningful in this context. Given this is UI content and we don't have definitive knowledge that "GPT-4o" is incorrect, we should not make assumptions about the intended model name. Delete the comment as it makes assumptions about UI content without strong evidence of an error, and UI changes should be assumed correct per the review rules.
8. components/features/data.ts:16
- Draft comment:
Typographical suggestion: The description for id:2 currently says 'Use PearAI Agent codes for you as your project's needs grow...'. This phrasing might be a typo; consider revising it to 'Use PearAI Agent to code for you as your project's needs grow...' for clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While the suggested change would improve the grammar slightly, this is marketing copy that was deliberately changed in this PR. The current phrasing, while not perfect, is still understandable. Comments about minor wording in marketing copy are generally not valuable enough to warrant a PR comment. The author likely carefully chose this wording for marketing purposes. The grammar issue could potentially affect user understanding of the product's functionality. Marketing copy should be professionally polished. The current wording is still clear enough to understand, and marketing teams often use intentionally informal or unconventional phrasing. This is not a technical issue that affects functionality. Delete this comment as it's a minor grammatical suggestion on marketing copy that doesn't impact functionality.
9. components/hero.tsx:82
- Draft comment:
There appears to be a typographical error in the backing text. The word 'COMBINATOR' is used, but it might be intended to be 'Y COMBINATOR' as in the previous version. Please verify and correct if needed. - Reason this comment was not posted:
Comment looked like it was already resolved.
10. components/pricing.tsx:462
- Draft comment:
Typo: In the tooltip text, "configure and manage different API's and tools" should be changed to "configure and manage different APIs and tools". The apostrophe is unnecessary for the plural. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
11. components/showcase.tsx:25
- Draft comment:
Typo found: 'indispensible' should be corrected to 'indispensable' in the testimonial text for Josh Koelker. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
12. components/ui/dropdown-menu.tsx:50
- Draft comment:
Typo spotted: the string 'xborder' in the class names (line 50) appears to be a mistake. It likely was intended to be 'border' or removed entirely. Please check and update accordingly. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
13. components/ui/dropdown-menu.tsx:68
- Draft comment:
Typo spotted: the string 'xborder' in the class names (line 68) seems to be a typo. It may need correction to 'border' or to be removed. Please verify. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
14. components/ui/mobile-menu.tsx:211
- Draft comment:
In the last part of the component, the className 'width-full' is used (lines 210-211). Typically, for Tailwind CSS, the correct class is 'w-full'. Please update these occurrences to avoid any styling issues. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
Workflow ID: wflow_LsE0MWUMv05vDQlq
You can customize 
| </small> | ||
| {(title === "Enterprise" || "Maker") && ( |
There was a problem hiding this comment.
Logical bug: The expression (title === 'Enterprise' || 'Maker') always evaluates to truthy. Use explicit comparisons for both conditions.
Suggested change
| {(title === "Enterprise" || "Maker") && ( | |
| {(title === "Enterprise" || title === "Maker") && ( |
| <div className="relative flex-col items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAILoginVector.svg" | ||
| alt="PearAI Creator" |
There was a problem hiding this comment.
The alt text for the PearAI Login image is set to 'PearAI Creator'. It should likely be 'PearAI Login' to accurately describe the image.
Suggested change
| alt="PearAI Creator" | |
| alt="PearAI Login" |
| <div className="relative flex items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAILaunchVector.svg" | ||
| alt="PearAI Agent" |
There was a problem hiding this comment.
The alt text for the PearAI Launch image is set to 'PearAI Agent'. It should be updated to 'PearAI Launch' for consistency.
Suggested change
| alt="PearAI Agent" | |
| alt="PearAI Launch" |
| <div className="flex items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAIRouterVector.svg" | ||
| alt="PearAI Creator" |
There was a problem hiding this comment.
Typo in alt attribute for the PearAI Router image. The alt text is currently PearAI Creator but should be PearAI Router.
Suggested change
| alt="PearAI Creator" | |
| alt="PearAI Router" |
| <div className="flex items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAIChatVector.svg" | ||
| alt="PearAI Agent" |
There was a problem hiding this comment.
Typo in alt attribute for the PearAI Chat image. The alt text is currently PearAI Agent but should be PearAI Chat.
Suggested change
| alt="PearAI Agent" | |
| alt="PearAI Chat" |
| <div className="flex items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAILoginVector.svg" | ||
| alt="PearAI Creator" |
There was a problem hiding this comment.
Typo in alt attribute for the PearAI Login image. The alt text is currently PearAI Creator but should be PearAI Login.
Suggested change
| alt="PearAI Creator" | |
| alt="PearAI Login" |
| <div className="flex items-center justify-center"> | ||
| <Image | ||
| src="/images/PearAILaunchVector.svg" | ||
| alt="PearAI Agent" |
There was a problem hiding this comment.
Typo in alt attribute for the PearAI Launch image. The alt text is currently "PearAI Agent" but should be "PearAI Launch".
Suggested change
| alt="PearAI Agent" | |
| alt="PearAI Launch" |
| </span> | ||
| </div> | ||
| <p className="text-base text-[#666666]"> | ||
| Launches your web projects onto to internet so you can |
There was a problem hiding this comment.
Typographical error in description text for the PearAI Launch card: it reads "Launches your web projects onto to internet so you can share with everyone." Consider revising to "Launches your web projects onto the internet so you can share with everyone."
Suggested change
| Launches your web projects onto to internet so you can | |
| Launches your web projects onto the internet so you can |
| }} | ||
| > | ||
| <Image | ||
| src="icons\ArrowDownTrayMicroIcon.svg" |
There was a problem hiding this comment.
Typo: The image src uses a backslash (\) instead of a forward slash (/). Please change icons\ArrowDownTrayMicroIcon.svg to icons/ArrowDownTrayMicroIcon.svg to ensure the path works correctly.
Suggested change
| src="icons\ArrowDownTrayMicroIcon.svg" | |
| src="icons/ArrowDownTrayMicroIcon.svg" |
| @@ -126,8 +126,7 @@ export const PRICING_TIERS: { | |||
| { | |||
| title: "Intern", | |||
| price: "0", | |||
| description: | |||
| "You can download PearAI directly, and use our free trial, or your own API key 🤓", | |||
| description: "Download with a free trail", | |||
There was a problem hiding this comment.
Typo detected: Consider changing "Download with a free trail" to "Download with a free trial".
Suggested change
| description: "Download with a free trail", | |
| description: "Download with a free trial", |
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed d6d1486 in 57 seconds. Click for details.
- Reviewed
13lines of code in1files - Skipped
0files when reviewing. - Skipped posting
1draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. app/beta/page.tsx:19
- Draft comment:
BetaPage no longer receives the 'user' prop, but the supabase.getUser call is still performed. Confirm that BetaPage doesn't rely on the user prop. If it's not needed, remove the unused getUser call to simplify the code. - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_e0M7bbVn49KeRvgK
You can customize
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related Issue
Changes Made
Screenshots
Checklist
yarn buildand build is successfulImportant
The pull request introduces a V2 preview for PearAI, featuring UI enhancements, new components like
VideoSection, and updates to pricing and feature offerings.Hero,Footer, andHeadercomponents for improved design and layout.VideoSectionwithDesktopVideoSectionandMobileVideoSectionfor responsive video content.Featurescomponent to highlight PearAI's capabilities.BetaTesterSignupFormfor user applications to the beta tester program.Pricingcomponent to include new pricing tiers and download options.FAQComponentfor frequently asked questions.constants.tswith new pricing and download URLs.package.json, including@heroicons/react.ExpandableCardsandIntegrationBox.This description was created by
for d6d1486. You can customize this summary. It will automatically update as commits are pushed.