Language & Project Naming
Tone
Use concise, equal, and direct language. State facts and next steps; avoid administrative command tone and over-friendly marketing phrasing.
- Recommended: "Your session expired. Please sign in again."
- Avoid: "Dear user, we are terribly sorry to inform you that there may be an issue with your session."
- Recommended: "This can't be undone."
- Avoid: "Are you sure you want to perform this operation?"
Terminology
Concept names must stay unique within a product. First-time abbreviations need their meaning explained. Developer jargon is only acceptable when the audience can understand it. Brand names keep their original spelling; file names, commands, and code identifiers use code formatting.
Project Naming
Repository names should be readable English or a course abbreviation plus the project name, avoiding meaningless numbers, full-width characters, or long names. The README first screen must state the project name, a one-line description, current maintenance status, and scope of use.
Organization-level names follow:
- Chinese: 重庆理工大学开源计划
- English: CQUT Open Project
- Abbreviation: CQUT-OSP
- GitHub: CQUT-OpenProject
Actions & Status Copy
Action buttons use a "verb + object" format, such as "Create repository", "Copy token", "Re-sync"; status indicators state concrete results, such as "Saved", "Sync failed", "Pending review". Avoid one word serving simultaneously as a page name, an object name, and an action name.
Dates & Numbers
For Chinese users prefer 2026-07-11 or 2026 年 7 月 11 日. For deadlines and cross-region operations, state Asia/Shanghai or the UTC offset. Units follow interface context consistently, e.g. 16 px, 24 MB.