Skip to content

feat(i18n): align community plugin names and release documentation - #4

Merged
mayneyao merged 1 commit into
mainfrom
codex/community-plugin-i18n
Oct 26, 2026
Merged

mayneyao merged 1 commit into
mainfrom
codex/community-plugin-i18n

Conversation

@mayneyao

Copy link
Copy Markdown
Contributor

Use the registry's language snapshots for catalog and detail names/descriptions. Read format 3 README documents from checksum-verified release archives, select one complete document with locale fallback, and keep caches separate by package hash and page language. Legacy plugins continue to read documentation at their immutable release tag.

Align contribution and permission summaries with current plugin Views, hooks and background capabilities, and link the public template and getting-started guide. Preserve the existing language menu and screenshot carousel. Keep pending Worker I/O request-local and retry failed archive lookups rather than caching blank documentation.

Validation: 27 tests, Astro typecheck and build pass. Deployed an isolated Cloudflare preview and checked 16 English/Chinese name, description and full rendered README outputs against the eight exact published archives. Six additional legacy detail pages retain their README. Browser visual verification was not available because the browser permission gate declined the preview origin; acceptance here uses server-rendered HTML, not screenshots. The original dirty checkout is untouched.

@mayneyao
mayneyao merged commit 7fb8472 into main Oct 26, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant