[Bug]: Documentation and Changelog footer links are non-functional

[ruhelamahi7-code]

Before submitting

• I have searched existing issues to make sure this is not a duplicate.
• I have read the contribution guidelines.

Bug summary

Documentation and Changelog footer links are non-functional

Steps to reproduce

1. Visit https://codelensx.vercel.app
2. Scroll down to the footer section
3. Under "RESOURCES", hover or click on "DOCUMENTATION" or "CHANGELOG"
4. Observe that the cursor shows a "not-allowed" (🚫) icon and nothing happens on click

Expected behavior

Either:

• The links should navigate to actual Documentation and Changelog
  pages (even simple placeholder pages), OR
• If these features aren't ready yet, the links should be clearly
  marked as "Coming Soon" (similar to the "SOON" badge already used
  for "LEETCODE AUTH" in the Integrations section of the same footer)

Actual behavior

Clicking "DOCUMENTATION" or "CHANGELOG" does nothing. The mouse
cursor changes to a "not-allowed" (🚫) icon, confirming these links
are disabled/non-functional. Meanwhile, "BUG REPORTS" right below
them in the same list works correctly as a clickable link, creating
an inconsistent user experience.

Screenshots or recordings

Browser and device information

Browser: Chrome (latest)
Device: MacBook Air
OS: macOS
Screen size: Desktop

Additional context

This appears to be either a missing href/route, or intentionally
disabled placeholder links without proper "Coming Soon" styling.
Suggested fix: either implement basic placeholder pages for
/docs and /changelog routes, or add a "Coming Soon" badge
consistent with the existing design pattern. I am a registered
GSSoC 2026 contributor and would like to implement this fix myself.

[ruhelamahi7-code]

Hi @kunalverma2512! 👋

I'd like to work on this issue! Based on my investigation, the
fix likely involves either:

• Adding proper href/route values for the Documentation and
  Changelog links in the footer component, or
• Adding a "Coming Soon" badge/tooltip consistent with the
  "SOON" badge already used for LeetCode Auth in the
  Integrations section, if these pages aren't ready yet

Could you please assign this issue to me? I'll submit a PR
soon! 😊

[kunalverma2512]

@ruhelamahi7-code Thanks for noticing CodeLens
But since we dont have documentation and Changelog Pages we cannot redirect these footer links to their respective pages

But for this issue I wanted that you provide some custom pop up for showing "Comming Soon" message with some more description (not too large) about codelens in that pop up and some hyperlink to explore page , FAQ page , About page

please make sure you give your creative and innovative mind and follow current design rules to make the custom popup

VERY IMPORTANT : make sure this custom popup behave as a special popup i.e general component (inside src/components/ui) so that in future if we decide to make new features but not created at that time then we can use this custom Coming soon popup component

Welcome to Codelens and make sure to join out discord , community

[kunalverma2512]

@ruhelamahi7-code I have also updated readme.md so refer it for proper local setup

[ruhelamahi7-code]

Thank you for the detailed guidance, @kunalverma2512! 🙏

Just to confirm my understanding before I start:

1. I'll create a reusable "ComingSoon" popup component inside
   src/components/ui/ (so it's general and reusable for future
   features)
2. The popup will show a short description about CodeLens
3. It will include hyperlinks to Explore, FAQ, and About pages
4. I'll trigger this popup when clicking "Documentation" or
   "Changelog" in the footer, instead of using disabled links
5. I'll match the site's existing bold/minimalist design style

I'll go through the updated README for local setup and get
started!

[kunalverma2512]

@ruhelamahi7-code

This is a great example of how open source contributions should start. You didn't just point out the issue you investigated the behavior, understood the context, and came up with possible solutions before asking for the assignment. That initiative is genuinely appreciated.

I've assigned this to you. Take your time to design a reusable and polished ComingSoon component that can serve CodeLens well in the future too. Focus on clean implementation, good UX, and consistency with the existing design. Looking forward to your PR.

Welcome and you can support this project by starring it
Good Luck

[kunalverma2512]

@ruhelamahi7-code Make sure you update your work in our matrix developement channel and your intro in welcome room

[ruhelamahi7-code]

Hi @kunalverma2512! 👋

I've completed work on this issue and submitted a PR for review!

🛠️ What I Built

• ComingSoonModal.jsx — a generic, reusable popup component
  in src/components/ui/, built so it can be reused for any
  future "coming soon" features without rebuilding from scratch
• Replaced the disabled Documentation and Changelog footer links
  (which previously did nothing on click) with buttons that
  trigger the modal
• The modal includes a short description about CodeLens and
  quick navigation links to Explore, FAQ, and About pages
• Followed the strict Brutalist design system exactly — pure
  black/white, thick borders, hard offset shadows
  (shadow-[16px_16px_0_0_rgba(0,0,0,1)]), zero rounded corners,
  and the same typography patterns (font-black uppercase tracking-widest)

🔧 Additional Fixes (from CodeRabbit's review)

• Added a proper ScrollToTop component using useLocation +
  useEffect, rendered once in App.jsx so it now works app-wide
  on every route change — this also fixed an existing bug where
  pages would load mid-scroll instead of at the top
• Added an Escape key handler to the modal for accessibility,
  so keyboard users can dismiss it without relying on mouse clicks

✅ Quality Checks

• ESLint passes with zero errors on all changed files
• Tested on desktop and mobile viewports
• All CodeRabbit feedback addressed and conversations resolved
• No conflicts with main — merged cleanly

🔗 Pull Request

➡️ #234

I've also joined the Matrix community and introduced myself there.
Really enjoyed working through the design system constraints on
this one — please let me know if you'd like any adjustments! 😊