Repository navigation
fix(docs): repair broken links in English docs - #518
Conversation
Several English docs link to files that do not exist, and since the translated docs are generated from them, every locale inherits the 404s. - fastify guide: replace Google search wrapped URLs with direct links - packages/*/index.md -> packages/*/exports.md - dictionary/*_content.md, plural.md -> actual file names - fill.md -> autoFill.md, readme.md -> README.md - react-intlayer exports: docs/dictionary/translation.md -> docs/docs/en/dictionary/translation.md - intlayer_with_nextjs_no_locale_path.md (removed) -> Next.js 16 guide, which covers the setup without locale path Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Hey @theluckystrike thanks! looks good to me, merging |
|
Thanks, @aymericzip, for merging #518. The content type links in content_file.md now land on real pages like nesting.md and plurial.md instead of a 404, and every locale should pick that up on the next translation run. My other work is at https://github.com/theluckystrike. Even a small one-time sponsorship through https://github.com/sponsors/theluckystrike would tell me the time on Intlayer's docs was valued, and I'd gladly keep sending fixes here. No pressure at all. Thank you, |
Several English docs link to files that are not in the repo, so the links return 404 on GitHub. The translated docs are generated from the English ones, so each broken link also shows up in every locale.
Every old target below returns 404 at
blob/maintoday and every new target returns 200.git cat-file -e origin/main:<path>gives the same result.intlayer_with_fastify.mdwraps the three package links in Google search URLs (https://www.google.com/search?q=%5B...). They now point straight topackages/{react,next,vite}-intlayer/exports.md.packages/*/index.mddoes not exist forreact-intlayer,next-intlayer,vite-intlayer,intlayerorintlayer-cli. Each package folder hasexports.md. Fixed in the adonisjs, elysia, express, fastify and hono guides,how_works_intlayer.mdandreleases/v7.md.dictionary/content_file.mdlinks totranslation_content.md,condition_content.md,enumeration_content.md,insertion_content.md,markdown_content.md,nested_content.md,file_content.mdandplural.md. The files aretranslation.md,condition.md,enumeration.md,insertion.md,markdown.md,nesting.md,file.mdandplurial.md.content_file.mdlinks tofill.md. The page isautoFill.md.intlayer_with_nextjs_14.md,intlayer_with_nextjs_15.mdandintlayer_with_nextjs_page_router.mdlink tointlayer_with_nextjs_no_locale_path.md, which was removed in b13cf18 when the Next.js docs were regrouped. They now link tointlayer_with_nextjs_16.md, which says at line 99 that both setups, with and without locale path routing, are covered there.packages/react-intlayer/exports.mdlinksttodocs/dictionary/translation.md, which is missing thedocs/enpart. The table columns were realigned by Prettier.readme.mdlinks to/blob/main/readme.md. GitHub paths are case sensitive and the file isREADME.md.I bumped
updatedAtin each changed doc, asdocs/CLAUDE.mdasks. Only the English sources are edited. The locales can pick the fixes up through the usual translation run.Checks run on the 13 changed files:
markdownFormattingandmetadataValidityfromdocs/toolspass (12 of 12 files checked,readme.mdis excluded by the tool's own pattern) andprettier --checkpasses with the repo config. After the change, no link in these files points to a path missing frommain.I wrote this with AI assistance and reviewed every changed line by hand.