[Profile-card] Refactor component to remove hardcoded Meshmate names
@debkrm is already working on this.
Since Jul 26, 2026.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 1.6k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 18
Description
Description
See Profile-card component (src/components/Profile-card/index.js), the code is currently hardcoding specific names to conditionally render the Meshmate icon badge.
Note: I would love to be assigned to this issue so I can submit a PR to refactor it.
Expected Behavior
The part of the code must be dynamic and must not depend on fixed string matching. The code part must rather validate some property that has been passed down through frontmatter in order to determine if it is necessary to render a particular Meshmate badge.
Screenshots
Here is the current hardcoded implementation in the codebase:
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
- 📚 See contributing instructions.
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.
Contributor guide
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.
Assessment
This issue has not been assessed yet.