#Standards

A standard is a norm or a criterion that applies to every team: how we review code, how we write tests, what conventions our GraphQL follows.

#Standards and guides

A standard says what is correct. A guide says how it is done. When in doubt, ask whether your page can be violated: a code review criterion can be, a CDN setup how-to cannot.

#How it is structured

The topic owns the top level; discipline appears beneath it, and only when the content genuinely diverges. A GraphQL standard that applies to backend and frontend lives at /standards/api/graphql/ once, and splits into backend and frontend the day they stop matching. The topic URL does not change.

#Sections

• Branching model — the Git flow for the repositories
• Branches and commits — branch names and commit messages
• Input design for queries and mutations — the single input object pattern in GraphQL
• Technical documentation standards — how we document technical changes
• Definition of Done — the requirements of every delivery
• Code review criteria

#Who approves

A standard binds every team, so every affected team approves it through the MR. The steps are in how to contribute to the portal.