[{"data":1,"prerenderedAt":136},["ShallowReactive",2],{"support-article-form-translate-the-form":3,"ls-connection":134},{"article":4,"related":30,"neighbors":100,"alternates":128},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":14,"notes":25,"updated":29},"form-translation","form","en","translate-the-form","Translate the registration form","Translate labels, placeholders and option labels; the form itself stays one.",[12,13],"The registration form is shared by every language of the page: the same fields, in the same order, with the same steps and required flags. What a visitor reads on it, the labels, the placeholders and the options of a dropdown, is translated per language.","The value a visitor picks in a dropdown is sent to Livestorm as the source option, whatever language its label was shown in, so your registrant data stays consistent.",[15,18,21],{"text":16,"image":17},"Open your page on step 2 · Form. The same language pill as on the Design step sits at the top of the panel.","\u002Fsupport\u002Fform-translation\u002Fen\u002Fstep-1.webp",{"text":19,"image":20},"Pick a version: each field says what is left to translate. Fields, their order, steps and required flags are shared by every language; only the texts visitors read are translated here.","\u002Fsupport\u002Fform-translation\u002Fen\u002Fstep-2.webp",{"text":22,"image":23,"caption":24},"Expand a field: its label, its placeholder and, for a dropdown, each option's label get a box of their own, with the source above. The value sent to Livestorm stays the source's.","\u002Fsupport\u002Fform-translation\u002Fen\u002Fstep-3.webp","The live preview on the right renders the form in the language shown.",[26,27,28],"The Livestorm terms consent and the session picker are translated by Venue in every language: nothing to do.","Update translations, in the language pill, also fills in the form texts that are missing or outdated.","A field you add later gets its translations at the next Update translations.","September 8, 2026",[31,51,74],{"feature":32,"category":6,"locale":7,"slug":33,"title":34,"lede":35,"purpose":36,"steps":38,"notes":46,"updated":50},"form-columns","two-columns","Show fields in two columns","Shorten the form by placing short fields side by side.",[37],"By default, each form field takes its own row. On forms with more than 3 to 4 fields, a 2-column layout shortens the form on screen: the register button stays visible without scrolling, which helps conversion.",[39,42],{"text":40,"image":41},"Open your page in the builder, on step 2 · Form. The Columns setting is in the Layout card, below the field list.","\u002Fsupport\u002Fform-columns\u002Fen\u002Fstep-1.webp",{"text":43,"image":44,"caption":45},"Choose 2 columns. In the live preview, short fields (first name, last name) sit side by side.","\u002Fsupport\u002Fform-columns\u002Fen\u002Fstep-2.webp","First name and Last name now share the same row in the preview.",[47,48,49],"Long fields — email, dropdowns — automatically stay full-width, even in 2 columns.","Below 4 short fields, a single column is usually easier to read.","The setting only changes the layout. The fields themselves come from Livestorm, except on an in-person page, which owns them — see “Fields on an in-person page”.","August 3, 2026",{"feature":52,"category":6,"locale":7,"slug":53,"title":54,"lede":55,"purpose":56,"steps":58,"video":68,"poster":61,"notes":69,"updated":73},"form-multi-step","multiple-steps","Split the form into multiple steps","Turn a long form into a progressive flow, with a progress bar.",[57],"A 7-field form shown all at once can discourage sign-ups. By splitting it into 2 or 3 steps, visitors see only a few fields at a time and move forward with a Next button — a progress bar shows where they are.",[59,62,65],{"text":60,"image":61},"Open your page in the builder, on step 2 · Form. The Steps setting is in the Layout card, below the field list.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-1.webp",{"text":63,"image":64},"Choose 2 steps. The live preview immediately shows the progress bar, “Step 1 of 2” and the Next button.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-2.webp",{"text":66,"image":67},"Very long form? Switch to 3 steps — the maximum. Then drag fields from one step to another to spread them out.","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fstep-3.webp","\u002Fsupport\u002Fform-multi-step\u002Fen\u002Fwalkthrough.webm",[70,71,72],"Consents and the submit button always stay on the last step — they can't be moved.","Each step adds a click before sign-up: reserve multi-step for forms of at least 6 to 7 fields.","An empty step is flagged by the builder — spread the fields before publishing.","July 15, 2026",{"feature":75,"category":6,"locale":7,"slug":76,"title":77,"lede":78,"purpose":79,"steps":81,"notes":95,"updated":99},"form-copy","wording","Customize the form's wording","Give the form title and catch line your own voice.",[80],"The form ships with default wording. Replacing it with your own title and catch line aligns the form with the event tone and gives a concrete reason to sign up.",[82,85,88,91],{"text":83,"image":84},"Open your page in the builder, on step 3 · Design.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-1.webp",{"text":86,"image":87},"Select the registration form: its properties carry a “Text inside the form” block.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-2.webp",{"text":89,"image":90},"Replace the form title with a message in your own voice. The preview updates as you type.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-3.webp",{"text":92,"image":93,"caption":94},"Add a catch line below the title — urgency, benefit or the event format — and, right under it, your own button label.","\u002Fsupport\u002Fform-copy\u002Fen\u002Fstep-4.webp","Custom title and catch line, visible right away in the live preview.",[96,97,98],"An action-oriented title (“Save your seat”) usually converts better than a descriptive label.","The same properties panel carries “Show logo on the form”, and the text that sits outside the form card.","Leave a field empty to fall back to the default text, translated into the event's language.","July 31, 2026",{"prev":101,"next":127},{"feature":102,"category":6,"locale":7,"slug":102,"title":103,"lede":104,"purpose":105,"steps":107,"notes":120,"generatedFrom":126,"updated":99},"in-person-fields","Fields on an in-person page","Choose what you ask for, and how it reads, when Venue owns the form.",[106],"A page built on a connected event mirrors that platform’s form. An in-person page has no platform behind it, so the form is yours: you pick the fields, write their labels and placeholders, and decide what is required.",[108,111,114,117],{"text":109,"image":110},"On step 2 · Form of an in-person page, the list is your form. The email is always there — it identifies each registrant — and “Add a field” at the bottom offers the rest.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-1.webp",{"text":112,"image":113},"Click a row to open it. “Field label” is what visitors read above the field; leave it empty to restore the default.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-2.webp",{"text":115,"image":116},"Add a placeholder — the example shown inside the field until someone types. Optional, and empty by default. The live preview shows both as you type.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-3.webp",{"text":118,"image":119},"Add what you need from “Add a field”: phone, job title, company, or a consent checkbox. “Remove field”, in the open card, takes one back out.","\u002Fsupport\u002Fin-person-fields\u002Fen\u002Fstep-4.webp",[121,122,123,124,125],"The email can never be removed: it is the identity behind the registration, the check-in and the QR ticket.","Each field carries its own required \u002F optional switch.","Collect job title and company if you print badges — those two lines come from these fields.","Layout works exactly as elsewhere: columns, steps and wording have their own Form guides.","A page built on a Livestorm or Zoom event works the other way round — the fields live on the platform and Venue mirrors them, see “Fields, consents and re-import”.","FormBuilder.vue (manual fields) · useManualFields.ts · i18n wizard.form.manual.*",null,[129,132],{"hreflang":130,"path":131},"fr","\u002Fsupport\u002Fformulaire\u002Ftraduire-le-formulaire",{"hreflang":7,"path":133},"\u002Fsupport\u002Fform\u002Ftranslate-the-form",{"connected":135},false,1788878226373]