Add bilingual FAQ pages - #35
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
1 participant
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.
What changed
/faqand/zh/faqsite routes with 16 representative answers organized around understanding, trying, building, and adopting SweetGold/sweetgoldGitHub Pages base pathWhy
Visitors need a clear path from the launch page to common project, evidence, engineering, adoption, and governance questions without turning the homepage into a long reference manual.
User impact
The public site will provide concise FAQ entry points in both languages, while linking to the complete repository reference for deeper operational questions.
Validation
npm test— 4 passing rendered HTML testsnpm run lintnpm run build:pages/sweetgold/faq,/sweetgold/zh/faq, language switches, and repository-base linksgit diff --check