Publishing & localization

Create a surface from its module’s template library. The copy becomes an independent draft; later template archival does not affect it. Design each screen independently and connect button routes. Preview uses the SDK renderer while simulating business actions.

• Content languages are separate from console language, with at most 20 per document. Layout, CSS, actions and capability bindings are shared; text, images and HTML can be localized.
• Edit centrally or import CSV in content localization. Review, apply to the draft and save. Referenced pages retain their own published snapshot.
• All enabled locales need complete required text, buttons and HTML before publication. Interactive preview and delivery select one complete locale instead of mixing per-field fallback languages.

Save changes the draft only. After structure, references, actions, variables and translations pass validation, publish creates an immutable version. Content changes need another publication. Invoke the published resource explicitly through SDK/API and verify the pinned Version and current Customer. Preview does not establish delivery to a customer.