Skip to content

Add FAQ navigation CTA button Fixes #42#65

Merged
kunalverma2512 merged 1 commit into
kunalverma2512:mainfrom
bhavya-tyagi20:faq-navigation-v2
May 16, 2026
Merged

Add FAQ navigation CTA button Fixes #42#65
kunalverma2512 merged 1 commit into
kunalverma2512:mainfrom
bhavya-tyagi20:faq-navigation-v2

Conversation

@bhavya-tyagi20
Copy link
Copy Markdown

@bhavya-tyagi20 bhavya-tyagi20 commented May 16, 2026

Fixes #42

Added a “View All FAQs” CTA button in the FAQ section to improve navigation and prepare for future scalability.

The button routes to /faq using React Router. No new routes or pages were added, as per issue constraints.

Changes are limited strictly to the FAQ section and maintain UI consistency and responsiveness.
Screenshot 2026-05-16 140936

Summary by CodeRabbit

  • New Features
    • Added a "View All FAQs" call-to-action button within the FAQ section, providing direct navigation to the complete FAQ page.

Review Change Stack

@github-actions
Copy link
Copy Markdown

🚀 PR Received Successfully

Hello @bhavya-tyagi20,

Thank you for taking the initiative to contribute to this project.

Please ensure that your PR follows all project guidelines properly before requesting review.

⚠️ Important Instructions

  • Maintain proper code quality and structure
  • Do not make unnecessary changes/files
  • Ensure responsiveness across devices
  • Follow existing project conventions strictly
  • Attach screenshots/videos for UI-related changes
  • Resolve merge conflicts before requesting review
  • Avoid AI-generated low quality PRs or copied implementations

📌 Mandatory for GSSoC'26 Participants

Joining the community group and announcement channel is compulsory for all contributors participating through GSSoC'26.

Failure to follow contribution guidelines may lead to PR rejection.

We appreciate your effort and wish you a great open-source journey ahead. ✨

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 16, 2026

📝 Walkthrough

Walkthrough

FAQ navigation link added to FAQSection component: Link import from react-router-dom enables a "View All FAQs" button routing to /faq, integrated into App.jsx, with minor formatting adjustments throughout. ExplorePage receives whitespace-only changes unrelated to this feature.

Changes

FAQ Navigation CTA

Layer / File(s) Summary
FAQ CTA button implementation and routing
frontend/src/App.jsx, frontend/src/components/explore/FAQSection.jsx
FAQSection imports Link from react-router-dom and renders a "View All FAQs" CTA button that navigates to /faq. App.jsx imports and integrates FAQSection. Minor whitespace adjustments are made within the FAQ container and component markup.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

  • #29: Main change directly implements the requested "View All FAQs" navigation button linking to /faq as a CTA within the FAQ section.

Poem

🐰 A rabbit hops through the FAQs with glee,
A button appears—"View All," you see!
To /faq it routes, so smooth and so swift,
A link-laden gift to improve the drift!
Navigation flows now, no question remains,
The answer awaits in those knowledge domains! 📚✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the main change: adding a FAQ navigation CTA button to fix issue #42, which aligns with the primary objective of the pull request.
Linked Issues check ✅ Passed The PR successfully implements all requirements from issue #42: adds a 'View All FAQs' button in FAQSection, uses React Router for /faq navigation, maintains brutalist UI consistency, and keeps changes strictly within UI scope without backend modifications.
Out of Scope Changes check ✅ Passed All changes are scoped to the FAQ section functionality. Minor formatting adjustments in ExplorePage and FAQSection imports are directly related to integrating the new navigation button feature.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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
Copy Markdown

@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

🤖 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 `@frontend/src/components/explore/FAQSection.jsx`:
- Around line 77-82: The Link in FAQSection.jsx currently points to "/faq" (the
Link component instance with to="/faq") but there is no "/faq" route registered
in the router; either register a route handler for "/faq" in your router
configuration (e.g., add a Route for path="/faq" that renders the FAQ page
component) or change the Link's target to an existing route (for example to the
existing help/knowledgebase route) so the CTA doesn't hit NotFound; update
either the router's route table or the Link's to value accordingly.
🪄 Autofix (Beta)

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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6e44b38d-f133-4b37-9128-2b138a63e1ae

📥 Commits

Reviewing files that changed from the base of the PR and between 89f2178 and fac431d.

📒 Files selected for processing (3)
  • frontend/src/App.jsx
  • frontend/src/components/explore/FAQSection.jsx
  • frontend/src/pages/ExplorePage.jsx

Comment on lines +77 to +82
<Link
to="/faq"
className="border-3 border-black px-5 py-2 text-sm sm:text-base font-black uppercase bg-white tracking-widest shadow-[5px_5px_0_0_rgba(0,0,0,1)] text-black transition-all duration-200 hover:bg-black hover:text-white hover:translate-x-1 hover:translate-y-1"
>
View All FAQs
</Link>
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

/faq CTA target is not registered in the current router.

Line 78 navigates to /faq, but the provided route table has no /faq route, so this CTA likely lands on NotFound. Please either add a matching route or point this CTA to an existing destination until /faq is available.

🤖 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 `@frontend/src/components/explore/FAQSection.jsx` around lines 77 - 82, The
Link in FAQSection.jsx currently points to "/faq" (the Link component instance
with to="/faq") but there is no "/faq" route registered in the router; either
register a route handler for "/faq" in your router configuration (e.g., add a
Route for path="/faq" that renders the FAQ page component) or change the Link's
target to an existing route (for example to the existing help/knowledgebase
route) so the CTA doesn't hit NotFound; update either the router's route table
or the Link's to value accordingly.

@kunalverma2512
Copy link
Copy Markdown
Owner

@coderabbitai The /faq route is intentionally not implemented yet.

Current scope of this PR was limited to adding the CTA button and preparing navigation flow for future FAQ expansion. Redirecting to the fallback route temporarily is acceptable for the current stage of the project.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 16, 2026

Tip

For best results, initiate chat on the files or code changes.

@kunalverma2512 Understood — thanks for the clarification! The staged approach makes sense here: establish the CTA button and navigation intent first, then build out the full /faq page in a subsequent PR.

Would you like me to open a follow-up GitHub issue to track the implementation of the /faq route and its dedicated page? That way it's formally captured and linked to this PR for future reference.


✏️ Learnings added
Learnt from: kunalverma2512
URL: https://github.com/kunalverma2512/CodeLens/pull/65

Timestamp: 2026-05-16T08:51:13.030Z
Learning: In the CodeLens project (GitHub: kunalverma2512/CodeLens), the `/faq` route is intentionally not implemented yet. The "View All FAQs" CTA button added in PR `#65` links to `/faq` as a placeholder for future expansion. Routing to the fallback is acceptable in the interim. Do not flag the missing `/faq` route as a blocking issue in this or related PRs.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

@kunalverma2512
Copy link
Copy Markdown
Owner

@bhavya-tyagi20 Proper implementation.

Scope was followed correctly, changes are controlled, and unnecessary modifications were avoided. Continue maintaining this level of contribution quality.

@kunalverma2512 kunalverma2512 self-assigned this May 16, 2026
@kunalverma2512 kunalverma2512 merged commit 4879f17 into kunalverma2512:main May 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants