layer5io / layer5io/layer5

[Profile-card] Refactor component to remove hardcoded Meshmate names

Open
#7,885 1 comment 0 reactions 1 assignee View on GitHub

@debkrm is already working on this.

Since Jul 26, 2026.

framework/gatsby help wanted kind/bug
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:

Image

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.