[Pricing] Plan cards reference non-existent "Free" and "Team" tiers
Maintainers usually reply within 1 day
@sameerkrdev is already working on this.
Since Oct 31, 2026.
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
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
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.
- 📚 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.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 1.7k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 69
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from layer5io/layer5
-
framework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Fix inconsistent visibility and clipping of Slick carousel navigation arrows on mobilePossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8275 · 4 comments ·
Maintainers usually reply within 1 day
-
Fix logo/graphic fitting within its container on mobile viewportsPossibly taken @AP24110011695 claimed this 14 days ago. Openframework/gatsby good first issue help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
layer5io/layer5#8272 · 4 comments ·
Maintainers usually reply within 1 day
-
[UI] Typography token Heading 1 overflows on mobile viewportsPossibly taken @tanav29 claimed this 4 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
layer5io/layer5#8267 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
[UI] Theme Provider Props table overflows on mobile viewportsPossibly taken @SajanBisht claimed this 15 days ago. Openframework/gatsby help wanted kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
layer5io/layer5#8264 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
good first issue help wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dlq/synthpopcan#58 ·
Maintainers usually reply within 2 days
-
cli: `execCargoMetadata` decodes stdout per chunk, corrupting non-ASCII paths across pipe boundariesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
osmlab/name-suggestion-index#13104 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fjaeckel/seriesoftubes#376 ·
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day