This glossary standardizes common names used throughout the preceding chapters and explains concepts found in English code, logs, and platform dashboards. Chinese terminology follows the conventions here. Filenames, types, configuration fields, commands, and protocol identifiers retain their source spelling.
Definitions apply to the current template and documentation context. Listing a technology or recovery mechanism does not mean the project implements it. For exact fields and defaults, see the Reference. For specific problems, see Troubleshooting.
- When introducing an unfamiliar concept in Chinese, you can give the Chinese term followed by the English name in parentheses. Use the same term afterward.
- Keep names such as Cloudflare, Stripe, OAuth, Webhook, API, URL, JSON, and SQL in English rather than forcing a literal translation.
- Use backticks for identifiers, paths, commands, and literal values, such as
DB, SAAS_SECRET, and payment_succeeded.
- Prefer commas and periods in Chinese sentences. Use semicolons for parallel clauses whose structure requires that separation, not as the default ending for list items or ordinary sentences.
- Specify the context when an English word has different meanings in different domains. For example, both a database transaction and a payment transaction use
transaction.
- “Template defaults” are values in the template source files. “Initialized configuration” may already have been rewritten by the CLI. “Effective configuration” also depends on the runtime environment and deployed version.
- A claim of “support” requires an actual implementation and an entry point that invokes it. A type, error code, or example in a comment does not mean the corresponding feature is available.
- Describe behavior with actions such as “read,” “write,” “send,” “match,” “grant,” and “revoke.” Avoid saying only “processing completed” without specifying which step completed.
| English / code | Chinese term | Meaning and usage |
|---|
| Saavo | Saavo | Product name. Keep it unchanged |
| Saavo CLI | Saavo 命令行工具 | Tool for signing in, selecting templates, and creating projects, among other tasks. It is not the application runtime |
| template | 模板 | Base source code and configuration used to create a project |
| project / application | 项目 / 应用 | “Project” emphasizes source code and development. “Application” emphasizes the running product |
| initialization | 初始化 | Preparing the initial state of a project or resource. Specify whether it is local or remote |
| template version | 模板版本 | The source version of the template when obtained. Record it separately from the application version |
| application version | 应用版本 | Your own product's version. It cannot establish which template source was used |
| dependency | 依赖 | A third-party package or module installed and used by the project |
| lockfile | 依赖锁文件 | Records resolved dependency versions, for example package-lock.json |
| build | 构建 | Converts source code into build output. It is neither deployment nor database migration |
| type checking | 类型检查 | TypeScript static checking, distinct from a Vite build |
| lint | 代码规范检查 | Checks configured code rules. It does not replace tests of business behavior |
| test | 测试 | Uses inputs, operations, and assertions to verify expected behavior |
| branch | 分支 | A Git reference used to organize independent development work |
| commit | 提交 | A code snapshot in Git, or the action of creating one |
| tag | 标签 | Marks a Git state. It does not mean that state has been deployed |
| diff | 差异 | Changes between two code or configuration states |
| merge conflict | 合并冲突 | Changes on two sides cannot be merged automatically and require understanding before resolution |
| source archive | 源码包 | An archive of a specific source state. It excludes runtime data and Secrets |
| changelog / release notes | 变更记录 / 更新说明 | Internal records document implementation details. Public notes describe changes for users |
| English / code | Chinese term | Meaning and usage |
|---|
| configuration / config | 配置 | Application settings and rules. Distinguish static configuration from runtime variables |
| source of truth | 权威来源 / 唯一依据 | The authoritative definition for a piece of data or a rule |
| schema | Schema / 数据结构 | Chinese documentation commonly retains “Schema” for configuration and input validation, and uses table or data structure terminology for databases |
| domain | 业务领域 | A business domain, distinct from a website's domain name |
| service | 服务层 / Service | Organizes business rules and workflows. Keep specific code names unchanged |
| repository | 仓储层 / Repository | Calls the database access layer and converts stored values into business values. This is not a Git repository |
| DB access / DAO | 数据库访问层 | Handles SQL, raw rows, and database operations. DB on its own may also refer to a binding |
| UI | 界面 / UI | Use the Chinese term for interface in user-facing text. UI can remain in discussions of architecture layers |
| DTO | 数据传输对象（DTO） | A request or response structure at an API boundary, distinct from a raw database row |
| contract | 约定 / 契约 | Rules both sides of a call must follow, such as interface or data contracts |
| route | 路由 | The mapping between a request path, method, and handling entry point |
| endpoint | 接口 / Endpoint | An entry point for external calls. Object names in platform dashboards can remain in English |
| handler | 处理函数 | A function that handles requests, messages, events, or commands |
| middleware | 中间件 | Shared logic executed during request handling |
| guard | 访问守卫（Guard） | Checks access conditions. Return values and redirects depend on the call site |
| provider | 服务商 / Provider | An external service provider in a business context, or an adapter implementing a capability in code |
| runtime | 运行时 | The execution environment or entry-point context, such as fetch, queue, or scheduled |
| context | 上下文 | Environment, language, logging, and other information needed for the current execution, such as Ctx or WorkerCtx |
| serialization | 序列化 | Converts data into a form that can be stored or transmitted. It is not encryption |
| validation | 校验 | Checks input formats, types, or constraints. Do not equate it broadly with user authentication |
| English / code | Chinese term | Meaning and usage |
|---|
| Cloudflare Workers | Cloudflare Workers | Platform name. An individual deployed application can be called a Worker. Do not translate it as a worker thread |
| Binding | 资源绑定 / Binding | Configuration that connects a Worker to a resource, with names such as MAIN_KV |
| resource name / resource ID | 资源名称 / 资源 ID | A platform resource's name and identifier, distinct from its binding name in code |
| environment variable | 环境变量 | Configuration supplied through a runtime or build environment. Preserve variable names from the source |
| Secret | Secret / 敏感配置 | A way to store sensitive variables in a Worker. Values may be keys, tokens, or passwords |
SAAS_SECRET | 应用主密钥 | The project's long-term key for operations such as encryption and signing. It is not a version number |
| build-time variable | 构建时变量 | A value read during the build and potentially written into the output. Changes usually require a rebuild |
| runtime variable | 运行时变量 | A value read during application execution. Check the actual Worker's configuration |
| D1 | D1 数据库 | The template accesses two databases through DB and ANALYTICS_DB |
DB | 业务库 Binding | Stores business data such as accounts, payments, and permissions |
ANALYTICS_DB | 统计库 Binding | Stores first-party analytics data |
| KV | KV 存储 | Key-value storage used by the template for content, logs, ticket bodies, and more. It is not just a cache |
| R2 | R2 对象存储 | R2 is the service name. A bucket is an individual storage container |
| bucket | 存储桶 | A container in object storage, such as the bucket referenced by MAIN_R2 |
| object key | 对象 Key / 对象标识 | An object's name within a bucket, not an encryption key |
| Durable Object / DO | Durable Object / DO | A Cloudflare component providing persistent state and coordination. Keep the name unchanged |
| local environment | 本地环境 | Runs on your machine. Resource state is managed separately from remote environments |
| local preview | 本地预览 | Viewing built output locally. It does not imply that a separate test Worker has been configured |
| staging environment | 预发布环境 | An isolated environment for validating behavior similar to production. The template does not automatically provide a complete one |
| production environment | 生产环境 | The environment that serves users |
| Origin | 源 / Origin | A source defined by scheme, host, and port. It excludes the URL path |
| hostname | 主机名 | For example, app.example.com. It excludes the scheme and path |
| custom domain | 自定义域名 | A domain you own that is bound to the application |
| English / code | Chinese term | Meaning and usage |
|---|
| database | 数据库 | Specify whether it is the business, analytics, local, or remote database |
| baseline / initial schema | 初始表结构 / 数据库基线 | In these docs, a baseline is the starting point for initialization, not a backup or incremental migration |
| initialization script | 初始化脚本 | Prepares the initial schema. The template's *-init.sql files include table deletion operations |
| migration | 数据库迁移 | A versioned change to existing structures or data, not just copying data |
| seed data | 初始化数据 | Base or sample data written into a new environment. This term does not imply that the template provides a general seed command |
| record / row | 记录 / 数据行 | “Record” is common in business descriptions, while “row” is common in SQL contexts |
| raw row | 原始数据行 | Data returned directly by the database before conversion to business types |
| transaction | 数据库事务 | A transaction boundary for database operations, distinct from a payment transaction |
| primary key | 主键 | A key that identifies records in a table |
| foreign key | 外键 | Constrains references between records |
| unique constraint | 唯一约束 | Prevents duplicate combinations of specified field values |
| index | 索引 | Specify whether the context is a database index or a search index |
| backfill | 数据补写 | Adds values required by new rules to historical records |
| soft delete | 软删除 | Retains a record and marks it deleted. Restoration depends on the business implementation |
| purge | 彻底清除 / 物理删除 | Physically removes records with no ordinary undo operation. Recovery depends on backups or similar measures |
| revoke | 撤销 | Invalidates authorization, roles, entitlements, or tokens. It does not mean deleting historical records |
| expire / expiration | 过期 / 到期 | The end of a validity period. It does not mean records have been physically removed |
| retention | 数据保留策略 / 保留期 | A retention period is a duration. A retention policy also includes cleanup scope and execution rules |
| Unix timestamp | Unix 时间戳 | Specify seconds or milliseconds. Most persisted timestamps in the template use milliseconds |
| UTC | 协调世界时（UTC） | A time standard. Do not treat it as the visitor's local time zone |
| English / code | Chinese term | Meaning and usage |
|---|
| authentication | 身份认证 / 用户认证 | Establishes a visitor's identity. Chinese prose can use the shortened term for authentication |
| verification | 验证 | Confirms a fact or submitted value, such as email ownership or a verification code |
| authorization | 授权 / 权限控制 | Use the Chinese term for authorization in OAuth contexts, and access permission control when discussing business access decisions |
| account | 用户账号 | A user's identity, distinct from an individual session |
| session | 会话 | Distinguish sign-in, verification, and OAuth sessions by purpose |
| Cookie | Cookie | Data stored by a browser and sent according to rules. It is not the server-side session itself |
| sign up | 注册 | The account creation process |
| sign in / log in | 登录 | Both English expressions use the same Chinese term |
| sign out / log out | 退出登录 | Do not confuse this with deleting an account |
| account deletion | 注销账号 | Ends use of an account and handles its data according to business rules. It does not mean ending the current session |
| password reset | 重置密码 | Usually a recovery process when the original password cannot be used, distinct from changing a password |
| email verification | 邮箱验证 | Confirms email ownership. Distinguish verification by this site from a third-party provider's assertion |
| two-factor authentication / 2FA | 双重验证（2FA） | Uses a second authentication factor. It is not simply entering a password twice |
| TOTP | 基于时间的一次性密码（TOTP） | A dynamic code generated by an authenticator based on time |
| recovery code | 恢复码 | A backup verification method for 2FA, distinct from an email verification code |
| step-up authentication | 敏感操作二次验证 | Reconfirms identity before a specific operation. It does not necessarily use a new authentication factor |
| rate limit / throttling | 限流 / 请求节流 | Limits the frequency of operations. It does not mean permanently disabling an account |
| Turnstile | Cloudflare Turnstile | An anti-automation verification service, not user authentication or role-based authorization |
| OAuth 2.0 | OAuth 2.0 | An authorization protocol. Preserve the space in its name |
| OAuth Client | OAuth 客户端 | An application that initiates authorization and uses tokens, distinct from the signed-in user |
| authorization server | 授权服务器 | The party that handles authorization and issues tokens |
| Redirect URI | 回调地址 / 重定向 URI | The address used to return to the client in OAuth. Verify actual values against the protocol and configuration |
| authorization code | 授权码 | A code exchanged for tokens in an authorization flow, not an email verification code |
| Access Token | 访问令牌 | A token used to access protected resources |
| Refresh Token | 刷新令牌 | Used to obtain new tokens, not to download project source code again |
| Client Secret | 客户端 Secret | A client credential, distinct from a user password or application master key |
| PKCE | PKCE | A verification mechanism linking an authorization request to a token exchange request. Preserve parameter names |
| Scope | 授权范围（Scope） | An OAuth token's access scope, also called 作用域 in Chinese. It is not a user role |
| consent | 授权确认 / 同意 | Use authorization consent for OAuth pages and consent for cookie preferences |
| English / code | Chinese term | Meaning and usage |
|---|
| access control | 访问控制 | The overall access rules for pages, APIs, and business operations |
| Subject | 授权主体（Subject） | The recipient of role and entitlement grants. Specific types follow the project's definitions |
| role | 角色 | A set of static capability definitions associated with an identity or responsibility, such as admin |
| capability | 能力 | A basic authorization unit included in roles and entitlements. It is not limited to static permissions |
| static capability | 静态能力 | Corresponds to CapabilityType.Static and is provided by role configuration |
| boolean capability | 布尔能力 | Corresponds to CapabilityType.Boolean and expresses whether a feature is available |
| numeric capability | 数值能力 | Corresponds to CapabilityType.Numeric and expresses measurable resources or quotas |
| entitlement | 权益 | Product access or resource rules granted to a subject. It can include dynamic capabilities |
| grant | 授予 | Adds a role or entitlement to a subject while preserving its source relationship |
| grant source | 授予来源 | Identifies the purchase, subscription, or system operation that provided access |
| quota | 额度 / 配额 | An available resource quantity or limit. The business defines its exact meaning |
| credits | 积分 | Consumable numeric resources defined by a product. They do not automatically represent a monetary balance |
| entitlement cycle | 权益周期 | The processing schedule for recurring entitlements. Describe it separately from the payment billing cycle |
For example, a role can provide a static capability to manage users. A download entitlement can provide a boolean capability that determines whether downloads are allowed, as well as a numeric capability for the download count. A role or entitlement name is not the result of a capability check, and purchasing a plan does not automatically grant every paid feature.
| English / code | Chinese term | Meaning and usage |
|---|
| product | 产品 | The application's own product configuration. Describe it separately from a Stripe Product object |
| Plan | 套餐 | A purchase option under a product. Use the designated Chinese term consistently rather than alternating with terms for a plan, proposal, or subscription tier |
| Stripe Product | Stripe Product | A product object in Stripe |
| Stripe Price / Price ID | Stripe Price / Price ID | Stripe's price object and identifier, with values such as price_... |
| connection ID | 支付连接 ID | A stable identifier the project uses for a payment connection, such as STRIPE_CONNECTION_ID |
| billing | 计费 | Describes charging methods and cycles. Do not label the entire module as invoices |
| subscription | 订阅 | A recurring billing relationship, distinct from an individual charge transaction |
| one-time purchase | 一次性购买 | A single payment. It does not automatically imply permanent entitlements or lifetime service |
| Checkout | Checkout / 收银台 | The payment checkout flow or page |
| Checkout Session | Checkout 会话 | An object representing one checkout flow, not a user sign-in session |
| payment customer | 支付客户 | A customer association on the payment provider's side, distinct from an application user record |
| transaction | 交易 | A business transaction in a payment context, distinct from a database transaction |
| line item | 明细项 | One product or charge entry in a transaction, subscription, or similar object |
| Billing Portal | 账单门户 | An entry point for users to manage payment and subscription information |
| Invoice | 账单 / Stripe Invoice | Retain the object name in technical explanations. Do not assume it means a Chinese tax invoice |
| trial period | 试用期 | Trial time provided according to plan or subscription rules |
| Coupon | 优惠券（Coupon） | A Stripe object that stores discount rules |
| Promotion Code | 促销代码 | A user-entered code associated with a Coupon |
| Coupon Offer | 动态优惠活动 | The template's feature for selecting discounts through links, also called dynamic coupon codes in the relevant chapter |
| refund | 退款 | Distinguish requested, processing, successful, and failed refunds. A refund does not automatically revoke entitlements |
| affiliate | 联盟推广 | A feature through which affiliates earn income from referrals |
| referral | 推荐 / 推广来源 | In affiliate contexts, use referral link or referral source terminology. Do not confuse it with payment callbacks |
| commission | 佣金 | An earnings record from affiliate referrals |
| payout | 佣金支付 / 收益支付 | Pays eligible earnings to an affiliate. It is not a refund to a purchaser |
Display prices, Stripe Prices, purchase transactions, and access entitlements are four different concepts. Displaying an amount on a page does not change what Stripe charges. Even after payment, a success page alone does not prove that entitlements were granted.
| English / code | Chinese term | Meaning and usage |
|---|
| API | API / 接口 | Preserve the actual definitions of paths, methods, and parameters |
| request / response | 请求 / 响应 | Input and output at an HTTP or other explicit call boundary |
| request body / payload | 请求体 / 载荷 | A request body belongs to HTTP. A payload can also be message or event data |
| callback | 回调 | Broadly, calling another entry point after completing a step. Specify whether it is an OAuth or business callback |
| Webhook | Webhook / 服务端回调 | An external service delivers events to the application. It is not the browser returning to a success page |
| signature verification | 签名验证 / 验签 | Checks origin and integrity. It does not decrypt the content |
| raw body | 原始请求体 | Request content that has not been reparsed and serialized. Preserve it for webhook signature verification |
| HTTP status code | HTTP 状态码 | For example, 200, 401, 403, or 500. It is distinct from a business error code |
| result code / error code | 结果码 / 错误码 | Allows programs to determine results. Distinguish the project's numeric codes from third-party string error codes |
APIResponse<T> | API 响应类型约定 | A type provided by the template. Not every actual endpoint returns the same complete structure |
| retryable | 可重试 | Allows another attempt under the relevant conditions. It does not guarantee that the next attempt will succeed |
| non-retryable | 不可重试 | The current failure should not be retried automatically. Input may need correction or side effects may need checking first |
| fallback | 备用值 / 备用处理 | Specify the fallback value or path. Do not confuse it with a version rollback |
| side effect | 副作用 / 外部效果 | An actual effect such as a data write, sent email, or payment. A code rollback may not undo it |
| English / code | Chinese term | Meaning and usage |
|---|
| background job | 后台任务 | Work performed in the background. It does not automatically mean the work has been enqueued |
| Cloudflare Queues / Queue | 队列 | Used to deliver messages. Preserve queue and binding names |
| producer / consumer | 生产者 / 消费者 | The sender of a message and the party that receives and processes it |
| enqueue | 入队 | Places a message in a queue. It does not mean the business operation has completed |
| acknowledgement / ack | 消息确认 | Indicates that this message delivery no longer needs to be retried. It does not necessarily mean the business operation succeeded |
| redelivery | 重新投递 | A queue or provider delivers a message or event again |
| retry | 重试 | Specify whether it means a Command execution retry, an HTTP retry, or Queue redelivery |
| replay | 重放 | Processes a historical event or task again. Check idempotency and effects that have already occurred first |
| idempotency | 幂等性 / 幂等处理 | Repeating the same business operation does not duplicate effects within the defined scope |
| idempotency key | 幂等键 | Identifies the same business operation within the relevant scope, for example idempotencyKey |
| lease | 租约 | The right to process work for a limited time, used to coordinate concurrent execution |
| dead-letter queue / DLQ | 死信队列（DLQ） | A queue that receives failed messages. Do not imply that the current template configures one for every queue |
| Reaction | Reaction | The project's internal system for organizing business events and command execution |
| Event | 业务事件 / Reaction Event | Describes a business fact that has occurred, with type names such as PaymentSucceededEvent |
| Command | 业务命令 / Reaction Command | An execution step produced by an event, with type names such as GrantRoleCommand |
| Event execution | Event 执行记录 | Corresponds to event_execution. Distinguish it from an external provider's Event ID |
| Command execution | Command 执行记录 | Corresponds to command_execution and stores step status and execution information |
| synchronous / sync | 同步 | Processes work directly in the current execution flow |
| asynchronous / async | 异步 | Schedules work separately from the current step. The template's asynchronous Commands are processed through a queue |
| Cron Trigger | Cron 定时触发器 | Determines when a task is triggered. Its expression is called a Cron expression |
| scheduled handler | 定时任务入口 | The Worker entry point that handles scheduled triggers |
| Status | Meaning in this project |
|---|
Webhook processing | The event processing record holds a lease. Check its update time to assess actual progress |
Webhook succeeded | Processing of this event has been recorded as successful. It does not guarantee completion of every subsequent asynchronous effect |
Webhook failed | Processing of this event failed. Use the error records to investigate |
Command pending | Not yet finished. It may be waiting for execution or a retry |
Command succeeded | The command succeeded and its result was saved |
Command failed | The command ended with a business failure |
Command errored | The command ended with an exception |
Event completed | A completion status computed from its Commands |
Event partial_failed | Execution was allowed to continue after failure, all steps have ended, and at least one business failure occurred |
Event status is computed from Command statuses. There is no separately persisted status column in event_execution. This table is not a complete list of all statuses. See Domain events and commands.
The word Event may also refer to a Stripe event or an analytics event. When describing flows across systems, specify “Stripe Event ID,” “Reaction execution ID,” or “analytics event.” Do not use a single “event ID” to refer to identifiers across all systems.
| English / code | Chinese term | Meaning and usage |
|---|
| MDX | MDX | A Markdown file format that supports component content. Follow the project's component conventions |
| Frontmatter | Frontmatter / 文档元数据 | Metadata such as titles and descriptions enclosed by --- at the start of a file |
| content collection | 内容集合 | Structured content generated from source files such as documentation and blog posts |
| search index | 搜索索引 | Output used for search queries, distinct from body content or a database index |
| Slug | 路径标识（Slug） | A path identifier in a content URL. Routing rules determine the actual path |
| analytics | 访问统计 / 统计 | This project's traffic and behavior analytics feature |
| first-party analytics | 第一方访问统计 | Analytics collection and reporting provided by this application itself |
| third-party analytics | 第三方统计服务 | Services such as Google Analytics and Clarity. Distinguish their configuration from first-party analytics |
| tracking event | 统计事件 / 事件采集 | The first Chinese term refers to a record, the second to the collection action. Neither is a business Event |
| page view / PV | 页面浏览 / 页面浏览量 | A page view or its count, not a count of unique visitors |
| visitor / visit / session | 访客 / 访问 / 统计会话 | Distinguish identity from the visit process according to the analytics implementation. These are not sign-in sessions |
| funnel | 转化漏斗 | Tracks completion and conversion across a set of steps |
| Do Not Track / DNT | 请勿跟踪（DNT） | A browser tracking preference signal, not a cookie consent record |
| Cookie consent | Cookie 同意管理 | Manages consent preferences and the conditions for enabling related scripts |
| internationalization / i18n | 国际化 | The structures and mechanisms that allow an application to support multiple languages |
| localization / l10n | 本地化 | Translating content and adapting its presentation for a language or region |
| locale | 语言标识 / Locale | In these docs, often an identifier such as en or zh-Hans. It does not necessarily include a region |
| language code | 语言代码 | Preserve actual configuration values, such as zh-Hant |
| translation key | 文案键 | A path used to find text in the standard language resources |
LocalizedText | 可本地化文案配置 | A configuration object containing key and value, not a plain string |
| translation fallback | 文案备用值 | Content used when a translation is missing. It does not mean translation is complete |
| Newsletter | 邮件订阅 | A subscription to website update emails, not a paid product subscription |
Analytics data helps observe visitor behavior. It cannot replace a payment ledger or audit records. An analytics session count cannot be treated directly as a count of signed-in users either.
| English / code | Chinese term | Meaning and usage |
|---|
| deployment | 部署 | Publishes the application and related runtime configuration to a target environment |
| release | 发布 / 版本发布 | May include code, configuration, data, and public notes. Specify the actual operations |
| upgrade / update | 升级 / 更新 | Specify whether the target is the CLI, template, dependencies, or live application |
| breaking change | 不兼容变更 | A change that prevents existing data, configuration, or usage from continuing to work without changes |
| backward compatibility | 向后兼容 | The new implementation still handles old inputs or states within a defined scope. It does not promise compatibility forever |
| health check | 健康检查 | Checks specified entry points or conditions. It is not full business acceptance testing |
| backup | 备份 | A copy retained for recovery. Specify which resources it includes |
| restore | 恢复 | Reconstructs state from a copy or recovery point. It may affect writes made after that point |
| recovery point | 恢复点 | A specific historical state available for recovery |
| Time Travel | D1 Time Travel | D1's point-in-time recovery mechanism, not an automatic rollback of the entire application |
| rollback | 回滚 / 版本回退 | Specify whether code, configuration, or data is being rolled back. Do not broadly promise to undo everything |
| roll forward | 向前修复 | Repairs the current state through subsequent changes rather than restoring an old version |
| log / audit log | 日志 / 审计日志 | Logs record runtime information. Audit logs track operations that require auditing |
| alert | 告警 | A notification of an abnormal condition requiring attention or action, distinct from an ordinary business notification |
| observability | 可观测性 | The ability to understand system state through logs, metrics, and execution records |
| incident / troubleshooting | 故障 / 故障排查 | An incident is a problem. Troubleshooting is the process of gathering evidence and locating its cause |
Updating the CLI does not automatically update projects already created. deploy:update deploys code from the current directory and does not download a newer template either. Rolling back code does not automatically undo database migrations, completed payment transactions, or sent emails. See Upgrades and maintenance.
Add a term only when it recurs across articles, its translation is easy to confuse, or a misunderstanding could affect configuration or business behavior. Keep definitions concise and link to the relevant chapter for detailed procedures. Do not duplicate a tutorial in the glossary.
Before changing a term, check the source code responsible for the concept and the existing articles. Adding an English alias or clarifying context does not require mechanically replacing every expression. If you change an established Chinese name, also check body text, headings, and links so that the glossary and tutorials use consistent names.