Skip to content

Feature/faq page#991

Open
kunwarshivamjsr wants to merge 2 commits into
rishabh0510rishabh:mainfrom
kunwarshivamjsr:feature/faq-page
Open

Feature/faq page#991
kunwarshivamjsr wants to merge 2 commits into
rishabh0510rishabh:mainfrom
kunwarshivamjsr:feature/faq-page

Conversation

@kunwarshivamjsr

@kunwarshivamjsr kunwarshivamjsr commented Jun 11, 2026

Copy link
Copy Markdown

GSSoC 2026 Contribution

This PR is part of GSSoC 2026 (GirlScript Summer of Code).
Related Issue: #990

Summary

Fixes #990 — Adds a new /faq page to replace the empty
/coming-soon placeholder that footer links pointed to.

Changes

  • Created frontend/src/app/faq/page.tsx — styled FAQ accordion page
  • Updated FAQ link in Footer.tsx to point to /faq
  • Fixed duplicate parameter declaration bug in layout.tsx
    that was causing a build error
  • Removed dead NavigationContext code from layout.tsx
    that was causing a Client Component error

Type of Change

  • New feature (non-breaking, frontend only)
  • Bug fix (pre-existing layout.tsx errors)

Screenshots

image image

Summary by CodeRabbit

  • New Features

    • Added a comprehensive FAQ page featuring expandable questions and answers for common inquiries.
  • Updates

    • Footer navigation updated to direct users to the new FAQ resource.

@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the rishabhmishra0510-5147's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e8c36b81-15e2-42a4-9fea-521d28d4ac54

📥 Commits

Reviewing files that changed from the base of the PR and between 7f59a96 and e6844f0.

⛔ Files ignored due to path filters (1)
  • frontend/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • frontend/src/app/components/Footer.tsx
  • frontend/src/app/faq/page.tsx
  • frontend/src/app/layout.tsx

📝 Walkthrough

Walkthrough

This PR implements a new FAQ page to replace the coming-soon placeholder, updates the footer navigation to point to /faq, and restructures the root layout to integrate the Navbar component while removing the NavigationProvider and useNavigation exports.

Changes

FAQ Feature and Layout Shell Restructuring

Layer / File(s) Summary
FAQ Page Implementation and Footer Integration
frontend/src/app/faq/page.tsx, frontend/src/app/components/Footer.tsx
New FAQPage component with inline Q&A dataset rendered as expandable details/summary items styled with CSS variables. Footer Resources link updated from "API Reference" (/coming-soon) to "FAQ" (/faq).
Layout Shell Restructuring and Navigation Context Cleanup
frontend/src/app/layout.tsx
RootLayout now renders Navbar and wraps children in a main element with existing minHeight and paddingTop styling. Removes NavigationProvider and useNavigation exports. Comment blocks around canonical URL guidance and RootLayout parameters removed.

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly Related PRs

Suggested Labels

level3

Suggested Reviewers

  • rishabh0510rishabh

🐰 A page of questions answered with care,
The footer now points folks right there,
With Navbar and main wrapped up tight,
The layout restructured just right,
FAQ time—no more placeholders bare!

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Linked Issues check ❓ Inconclusive The PR implements most core requirements from #990: FAQ page created with collapsible UI, footer link updated to /faq. However, the FAQAccordion component requirement and some content requirements cannot be fully verified. The raw_summary shows /faq page implementation and Footer update, but indicates no separate FAQAccordion component file. Confirm whether FAQ styling is appropriately componentized or if a distinct component was intended but omitted.
✅ 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 'Feature/faq page' directly corresponds to the main objective of adding a new FAQ page feature.
Out of Scope Changes check ✅ Passed All changes directly address #990 requirements: new FAQ page, updated footer link, and layout.tsx fixes resolve mentioned build/Client Component errors.
Description check ✅ Passed The PR includes comprehensive description with clear summary of changes, motivation (fixing /coming-soon), and visual evidence via screenshots.
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

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.

@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

🔍 PR Action Required

Hi @kunwarshivamjsr,

We detected some items on this Pull Request that require attention:

❌ Failing CI Checks

The following check runs or commit statuses are failing (ignoring vercel):

Please resolve the issues above to proceed.


Last updated: Thu, 11 Jun 2026 10:02:00 GMT

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.

[Enhancement] Replace "Coming Soon" placeholder with a real FAQ page

1 participant