Skip to content

Improve landing page conversion by directing primary CTA to upload page#494

Open
mahek2016 wants to merge 2 commits intoAOSSIE-Org:mainfrom
mahek2016:feature/landing-page-483
Open

Improve landing page conversion by directing primary CTA to upload page#494
mahek2016 wants to merge 2 commits intoAOSSIE-Org:mainfrom
mahek2016:feature/landing-page-483

Conversation

@mahek2016
Copy link

@mahek2016 mahek2016 commented Feb 27, 2026

Addressed Issues:

Fixes #483

Screenshots/Recordings:

  • No UI redesign was introduced.
  • Only CTA navigation targets were updated to improve onboarding flow.
  • Landing page layout remains unchanged.

Additional Notes:

This PR improves the landing page conversion flow by directing the primary CTA button to the upload page (/input) instead of the intermediate question-type page.
This reduces friction and aligns with the issue goal of making the product clearer within 5–10 seconds for first-time users.

No structural, styling, or layout changes were introduced.

Checklist

  • My PR addresses a single issue, fixes a single bug or makes a single improvement.
  • My code follows the project's code style and conventions
  • If applicable, I have made corresponding changes or additions to the documentation
  • If applicable, I have made corresponding changes or additions to tests
  • My changes generate no new warnings or errors
  • I have joined the Discord server and I will share a link to this PR with the project maintainers there
  • I have read the Contribution Guidelines
  • Once I submit my PR, CodeRabbit AI will automatically review it and I will address CodeRabbit's comments.

AI Usage Disclosure

  • This PR does not contain AI-generated code at all.
  • This PR contains AI-generated code. I have tested the code locally and I am responsible for it.

I have used the following AI tools:
ChatGPT (for guidance and review)

Summary by CodeRabbit

  • Features

    • Updated navigation flow to streamline the user path through the application interface.
  • Style

    • Fixed import statement formatting and applied minor layout adjustments for improved consistency.

@coderabbitai
Copy link

coderabbitai bot commented Feb 27, 2026

Warning

Rate limit exceeded

@mahek2016 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 13 minutes and 57 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 12c80c0 and 90cdff3.

📒 Files selected for processing (1)
  • eduaid_web/src/pages/Home.jsx
📝 Walkthrough

Walkthrough

The Home page component was updated to redirect users to the /input route instead of /question-type when clicking primary action buttons. An inline comment was added to document this navigation change, supporting the landing page conversion optimization effort.

Changes

Cohort / File(s) Summary
Landing Page Navigation Update
eduaid_web/src/pages/Home.jsx
Updated button navigation target from /question-type to /input with explanatory comment. Minor formatting adjustments and import statement cleanup.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A hop, a click, a faster way,
From Home to Input, users now stay,
The landing page gleams bright and clear,
"Upload your notes!" rings loud and dear,
Conversion blooms where paths align,
Our EduAid journey now does shine! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the primary CTA navigation from /question-type to /input page to improve conversion.
Linked Issues check ✅ Passed The PR directly addresses issue #483 by redirecting the primary CTA to the upload page (/input), fulfilling the core objective to push users to upload files and reduce friction.
Out of Scope Changes check ✅ Passed All changes are narrowly focused on updating CTA navigation from /question-type to /input; no UI redesign, styling, or unrelated modifications were introduced.
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

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 and usage tips.

Copy link

@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: 1

🧹 Nitpick comments (1)
eduaid_web/src/pages/Home.jsx (1)

88-88: Remove PR-context inline comment from production JSX.

Line 88 (Only change here...) is diff-context metadata and will go stale; prefer removing it or replacing it with a product-intent comment.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@eduaid_web/src/pages/Home.jsx` at line 88, In Home.jsx remove the
diff-context comment "/* ✅ Only change here: /question-type → /input */" from
the JSX (inside the Home component) — either delete it entirely or replace it
with a product-intent comment that explains the UI intent (e.g., why the route
changed) so the JSX no longer contains PR-specific metadata.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@eduaid_web/src/pages/Home.jsx`:
- Around line 89-101: Remove the nested <button> elements inside the React
Router <Link> components for the "/input" and "/history" links and move the
button-related attributes/classes to the <Link> itself (e.g., copy classes like
"w-full sm:w-auto items-center text-lg flex justify-center gap-3 text-white px-6
py-3 border-gradient hover:wave-effect rounded-md transition-all duration-300"
and the inner text plus <img> into the Link), so that <Link to="/input"> and
<Link to="/history"> are the interactive elements instead of wrapping a
<button>; ensure semantics and keyboard behavior remain by preserving role/aria
attributes if used elsewhere.

---

Nitpick comments:
In `@eduaid_web/src/pages/Home.jsx`:
- Line 88: In Home.jsx remove the diff-context comment "/* ✅ Only change here:
/question-type → /input */" from the JSX (inside the Home component) — either
delete it entirely or replace it with a product-intent comment that explains the
UI intent (e.g., why the route changed) so the JSX no longer contains
PR-specific metadata.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fc3bf1a and 12c80c0.

📒 Files selected for processing (1)
  • eduaid_web/src/pages/Home.jsx

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.

[FEATURE]: Build best, conversion-optimized landing Page for EduAid

1 participant