Skip to content

Hide broken Discord and Email link and update layout classes#288

Closed
jnakaigen wants to merge 1 commit into
CCExtractor:mainfrom
jnakaigen:patch-1
Closed

Hide broken Discord and Email link and update layout classes#288
jnakaigen wants to merge 1 commit into
CCExtractor:mainfrom
jnakaigen:patch-1

Conversation

@jnakaigen
Copy link
Copy Markdown

@jnakaigen jnakaigen commented Dec 21, 2025

Description

This PR fixes a layout alignment issue in the "Contact Us" section and temporarily hides incomplete contact options to improve user experience.

Changes made:

  1. Hidden Broken Links: Commented out the "Discord" and "Email" cards in the contactList array. These items had empty URL strings (''), which caused the page to reload or jump when clicked.
  2. Improved Layout: Switched the container class from a fixed 4-column grid (grid lg:grid-cols-4) to a flexible centered layout (flex flex-wrap justify-center). This ensures the remaining two cards (Zulip and Github) are perfectly centered on the screen, rather than being stuck on the left side.

Checklist

  • Ran npx prettier --write . (for formatting)
  • Ran gofmt -w . (for Go backend)
  • Ran npm test (for JS/TS testing)
  • Added unit tests, if applicable
  • Verified all tests pass
  • Updated documentation, if needed

Additional Notes

The switch to flex-wrap is future-proof; if the Discord and Email links are uncommented later, the layout will automatically adjust to center all 4 items again.

Note to Maintainers: I commented out the Discord and Email sections because their URLs were missing. If you have the valid invite links, let me know and I can update the URLs file and uncomment these sections.

Temporarily hide broken links for Discord and adjust layout classes.
@github-actions
Copy link
Copy Markdown

Thank you for opening this PR!

Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools.

Please take a moment to:

  • Check the "Files changed" tab
  • Leave comments on any lines for functions, comments, etc. that are important, non-obvious, or may need attention
  • Clarify decisions you made or areas you might be unsure about and/or any future updates being considered.
  • Finally, submit all the comments!

More information on how to conduct a self review:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request

This helps make the review process smoother and gives us a clearer understanding of your thought process.

Once you've added your self-review, we'll continue from our side. Thank you!

@its-me-abhishek
Copy link
Copy Markdown
Collaborator

This is not really required, closing until we find something else instead!

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.

2 participants