Skip to content

Conversation

samejr
Copy link
Member

@samejr samejr commented Aug 3, 2025

Adds an image of the dashboard behind the onboarding page:

  • Aspect ratio/scaling behaves correctly when resizing the browser using multiple images
  • Uses a simple wrapper component which contains all the image behavior
  • Additional: Updates the color of the "ButtonSpinner" component since we changed our primary button color back to purple
CleanShot 2025-08-03 at 12 32 43@2x CleanShot 2025-08-03 at 12 36 49@2x CleanShot 2025-08-03 at 12 46 38@2x CleanShot 2025-08-03 at 12 49 45@2x

Copy link

changeset-bot bot commented Aug 3, 2025

⚠️ No Changeset found

Latest commit: 0d39a9d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Aug 3, 2025

Walkthrough

A new BackgroundWrapper React component was introduced to provide a styled background with layered images and dark overlays. The AppContainer component was enhanced to accept an optional className prop for flexible styling. Multiple page components—including NewOrganizationPage, project creation, plan selection, basic details confirmation, invites, and organization invite pages—were refactored to incorporate BackgroundWrapper and updated AppContainer usage. These pages also received layout enhancements such as rounded corners, borders, background colors, padding, and shadows. The ButtonSpinner component's default color scheme was changed from black to white. Some forms had input order and conditional rendering adjusted without changes to business logic or data handling.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~18 minutes

  • The addition of a new layout component and its integration across multiple pages increases the review scope.
  • Changes involve moderate complexity due to component composition updates, styling adjustments, and some conditional UI restructuring.
  • No significant data handling, business logic, or algorithmic changes are present, maintaining a moderate complexity level.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c23ae25 and 0d39a9d.

📒 Files selected for processing (2)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug.invite/route.tsx (2 hunks)
  • apps/webapp/app/routes/invites.tsx (2 hunks)
✅ Files skipped from review due to trivial changes (1)
  • apps/webapp/app/routes/invites.tsx
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

  • apps/webapp/app/routes/_app.orgs.$organizationSlug.invite/route.tsx
{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

We use zod a lot in packages/core and in the webapp

Files:

  • apps/webapp/app/routes/_app.orgs.$organizationSlug.invite/route.tsx
apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/webapp.mdc)

apps/webapp/**/*.{ts,tsx}: In the webapp, all environment variables must be accessed through the env export of env.server.ts, instead of directly accessing process.env.
When importing from @trigger.dev/core in the webapp, never import from the root @trigger.dev/core path; always use one of the subpath exports as defined in the package's package.json.

Files:

  • apps/webapp/app/routes/_app.orgs.$organizationSlug.invite/route.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
  • GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
  • GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
  • GitHub Check: typecheck / typecheck
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
apps/webapp/app/routes/_app.orgs.$organizationSlug.invite/route.tsx (2)

146-146: LGTM! Consistent styling with the broader UI update pattern.

The styling classes added to MainCenteredContainer create a cohesive card-like appearance that aligns with the PR's objective of enhancing the onboarding dashboard background. The classes provide good visual hierarchy with appropriate spacing, borders, and shadows.


206-206: LGTM! Button variant change aligns with design system updates.

The change from "tertiary/small" to "secondary/small" for the cancel button is consistent with the PR's mention of button color updates and provides better visual consistency with the new card-style container.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch onboarding-dashboard-background

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/webapp/app/components/BackgroundWrapper.tsx (1)

8-46: Consider refactoring inline styles and addressing mobile viewport issues.

The implementation uses extensive inline styles which could be moved to CSS classes for better maintainability. Also, using 100vh can cause viewport issues on mobile browsers where the viewport height changes when the address bar appears/disappears.

Consider these improvements:

+/* Add to CSS file */
+.bg-menu-top {
+  background-image: url('~/assets/images/blurred-dashboard-background-menu-top.jpg');
+  background-size: 260px auto;
+  background-position: left top;
+  background-repeat: no-repeat;
+  height: 100dvh; /* Use dynamic viewport height */
+}

