Repository navigation
docs: rename the Enjeu glossary term to Challenge - #111
Merged
Merged
Conversation
CONTEXT.md now defines Challenge, with Enjeu as the French UI word. ADR 0002 gains a dated note on the rename (posts#110); its decision is unchanged.
Contributor
|
🔍 Preview: https://website-mtwaweig7-ocobo-22231b32.vercel.app Built from website |
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.
Part of #110.
PR #109 merged before this commit arrived, so
mainhas code that says challenge while the glossary and ADR still said Enjeu.What
CONTEXT.md: the glossary entry becomes Challenge, with "Enjeu" noted as the French UI word. "challenge" leaves its Avoid list, "enjeu (in code)" joins it. The Content line and the relationship lines say challenge.docs/adr/0002-enjeu-pages-as-content.md: a dated note at the end records the rename: content typechallenge, files inchallenges/<lang>/, schemascripts/schemas/challenge.schema.js, Team member fieldchallengetyped byCHALLENGE_KEYS. The decision text and the file name are unchanged.Checked against
mainafter #108: the Team member field ischallengeand its values come fromCHALLENGE_KEYS.Still in #110
new-content,translate-content,publish-content).Tests
pnpm testandpnpm validategreen. Docs only.