[Bug]: Fix broken README.md documentation table, dead catalog links, and missing payload-host ESLint ignores
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown, nextjs
- Domain
- documentation, tooling
Research direction
Start with the broken table near README.md lines 40-44 and the /catalog links at lines 28-43, then check MIGRATION.md line 56 against fixtures/app/(helmdeck)/catalog/, which only defines page.tsx. For lint, add the two examples/payload-host paths to the ignores in eslint.config.mjs around line 8, then run pnpm lint with the .next directory present. Done when the table renders, no link points to a missing route, and lint passes; the v0 and resource-engine wording needs a decision on the replacement text first.
Written by the indexing model from the issue text.
Description
Area
Generic core
Priority
P2 - Normal priority
Summary
README.md has a broken Markdown table and links to non-existent /catalog/* sub-routes and v0 floating tags, and eslint.config.mjs omits examples/payload-host/.next/** and examples/payload-host/next-env.d.ts from its ignore list.
Reproduction steps
- View
README.md:40-44where prose inserted between table rows breaks theGetting startedtable row. - Follow the
/catalog/<slug>links inREADME.md:28-43andMIGRATION.md:56(fixtures/app/(helmdeck)/catalog/only defines/catalog/page.tsx). - Build
examples/payload-hostand runpnpm lint(eslint.config.mjs:8does not ignoreexamples/payload-host/.next/**orexamples/payload-host/next-env.d.ts).
Expected behavior
- The documentation table in
README.mdrenders cleanly, all links resolve to live routes or sections onhttps://helmdeck.yesvus.com, and release documentation reflects1.x(v1) and the Payload-backed starter. eslint.config.mjsignoresexamples/payload-host/.next/**andexamples/payload-host/next-env.d.tsalongsidefixtures,examples/independent-host, andtemplate.
Actual behavior
README.md:42splits the documentation Markdown table in half and links to 404/catalog/*sub-routes onhelmdeck-web.vercel.app.README.md:14,30-32,70-76still references the retired pre-1.0 resource engine andv0floating rollout tag.pnpm lintfails ifexamples/payload-host/.nextexists on disk.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 102
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 yesvus/helmdeck
-
CI documentation enhancement good first issue help wanted P2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yesvus/helmdeck#454 · 1 comment ·
Maintainers usually reply within 1 day
-
CI enhancement good first issue help wanted P2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yesvus/helmdeck#449 · 1 comment ·
Maintainers usually reply within 1 day
-
accessibility bug good first issue help wanted P1 Shell Theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yesvus/helmdeck#442 · 1 comment ·
Maintainers usually reply within 1 day
-
Analytics enhancement help wanted P1
Difficulty 4/5 3-5 days Newbie friendliness 25/100
yesvus/helmdeck#461 · 1 comment ·
Maintainers usually reply within 1 day
-
Analytics enhancement help wanted P1
Difficulty 3/5 1-2 days Newbie friendliness 45/100
yesvus/helmdeck#459 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kunchenguid/gh-axi#247 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lidge-jun/opencodex#8101 · 2 comments ·
Maintainers usually reply within 1 day
-
effort:S P3 refactor
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/nocturne#3243 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
JuliusBrussee/caveman#1449 ·
Maintainers usually reply within 1 day