-      <div
-        className="absolute left-0 top-0 w-[260px] bg-contain bg-left-top bg-no-repeat"
-        style={{
-          backgroundImage: `url(${blurredDashboardBackgroundMenuTop})`,
-          aspectRatio: "auto",
-          height: "100vh",
-          backgroundSize: "260px auto",
-        }}
-      />
+      <div className="absolute left-0 top-0 w-[260px] bg-menu-top" />

Also consider using 100dvh (dynamic viewport height) instead of 100vh for better mobile compatibility.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7b54c35 and c23ae25.

⛔ Files ignored due to path filters (3)
  • apps/webapp/app/assets/images/blurred-dashboard-background-menu-bottom.jpg is excluded by !**/*.jpg
  • apps/webapp/app/assets/images/blurred-dashboard-background-menu-top.jpg is excluded by !**/*.jpg
  • apps/webapp/app/assets/images/blurred-dashboard-background-table.jpg is excluded by !**/*.jpg
📒 Files selected for processing (7)
  • apps/webapp/app/components/BackgroundWrapper.tsx (1 hunks)
  • apps/webapp/app/components/layout/AppLayout.tsx (1 hunks)
  • apps/webapp/app/components/primitives/Spinner.tsx (1 hunks)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx (3 hunks)
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx (2 hunks)
  • apps/webapp/app/routes/_app.orgs.new/route.tsx (2 hunks)
  • apps/webapp/app/routes/confirm-basic-details.tsx (3 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Always prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code
For TypeScript, we usually use types over interfaces
Avoid enums
No default exports, use function declarations

Files:

  • apps/webapp/app/components/primitives/Spinner.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx
  • apps/webapp/app/components/layout/AppLayout.tsx
  • apps/webapp/app/components/BackgroundWrapper.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx
  • apps/webapp/app/routes/_app.orgs.new/route.tsx
  • apps/webapp/app/routes/confirm-basic-details.tsx
{packages/core,apps/webapp}/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

We use zod a lot in packages/core and in the webapp

Files:

  • apps/webapp/app/components/primitives/Spinner.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx
  • apps/webapp/app/components/layout/AppLayout.tsx
  • apps/webapp/app/components/BackgroundWrapper.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx
  • apps/webapp/app/routes/_app.orgs.new/route.tsx
  • apps/webapp/app/routes/confirm-basic-details.tsx
apps/webapp/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/webapp.mdc)

apps/webapp/**/*.{ts,tsx}: In the webapp, all environment variables must be accessed through the env export of env.server.ts, instead of directly accessing process.env.
When importing from @trigger.dev/core in the webapp, never import from the root @trigger.dev/core path; always use one of the subpath exports as defined in the package's package.json.

Files:

  • apps/webapp/app/components/primitives/Spinner.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx
  • apps/webapp/app/components/layout/AppLayout.tsx
  • apps/webapp/app/components/BackgroundWrapper.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx
  • apps/webapp/app/routes/_app.orgs.new/route.tsx
  • apps/webapp/app/routes/confirm-basic-details.tsx
🧠 Learnings (2)
📚 Learning: applies to apps/webapp/app/v3/presenters/**/*.server.ts : favor the use of 'presenters' to move comp...
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .cursor/rules/webapp.mdc:0-0
Timestamp: 2025-07-18T17:49:47.180Z
Learning: Applies to apps/webapp/app/v3/presenters/**/*.server.ts : Favor the use of 'presenters' to move complex loader code into a class, as seen in `app/v3/presenters/**/*.server.ts`.

Applied to files:

  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx
  • apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx
📚 Learning: applies to {packages/core,apps/webapp}/**/*.{ts,tsx} : we use zod a lot in packages/core and in the ...
Learnt from: CR
PR: triggerdotdev/trigger.dev#0
File: .github/copilot-instructions.md:0-0
Timestamp: 2025-07-18T17:49:24.468Z
Learning: Applies to {packages/core,apps/webapp}/**/*.{ts,tsx} : We use zod a lot in packages/core and in the webapp

Applied to files:

  • apps/webapp/app/routes/confirm-basic-details.tsx
🧬 Code Graph Analysis (2)
apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx (4)
apps/webapp/app/components/layout/AppLayout.tsx (1)
  • AppContainer (4-16)
apps/webapp/app/components/BackgroundWrapper.tsx (1)
  • BackgroundWrapper (6-48)
