Skip to content

fix: make onboarding responsive - #237

Open
AmzBG wants to merge 2 commits into
mhmdfarhat-mhmdali-amirfrom
feat/responsive-onboarding
Open

fix: make onboarding responsive#237
AmzBG wants to merge 2 commits into
mhmdfarhat-mhmdali-amirfrom
feat/responsive-onboarding

Conversation

@AmzBG

@AmzBG AmzBG commented Aug 10, 2026

Copy link
Copy Markdown
Collaborator

Description

  • Make the developer onboarding handle field responsive by stacking the public URL prefix above the input on narrow screens.
  • Preserve the inline URL layout on tablet and desktop widths.
  • Reduce mobile card padding and keep the onboarding progress header within the viewport.
  • Stack onboarding actions as full-width buttons on mobile while retaining the desktop footer layout.
  • Make the recruiter organization-type selector full width and verify both recruiter onboarding steps at phone widths.
  • Position mobile onboarding from the top so the form remains reachable when the software keyboard opens.
  • Pin the local Redis container to version 8.8.1 instead of the floating latest tag.

Link to issue or ticket

N/A

Steps to QA

  1. Complete developer signup and open onboarding from a magic link on a phone-sized viewport.
  2. Confirm the public profile URL appears above the handle input and that the input is fully visible without rotating the device.
  3. Continue to developer details and confirm every field and both footer actions fit without horizontal scrolling.
  4. Repeat onboarding with a recruiter account and confirm the organization fields, details fields, and actions remain fully visible.
  5. Verify the URL prefix and handle input return to one row at tablet and desktop widths.
  6. Run docker compose config and confirm the Redis service resolves to redis:8.8.1.
  7. Run npm test --workspace=api -- --runInBand and confirm all 125 tests pass.
  8. Run npx turbo run lint, npx turbo run check-types, and npm run format:check.

Screenshots

Before

image

After

image

Summary by CodeRabbit

  • Improvements
    • Refined the onboarding experience with more responsive spacing, alignment, sizing, and layout behavior across screen sizes.
    • Improved the profile URL display and organization selection area for mobile and desktop use.
    • Updated onboarding navigation and submission controls to adapt better on smaller screens.
    • Completed profiles now transition cleanly to the dashboard without displaying debug information.

@AmzBG AmzBG self-assigned this Aug 10, 2026
@AmzBG AmzBG added the enhancement New feature or request label Aug 10, 2026
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The onboarding flow now initializes the profile host after mount and uses responsive layout and control styles. The Redis service now uses the pinned redis:8.8.1 image.

Changes

Onboarding flow

Layer / File(s) Summary
Mounted profile host initialization
apps/web/components/onboarding-wizard.tsx
The wizard reads window.location.host after mounting and uses the value in the profile URL prefix.
Responsive onboarding layout and controls
apps/web/app/onboarding/page.tsx, apps/web/components/onboarding-wizard.tsx
The onboarding page, form, footer, and buttons use responsive spacing, alignment, sizing, wrapping, and width classes.

Redis image version

Layer / File(s) Summary
Pinned Redis service image
docker-compose.yml
The Redis service uses redis:8.8.1 instead of redis:latest.

Estimated code review effort: 2 (Simple) | ~15 minutes

Possibly related PRs

Suggested reviewers: mohamad12farhat, mohamadbakawi

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the primary change: responsive onboarding layouts.
Description check ✅ Passed The description includes the required sections, detailed changes, QA steps, and screenshots for this UI change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/responsive-onboarding

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install failed: one or more packages not found in the registry.


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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
docker-compose.yml (1)

17-17: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick win

Pin the Redis image by digest for reproducible deployments.

Replace redis:8.8.1 with the resolved multi-platform manifest digest:

Proposed change
-    image: redis:8.8.1
+    image: redis@sha256:3eafabb4c93fcb8b36b666e07a43f096cb157bc6b07dce4b2492b895c63cf37f
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docker-compose.yml` at line 17, Update the Redis service’s image reference
from the version tag in docker-compose.yml to the resolved multi-platform
manifest digest, preserving the existing Redis image while ensuring reproducible
deployments.

Source: MCP tools

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/web/components/onboarding-wizard.tsx`:
- Around line 502-512: Update the CardFooter action layout in the onboarding
wizard so mobile rendering preserves the DOM order, with Back before Complete
Setup. Replace the reversing flex direction or explicitly apply responsive order
classes, while preserving the existing desktop arrangement and alignment
behavior.

---

Nitpick comments:
In `@docker-compose.yml`:
- Line 17: Update the Redis service’s image reference from the version tag in
docker-compose.yml to the resolved multi-platform manifest digest, preserving
the existing Redis image while ensuring reproducible deployments.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 922fb4bf-1edc-4ec0-a4c7-3c9836fb17a9

📥 Commits

Reviewing files that changed from the base of the PR and between 9596543 and ba136ec.

📒 Files selected for processing (3)
  • apps/web/app/onboarding/page.tsx
  • apps/web/components/onboarding-wizard.tsx
  • docker-compose.yml

Comment on lines +502 to +512
<CardFooter
className={`flex flex-col-reverse items-stretch gap-3 border-t bg-muted/10 px-4 pt-6 sm:flex-row sm:items-center sm:px-6 ${
step === 1 ? 'sm:justify-end' : 'sm:justify-between'
}`}
>
{step !== 1 && (
<Button
key="back-btn"
type="button"
variant="outline"
className="w-full sm:w-auto"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Keep the mobile action order consistent with the DOM.

On step 2, the DOM lists Back before Complete Setup, but flex-col-reverse renders Complete Setup above Back on narrow screens. Keyboard and screen-reader focus still follows the DOM, so the visual and interaction order differ. Use flex-col or reorder the buttons and restore the desktop order with responsive order-* classes.

Proposed minimal fix
-          className={`flex flex-col-reverse items-stretch gap-3 border-t bg-muted/10 px-4 pt-6 sm:flex-row sm:items-center sm:px-6 ${
+          className={`flex flex-col items-stretch gap-3 border-t bg-muted/10 px-4 pt-6 sm:flex-row sm:items-center sm:px-6 ${
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<CardFooter
className={`flex flex-col-reverse items-stretch gap-3 border-t bg-muted/10 px-4 pt-6 sm:flex-row sm:items-center sm:px-6 ${
step === 1 ? 'sm:justify-end' : 'sm:justify-between'
}`}
>
{step !== 1 && (
<Button
key="back-btn"
type="button"
variant="outline"
className="w-full sm:w-auto"
<CardFooter
className={`flex flex-col items-stretch gap-3 border-t bg-muted/10 px-4 pt-6 sm:flex-row sm:items-center sm:px-6 ${
step === 1 ? 'sm:justify-end' : 'sm:justify-between'
}`}
>
{step !== 1 && (
<Button
key="back-btn"
type="button"
variant="outline"
className="w-full sm:w-auto"
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/web/components/onboarding-wizard.tsx` around lines 502 - 512, Update the
CardFooter action layout in the onboarding wizard so mobile rendering preserves
the DOM order, with Back before Complete Setup. Replace the reversing flex
direction or explicitly apply responsive order classes, while preserving the
existing desktop arrangement and alignment behavior.

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

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant