Guides
Start from the question you need answered, then continue into the right guide, path, or setup page.
Best for how-to, readiness, and timing questions.
Start with a clear answer before you jump into setup details.
Continue into docs, path details, or broader workflows after the first decision is clear.
Start from the question you need answered, then continue into the next step.
Guide · Lanhu to Unity Prefab
Yes. The safer path is to confirm that Lanhu to Unity is currently supported, prepare access and file quality, and validate one real screen before expanding scope.
Lanhu to Unity is currently a released path, so this question should be handled as preparation -> setup -> contained validation.
Guide · Figma to Unity
Yes, but it is better treated as a Beta validation path. Confirm roadmap status first, then prepare setup and test one real module before broader rollout.
Figma to Unity is currently a Beta path. It is best validated in one real project slice before broader rollout decisions.
Guide · Design to Unity Handoff
The safer order is to identify the current path first, then separate maturity, setup, and trial scope before a larger rollout decision.
A design-to-Unity handoff question should be split into path choice, maturity, setup work, and project-specific blockers instead of flattening everything into docs.
Guide · Unity UI Delivery Automation
Automation should not begin with a tool decision alone. The safer order is to confirm that repeated delivery cost is real, identify the current path maturity, and validate one contained workflow before broader rollout.
Automation becomes worth testing when repeated rebuild cost, coordination cost, or regression overhead are already visible in the team workflow.