Visitar URL original
[UI]: Unwanted border and incorrect Layer5 logo color in “Join the Conversation” box · Issue #7958 · layer5io/layer5 · GitHub
Skip to content

[UI]: Unwanted border and incorrect Layer5 logo color in “Join the Conversation” box #7958

Open

Description

@Maanvi212006

Description

The “JOIN THE CONVERSATION” box on the Layer5 Community page has an unintended white border around the container. Additionally, the Layer5 logo displayed inside the box has incorrect/inconsistent colors compared to the standard Layer5 branding.

Expected Behavior

The box should not have the unintended white border, and the Layer5 logo should use the correct, consistent brand colors.

Screenshots

Image

Environment:

  • Host OS:
  • Browser:

Contributor Resources and Handbook

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.

Join the Layer5 Community by submitting your community member form.

Activity

  1. riyan-001 commented on Aug 13, 2026

    @riyan-001

    Hi @Maanvi212006 , I’d like to work on this issue.

    I’ve read the CONTRIBUTING.md guidelines and reviewed the issue. I understand that the “Join the Conversation” box has an unintended border and that the Layer5 logo inside it needs to use the correct branding/colors.

    My approach will be to:

    • Locate the component and styling responsible for the “Join the Conversation” section.
    • Identify and remove the unintended border without affecting the surrounding layout.
    • Locate the logo asset/component being used and replace or update it to the appropriate Layer5 branding.
    • Run the project locally and verify the changes across the relevant screen sizes before opening a PR.

    I also have a functional development environment and am ready to work on the issue.

    If it’s available, could you please assign this issue to me?

  2. Maanvi212006 commented on Aug 13, 2026

    @Maanvi212006
    ContributorAuthor

    Go ahead @riyan-001 !

  3. kimberly-WY commented on Aug 13, 2026

    @kimberly-WY

    Confirmed reproducible on Node 20 + macOS. Interestingly it doesn't happen if you set NODE_OPTIONS=--max-old-space-size=512.

  4. riyan-001 commented on Aug 13, 2026

    @riyan-001

    Hey @Maanvi212006 , I am Unable To Run This Website Locally on My System, Can You Please Help ?

  5. Maanvi212006 commented on Aug 13, 2026

    @Maanvi212006
    ContributorAuthor

    Hii @riyan-001 can you message me on slack about what issue you are facing? We can discuss there and help you get started!

  6. Katomoto commented on Aug 13, 2026

    @Katomoto

    The workaround in #142 works short-term but I think the real fix needs to happen at the connection pool level.

  7. rishiraj38 commented on Aug 16, 2026

    @rishiraj38
    Contributor

    @riyan-001 Any updates?

  8. riyan-001 commented on Aug 16, 2026

    @riyan-001

    @rishiraj38 I am Unable To Make The Website Live on My Localhost , Since I am Using WSL , Ubuntu The WSL Connection With VS Code is Disconnecting Automatically

  9. khushal-winner commented on Aug 16, 2026

    @khushal-winner
    Contributor

    Can I get to work on this? @rishiraj38

  10. Harshitera1 commented on Aug 16, 2026

    @Harshitera1

    Hi @khushal-winner, I'm participating in the LFX Meshery AXI mentorship and I'm interested in contributing to #7958 as my first contribution. I saw this issue shared with the newcomers and have started looking into the relevant code. Are you already actively working on it, or would you be open to collaborating on it?

  11. khushal-winner commented on Aug 16, 2026

    @khushal-winner
    Contributor

    Hi @khushal-winner, I'm participating in the LFX Meshery AXI mentorship and I'm interested in contributing to #7958 as my first contribution. I saw this issue shared with the newcomers and have started looking into the relevant code. Are you already actively working on it, or would you be open to collaborating on it?

    thnx, im working on it

  12. added 4 commits that reference this issue on Aug 20, 2026
    9b0c909
    c185606
    231bc95
    265e603
  13. MAYANKSHARMA01010 commented on Aug 25, 2026

    @MAYANKSHARMA01010
    Contributor

    @Maanvi212006 if this issue is still open and no one is working on this so can you assign me this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions