[Pricing] Plan cards reference non-existent "Free" and "Team" tiers

Open Beginner friendly
#8,258 4 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@sameerkrdev is already working on this.

Since Oct 31, 2026.

  • #8278 by @AP24110011695 — open
  • #8283 by @sameerkrdev — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript, react
Domain
frontend

Research direction

Start with src/sections/Pricing/generatePlans.js, especially the byline2 entries on lines 14, 23, 33, and 43. Check how the pricing cards display those descriptions and confirm which tiers Enterprise includes. Done means each line refers to plans shown on the page and Personal’s line has consistent formatting.

Written by the indexing model from the issue text.

Description

framework/gatsby help wanted kind/bug
Description

On https://layer5.io/pricing, the "Everything included in ..., plus..." lines reference plan names that don't appear on the page:

  • Team Designer and Team Operator say "Everything included in Free, plus...", but the tier is displayed as Personal ("Free Forever" is only a badge).
  • Enterprise says "Everything included in Team, plus...", but there is no "Team" plan, only Team Designer and Team Operator, so it's unclear which one Enterprise builds on.

Source: src/sections/Pricing/generatePlans.js (byline2 on lines 14, 23, 33, 43)

Expected Behavior

Each line names a plan that is actually shown, e.g.:

  • Team Designer / Team Operator: "← Everything included in Personal, plus..."
  • Enterprise: "← Everything included in Team Designer and Team Operator, plus..." (please confirm which tiers Enterprise includes)

Minor: Personal's line has a leading space and no ←, unlike the others.

Screenshots
Image
Environment:
  • Host OS: Windows 11
  • Browser: Brave

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.

Dominant language
JavaScript
Stars
1.2k
Forks
1.7k
Avg merge
2d 22h
Merged PRs (30d)
69

Getting set up

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.

More from layer5io/layer5

All issues in layer5io/layer5

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.