Blender Mode, Node, and Library Workflow Guide

Outliner - Outliner should be read through Blender / Maya, not as a loose label in a translation sheet. Outliner (大纲视图 / アウトライナー) is useful in a brief only when it points to an inspectable source state. Put the term beside the file, target output, and owner who can verify it. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Attribute Editor - When 属性编辑器 or 属性エディタ appears in a review note, the English term still needs the file state beside it. Attribute Editor (属性编辑器 / 属性エディタ) should include procedural cause and cached result. Name the node path, attribute or solver setting, frame range, and exported artifact before calling the effect reproducible. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Preferences - Preferences becomes useful only when the reviewer can point to the part of export, render, linked scene, or geometry-node driven asset that it changes. Preferences (首选项 / プリファレンス) is a dependency risk. Check whether the file is copied, linked, overridden, or resolved through a versioned reference, then save the path or layer that the receiving machine will load. The translation is therefore tied to evidence, not to an isolated glossary row.

Node Tree - For a vendor-facing brief, Node Tree is the anchor term and the localized labels explain the same inspected state. Node Tree (节点树 / ノードツリー) should be reviewed at the graph level. A screenshot of the final viewport is secondary; the important evidence is the node group, exposed parameters, and the output that proves the graph behaves as intended. That keeps the article searchable while still giving Blender generalist or technical artist something concrete to approve.

Graph Editor - The practical question around Graph Editor is what evidence would make another reviewer agree with the same decision. Graph Editor (图表编辑器 / グラフエディタ) should be reviewed at the graph level. A screenshot of the final viewport is secondary; the important evidence is the node group, exposed parameters, and the output that proves the graph behaves as intended. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

Shelf - Treat Shelf as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Shelf (工具架 / シェルフ) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Command Panel - Command Panel should be read through 3ds Max, not as a loose label in a translation sheet. Command Panel (命令面板 / コマンドパネル) should be tied to the exact part of export, render, linked scene, or geometry-node driven asset that it changes. Record the setting, reviewer, and proof artifact so the term is not reduced to a loose label. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Hotkey / Shortcut - When 快捷键 or ショートカットキー appears in a review note, the English term still needs the file state beside it. Hotkey / Shortcut (快捷键 / ショートカットキー) belongs to editorial review. Keep shot ID, frame range, timing note, and the current cut reference together so the animation or previs note does not drift from the approved sequence. The translation is therefore tied to evidence, not to an isolated glossary row.