Unwanted white border around "Join the Conversation" (Discuss) card on Learn, Community & FAQ pages
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in src/sections/Discuss-Callout/discuss.style.js around line 70 and inspect the styled-components template scope, especially the button block. Correct the misplaced closing brace so the DiscussWrapper has no white border while the card size, spacing, and logo box remain unchanged, then verify the affected DiscussCallout pages in Chrome.
Written by the indexing model from the issue text.
Description
Description
The "Join the Conversation" Discuss callout card renders with a stray 2px solid white border around its outer container. It shows up on every page that uses the DiscussCallout component.
Root cause: In src/sections/Discuss-Callout/discuss.style.js, an extra closing brace } (~line 70) prematurely closes the styled-components template's root scope. The button { … border: 2px solid; … } block below it is then parsed as a root-level rule, and its border: 2px solid (color resolves to currentColor, i.e. the inherited white text color) leaks onto the outer DiscussWrapper container — producing the white border.
Affected Pages
- https://layer5.io/community
- https://layer5.io/company/faq
- https://layer5.io/learn/learning-paths/mastering-meshery/introduction-to-meshery
- https://layer5.io/learn/learning-paths/mastering-service-meshes-for-developers/introduction-to-service-meshes
- https://layer5.io/learn/learning-paths/mastering-service-meshes-for-developers/advance-concepts-of-service-mesh
- https://layer5.io/learn/learning-paths/mastering-kubernetes-for-engineers/ambassador-edge-stack-api-gateway-with-meshery
- https://layer5.io/learn/learning-paths/mastering-kubernetes-for-engineers/explore-dapr-with-meshery
- https://layer5.io/learn/learning-paths/mastering-kubernetes-for-engineers/scalable-postgres-with-cloudnativepg
- https://layer5.io/learn/learning-paths/mastering-kubernetes-for-engineers/deploying-wordpress-and-mysql-with-persistent-volumes-with-meshery
Expected Behavior
No white border should frame the "Join the Conversation" card. It should sit cleanly on the dark background, with the card size, spacing, and logo box unchanged.
Screenshots
Screenshot from one of the pages
Environment
- Host OS: Windows 11
- Browser: Chrome
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 1.6k
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 34
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from layer5io/layer5
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
layer5io/layer5#8155 · 3 comments ·
Maintainers usually reply within 2 days
-
framework/gatsby help wanted kind/bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
layer5io/layer5#8147 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
useScrollPosition re-attaches its scroll listener on every frame while scrollingPossibly taken @ayushgade06 claimed this today. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
layer5io/layer5#8142 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
[UI]: MeshMate logo disappears to the left on the MeshMates pagePossibly taken @ayanasarkar claimed this 5 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
layer5io/layer5#8123 · 3 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
layer5io/layer5#8075 · 2 comments ·
Maintainers usually reply within 2 days
Similar issues
-
automation models
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs:triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
mastra-ai/mastra#25508 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 72/100
githubnext/gh-aw-cao#15017 ·
Maintainers usually reply within 1 day