Repository navigation
feat(i18n): align community plugin names and release documentation - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.