Repository navigation
Give the Turkish standards the layer that tells you what to read next - #9
Merged
Merged
Conversation
STANDARDS.md gained section 13, Layered conventions, when project-type/ and lang/ were introduced: it is the section that says a repository reads STANDARDS, then its project type, then its language, then any overlay it adopts. The Turkish file never got it and went straight from 12 to the repository roster, so a Turkish reader was never told the other layers exist - and TOOL.md, LIBRARY.md and APPLICATION.md are exactly where the concrete rules live. Section numbering now matches the English file section for section, and the roster moves to 14 as it is there.
There was a problem hiding this comment.
Pull request overview
Adds the missing “Layered conventions” section to STANDARDS.tr.md so Turkish documentation matches the English STANDARDS.md structure and points readers to the concrete rules in project-type/, lang/, and overlay/.
Changes:
- Added Turkish §13 “Katmanlı sözleşmeler” describing the layered standards model and recommended reading order.
- Renumbered the repository roster from §13 to §14 to align with
STANDARDS.md.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| | Katman | Yol | Kapsam | | ||
| |---|---|---| | ||
| | Proje tipi | [`project-type/`](project-type/) | Library, tool ya da application; dil farketmez | |
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.
STANDARDS.md§13 Layered conventions was added whenproject-type/andlang/came online.STANDARDS.tr.mdnever received it: it jumps from §12 to the repository roster, so a Turkish reader is never told thatproject-type/TOOL.md,LIBRARY.md,APPLICATION.mdandoverlay/exist, or in what order to read them — which is where the concrete rules actually live.This adds §13 in Turkish and renumbers the roster to §14, so the two files now match section for section (0–14, verified heading by heading).
Not a breaking change: no rule changes, one section is translated and one is renumbered. The only cross-reference to the roster in the tree is
lang/python/README.md, which points at the EnglishSTANDARDS.md#14-active-repositoriesand is unaffected.