apps/webapp/app/components/primitives/Headers.tsx (1)
  • Header1 (32-50)
apps/webapp/app/routes/resources.orgs.$organizationSlug.select-plan.tsx (1)
  • PricingPlans (213-244)
apps/webapp/app/components/layout/AppLayout.tsx (1)
apps/webapp/app/utils/cn.ts (1)
  • cn (77-79)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
  • GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
  • GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
  • GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
  • GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
  • GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
  • GitHub Check: typecheck / typecheck
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (14)
apps/webapp/app/components/BackgroundWrapper.tsx (1)

6-48: LGTM! Well-structured component with proper layering.

The component correctly implements the layered background approach with proper z-index management to ensure content visibility. The fixed-width left menu backgrounds and full-width right background create the desired dashboard effect.

apps/webapp/app/routes/_app.orgs.$organizationSlug_.select-plan/route.tsx (1)

52-68: LGTM! Consistent layout restructuring aligned with PR objectives.

The nested AppContainer > BackgroundWrapper structure follows the same pattern applied across other routes in this PR. The styling enhancements (rounded corners, border, shadow) improve visual presentation while maintaining all existing functionality.

apps/webapp/app/components/layout/AppLayout.tsx (1)

4-15: LGTM! Clean API enhancement with proper class merging.

The addition of the optional className prop follows established patterns in the codebase and enables the styling flexibility needed for the new layout structure. The use of the cn utility ensures proper Tailwind class merging.

apps/webapp/app/components/primitives/Spinner.tsx (1)

69-70: LGTM! Appropriate color update for dark theme compatibility.

The change from black to white spinner colors ensures proper visibility on the dark backgrounds introduced by BackgroundWrapper. The rgba values follow the existing pattern used in other color options.

apps/webapp/app/routes/_app.orgs.$organizationSlug_.projects.new/route.tsx (1)

141-196: LGTM! Consistent implementation of new layout pattern.

The restructuring follows the same AppContainer > BackgroundWrapper pattern applied across other routes in this PR. The enhanced styling for MainCenteredContainer and the button variant update align with the overall UI improvements while maintaining all existing functionality.

apps/webapp/app/routes/_app.orgs.new/route.tsx (4)

10-11: LGTM!

The new imports for BackgroundWrapper and updated AppContainer are correctly structured and align with the UI enhancement objectives.


98-100: LGTM!

The new container hierarchy with AppContainer, BackgroundWrapper, and styled MainCenteredContainer properly implements the UI enhancement goals. The styling classes are appropriate and the nesting structure is logical.

Also applies to: 182-184


118-164: LGTM!

The form reorganization logically groups the company size and problem description inputs within the managed cloud conditional block. This improves the user experience by showing related fields together while maintaining all existing form logic and validation.


166-180: LGTM!

The form buttons maintain all existing functionality including conditional rendering of the cancel button and proper loading state handling, while fitting well within the new UI structure.

apps/webapp/app/routes/confirm-basic-details.tsx (5)

11-11: LGTM!

The BackgroundWrapper import is correctly added and follows the same pattern as other updated routes.


117-117: LGTM!

The icon color update from text-amber-300 to text-amber-400 provides better visual consistency and slightly improved contrast.


142-144: LGTM!

The container structure follows the same consistent pattern as other updated routes, providing a unified UI experience with proper styling and background enhancements.

Also applies to: 241-242


171-230: LGTM!

The form field reorganization improves user experience by presenting fields in a logical order. The conditional rendering logic for email confirmation and referral source is correctly maintained.


225-225: LGTM!

The updated placeholder text to include "LLM" reflects current market trends and provides users with relevant examples of referral sources.

@matt-aitken matt-aitken merged commit 51305b6 into main Aug 7, 2025
31 checks passed
@matt-aitken matt-aitken deleted the onboarding-dashboard-background branch August 7, 2025 15:13
nicktrn pushed a commit that referenced this pull request Aug 7, 2025
* Adds a background image dashboard wrapper

* Dashboard background image

* Adds a background image to the welcome onboarding page

* Background is constructed of 3 images

* Adds the background to the create org page

* Adds a background to the choose plan page

* Change the default button spinner color to white

* Adds the background to the create new project page

* Updates the invite team member page

* Adds background image to received invite page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants