What this surface does

This is the create wizard for a new wheel.

Operators use it to define all required wheel data in five steps:

1. Wheel Name
2. Wheel Settings
3. Wheel UI
4. Segments
5. Visibility

Each step also has its own Complete Step action, and each step can expose Save Draft while the wheel still exists only as a local browser draft.

How the create flow really behaves

• Save Draft is a per-step local-draft helper until the first backend draft row exists.
• The first successful Complete Step can bootstrap a real backend draft row and redirect the operator from /create to /wheel-of-fortune/:id.
• Step headers are clickable, but the operator can only open step 0 immediately or a later step when the previous step is already completed.
• The final submit path publishes the wheel only after all required steps are completed and FE validation passes for the required steps.
• Segment setup uses the active bonus catalog as one of its reference inputs, but choosing a segment bonus does not edit the underlying bonus definition.
• The first step includes identity and cooldown: wheel name, cooldown period, title, subtitle, claim button text, and claim title.
• Settings cover player-facing links and motion: wheel URL, wheel MKT tag, claim button URL, wheel speed, wheel turns, and guest access.
• UI configuration covers text placement, segment text styling, modal background, and four asset slots: wheel background, spin button, pointer arrow, and wheel frame.
• Segment configuration supports localized text, chance percent, optional segment image, and a linked bonus per segment.
• Visibility controls include include-tags, exclude-tags, and the active or inactive status switch.
• Translate fills missing localized values from EN only.
• Force Translate overwrites existing target-language values for the supported translated fields.
• The right-side Live Preview is not a persistence surface. It mirrors current FE state, includes a preview-language switcher and completion progress, and helps operators inspect wheel links, claim links, preview chips, and segment UI before publish.

Common caveats

• Backend publish validation requires a wheel name, title translations, claim button translations, claim title translations, and between 10 and 16 segments with text.
• FE step validation only hard-gates Wheel Name and Segments; the intermediate settings, UI, and visibility steps can still be marked complete without extra FE validation errors.
• Full publish still requires all steps to be completed, so operators should not treat a green Complete Step on step 1, 2, or 4 as proof that all downstream data is ready.
• Save Draft stops writing local storage after the first backend draft exists; from that point the operator must use Complete Step to persist changes.
• The first backend draft is stored unpublished. Backend create stores it inactive unless the visibility step has already been completed in the payload.
• Translate and Force Translate only work when at least one EN source text exists across title, subtitle, claim button text, claim title, or segment text.
• Preview links are generated from current form values and casino origin settings. They are helpful for inspection, but they do not save or publish the wheel.
• Preview spin is FE-only. It uses segment chance weights for inspection and does not create spin history or award a real prize.
• Segment images and wheel UI assets can come from either direct URLs or asset-library selections depending on the current source-type toggle.