Rebuild the form editor as one document

.vitepress/config.mts

@@ -29,8 +29,8 @@ export default defineConfig({
                         text: "Managing Forms",
                         link: "/workbench/managing-forms",
                     },
-                    { text: "Workbench", link: "/workbench/workbench" },
-                    { text: "Storyboard", link: "/workbench/storyboard" },
+                    { text: "Form Editor", link: "/workbench/workbench" },
+                    { text: "Outline", link: "/workbench/storyboard" },
                     { text: "Form Blocks", link: "/workbench/form-blocks" },
                     {
                         text: "Conditional Logic",
@@ -43,26 +43,26 @@ export default defineConfig({
                 collapsed: true,
                 items: [
                     {
-                        text: "Information Block 📝",
+                        text: "Text only 📝",
                         link: "/input-types/no-interaction",
                     },
                     {
-                        text: "Multiple Choice 🔘",
+                        text: "Single choice 🔘",
                         link: "/input-types/multiplechoice",
                     },
                     { text: "Checkboxes ✅", link: "/input-types/checkboxes" },
-                    { text: "Short Text 💬", link: "/input-types/short-text" },
-                    { text: "Long Text 📄", link: "/input-types/long-text" },
+                    { text: "Short text 💬", link: "/input-types/short-text" },
+                    { text: "Long text 📄", link: "/input-types/long-text" },
                     { text: "Number 🔢", link: "/input-types/number" },
                     { text: "Email 📧", link: "/input-types/email" },
                     { text: "Link 🔗", link: "/input-types/link" },
                     { text: "Phone ☎️", link: "/input-types/phone" },
                     { text: "Date 📅", link: "/input-types/date" },
-                    { text: "Secret 🔒", link: "/input-types/secret" },
+                    { text: "Hidden text 🔒", link: "/input-types/secret" },
                     { text: "Rating ⭐", link: "/input-types/rating" },
                     { text: "Scale 📊", link: "/input-types/scale" },
                     {
-                        text: "File Upload 📁",
+                        text: "File upload 📁",
                         link: "/input-types/file-upload",
                     },
                     { text: "Consent ✓", link: "/input-types/consent" },

CHANGELOG.md

@@ -14,6 +14,9 @@ Lines marked **Upgrade step** need you to act after updating.
 -   The API can copy a question (`POST /api/blocks/{block}/duplicate`) with its text, settings, answers and Required, but not its rules or its Identifier, so links that fill in answers and webhooks can't mix the two up. The copy goes right after the original. (#262)
 -   The public form API has a preview mode for the form's team: start a session with `preview: true`, also for a draft. Answers in preview mode are never stored or counted and send no webhooks or emails. (#266)
 -   Add `?preview=1` to your form's link to try it as a member of its team. Nothing is stored, files aren't uploaded and the form doesn't redirect at the end. (#270)
+-   Add a question right where you need it: between questions or from a question's menu, and type "/" in an empty question to pick its answer type. A picker groups the answer types as Text, Choice, Rating, Other and Content, and the new question opens ready to type. The answer types have new names, like Single choice, Short text and Text only. (#276)
+-   The form editor shows the end screen as the last block of your form. You can edit its headline, text and button right there, and the End screen tab in Settings shows the same values. (#271)
+-   "Preview" in the editor shows your form beside the questions, on tablet and phone as a panel. It follows the question you edit, and the editor follows when you click Next in it. On the other form pages, "Preview" opens your form in a new tab in preview mode. Answers in either preview aren't saved. (#273)
 
 ### Changed
 
@@ -23,6 +26,11 @@ Lines marked **Upgrade step** need you to act after updating.
 -   The form list loads faster when a team has many forms. It now needs the same few database queries for one form or a hundred. Before, every form added 3 queries. (#256)
 -   On screens narrower than 1280 px, a form's editor bar now sits in two rows under the app header: the form with Dashboard and Preview, then Editor, Settings, Integrations and Submissions as tabs. Nothing in it scrolls sideways any more, and the header keeps the logo and your team name. On every screen, keyboard focus in the editor bar and the account menu now shows a blue ring. (#257)
 -   A form's pages have one top bar instead of two: the form's name with its menu, a Draft or Live label, the pages, Preview, Publish and your account. Publish first checks for questions without text, rules that point to a deleted question and a missing privacy link. Once the form is live, Share has its link, Open form and Unpublish. On a phone the pages sit in a tab bar at the bottom. (#265)
+-   The form editor shows your whole form as one column. Each question shows its number, answer type, text, and if it is required, has rules or is hidden. The question you work on opens right there, also on a phone, where you couldn't edit questions before. Hiding a question, random order and custom answers are now under the question's Settings. An outline next to the form jumps to any question, and on a phone a question's Settings open from the bottom of the screen. Move a question with Alt+Up/Down, with Move up and Move down in its menu, or by dragging. Duplicate in a question's menu puts a copy right below it. (#268, #272, #275, #277)
+-   Each rule now shows as a sentence under its question, and a group says when it's hidden. Edit changes a rule right there, and for choices, ratings and scales you pick the answer instead of typing it. A rule whose question was deleted shows in red and can't be saved until you fix it. (#274)
+-   The form editor uses plain words: a question's settings are headed by its answer type, like Choices or Rating, "Identifier" is now "Short name", and every switch shows on or off. Settings name what they do, like "Lowest value", "Shuffle choices" and "None ticked: all types allowed." on file uploads. (#279)
+-   The editor's preview shows the end screen while you edit it, with your latest text, and says so when your form sends people to a link instead. Its button opens in a new tab there, so you stay in the editor, and typing in a question you just opened no longer goes into the preview. On a tablet or phone, Esc closes the preview even after you clicked into it. Settings now calls the Completion Page "End screen", like the editor. (#280)
+-   In the form editor a thin line marks where each question starts, its number stands out more, and the question you edit gets more room around it. On a phone the editor keeps a wider margin at the sides. (#281)
 -   A logic rule with a missing field now tells you in plain words what to fill in, like "Pick a question for condition 1." (#278)
 -   Deleting a question, a group, an answer choice, a consent policy or a logic rule in the form editor now asks first in the app's own dialog. It names the question, how many answers will be deleted with it, and the questions whose rules will stop working. A choice nobody picked, or a policy nobody agreed to, is still deleted at once. (#269)
 

docs/embedding-forms.md

@@ -115,13 +115,13 @@ https://app.getinput.co/form-uuid?iframe=1&hideTitle=1&alignLeft=1
 
 ## Prefill Questions
 
-You can fill in answers with URL parameters. The parameter name is the question's Identifier (open the question, then "More Settings"). For example, this fills the question with the Identifier `email`:
+You can fill in answers with URL parameters. The parameter name is the question's short name (open the question, then **Settings**, then **Short name**). For example, this fills the question with the short name `email`:
 
 ```
 https://app.getinput.co/form-uuid?email=ada@example.com
 ```
 
--   Works for short text, long text, email, number, phone and link questions. Parameters for other question types or unknown Identifiers are ignored.
+-   Works for short text, long text, email, number, phone and link questions. Parameters for other question types or unknown short names are ignored.
 -   The question still shows, so the visitor can check and change the answer. A question skipped by a jump doesn't send its prefilled answer.
 -   The value shows as plain text. Encode special characters: `%2B` for `+`, `%20` for a space.
 -   Number questions take digits with a dot as decimal separator, like `price=12.5`, rounded to the question's decimal places. Anything else is ignored.

docs/input-types/checkboxes.md

@@ -36,5 +36,5 @@ Checkboxes allow users to select multiple options from a list, making them perfe
 -   When you want to offer comprehensive option coverage
 
 ::: warning Note
-If you want users to select only one option from a list, use the **Multiple Choice (Radio)** input type instead.
+If you want users to select only one option from a list, use the **Single choice** input type instead.
 :::

docs/input-types/consent.md

@@ -7,7 +7,7 @@ The Consent input type is designed specifically for gathering agreement from use
 1. Choose **Consent** as the input type
 2. Enter a clear message explaining what the user is consenting to
 3. Configure the consent option with a concise label
-4. Toggle "Opt-In Required" if the consent is mandatory to proceed
+4. Turn on "Must be ticked" if people must agree to go on
 
 ::: tip Best Practice
 < Keep consent messages clear and specific. Explain exactly what users are agreeing to, and include links to relevant policies when appropriate.

docs/input-types/date.md

@@ -7,9 +7,9 @@ The Date input type allows users to select dates from a calendar interface, maki
 1. Choose **Date** as the input type
 2. Enter the question or prompt asking for a date
 3. Configure the date restrictions (optional):
-    - **Minimum Date**: Earliest date users can select
-    - **Maximum Date**: Latest date users can select
-    - **No Past Dates**: Toggle to prevent selection of dates before today
+    - **Min date**: Earliest date users can select
+    - **Max date**: Latest date users can select
+    - **No dates in the past**: Turn on to prevent selection of dates before today
 
 ::: tip Best Practice
 < Always specify what kind of date you're asking for (appointment date, birth date, event date, etc.) and the expected format in your prompt.

docs/input-types/file-upload.md

@@ -1,15 +1,15 @@
-# File Upload 📁
+# File upload 📁
 
-The File Upload input type allows users to attach files to their form responses. It supports multiple file types and offers a user-friendly drag-and-drop interface.
+The File upload input type allows users to attach files to their form responses. It supports multiple file types and offers a user-friendly drag-and-drop interface.
 
 ## How to use:
 
-1. Choose **File Upload** as the input type
+1. Choose **File upload** as the input type
 2. Enter instructions for what files users should upload
 3. Configure the upload settings:
-    - **Maximum Files**: Set how many files users can upload
-    - **Maximum File Size**: Limit file size (in MB)
-    - **Allowed File Types**: Choose which file formats are accepted
+    - **Most files**: How many files users can upload (1 to 10)
+    - **Largest file (MB)**: Up to 8 MB per file
+    - **File types**: Choose which file formats are accepted. None ticked: all types allowed
 
 ::: tip Best Practice
 < Be specific about what files you're looking for and any requirements (format, size, resolution, etc.) to avoid confusion and unsuccessful uploads.
@@ -40,7 +40,7 @@ The File Upload input type allows users to attach files to their form responses.
 -   **Document Collection**: ID verification or signed forms
 -   **Media Sharing**: Audio or video uploads for feedback
 
-## When to use File Upload:
+## When to use File upload:
 
 -   When you need users to submit existing files rather than typing information
 -   For collecting visual or media information that can't be entered as text

docs/input-types/long-text.md

@@ -1,14 +1,14 @@
-# Long Text 📄
+# Long text 📄
 
-The Long Text input type provides a multi-line text area for collecting detailed, open-ended responses from users. It's ideal for comments, feedback, descriptions, and any situation where users need to enter more than a brief phrase.
+The Long text input type provides a multi-line text area for collecting detailed, open-ended responses from users. It's ideal for comments, feedback, descriptions, and any situation where users need to enter more than a brief phrase.
 
 ## How to use:
 
-1. Select **Long Text** as the input type
+1. Select **Long text** as the input type
 2. Enter the question or prompt
 3. Configure the text area options:
-   - **Rows**: Number of visible text rows (1-10, default: 5)
-   - **Maximum Characters**: Limit on response length (default: 500)
+   - **Height in lines**: How many lines the field shows (1 to 10, default: 5)
+   - **Max characters**: Limit on response length (default: 500)
    - **Placeholder**: Hint text shown when the field is empty
 4. Toggle the "Required" option if necessary
 
@@ -35,7 +35,7 @@ The Long Text input type provides a multi-line text area for collecting detailed
 💡 Set an appropriate character limit based on the expected response length. For short paragraphs, 500 characters is usually sufficient, while detailed feedback might require 1000+ characters. Add clear instructions about the level of detail you're looking for to guide users.
 :::
 
-## When to use Long Text:
+## When to use Long text:
 
 - When you need more than a single line of text
 - For qualitative, open-ended responses
@@ -45,13 +45,13 @@ The Long Text input type provides a multi-line text area for collecting detailed
 - For feedback that requires elaboration
 
 ::: warning Note
-While Long Text fields are great for detailed responses, very long responses may be difficult for users to type, especially on mobile devices. For extremely detailed information, consider breaking your questions into smaller, more focused parts.
+While Long text fields are great for detailed responses, very long responses may be difficult for users to type, especially on mobile devices. For extremely detailed information, consider breaking your questions into smaller, more focused parts.
 :::
 
 ## Technical Details:
 
 - Text can include line breaks and paragraphs
 - The character counter updates in real-time as users type
 - Maximum storage capacity is virtually unlimited
-- Long Text fields cannot include rich formatting (bold, italics, etc.)
+- Long text fields cannot include rich formatting (bold, italics, etc.)
 

docs/input-types/multiplechoice.md

@@ -1,10 +1,10 @@
-# Multiple Choice 🔘
+# Single choice 🔘
 
 This input type allows users to select one option from a list of choices, perfect for questions with mutually exclusive answers.
 
 ## How to use:
 
-1. Choose **Multiple Choice (Radio)** as the input type
+1. Choose **Single choice** as the input type
 2. Enter the question or prompt
 3. Add your answer options, one per line
 4. Toggle the "Required" option if necessary
@@ -14,7 +14,7 @@ This input type allows users to select one option from a list of choices, perfec
 -   **Single Selection**: Users can select exactly one option
 -   **Visual Clarity**: Clear indication of which option is selected
 -   **Option Ordering**: Arrange options in a meaningful sequence
--   **Randomization**: Option to randomize choice order to reduce bias (if available)
+-   **Shuffle choices**: Show the choices in a random order to reduce bias
 
 ## Example Uses:
 
@@ -28,7 +28,7 @@ This input type allows users to select one option from a list of choices, perfec
 🌟 Keep options mutually exclusive and limit the number of choices to prevent overwhelming users. Consider adding an "Other" option for unexpected responses, and arrange options in a logical order (alphabetical, numerical, or by relevance).
 :::
 
-## When to use Multiple Choice:
+## When to use Single choice:
 
 -   When users should select only one option from a list
 -   For questions with mutually exclusive answers
@@ -40,4 +40,4 @@ This input type allows users to select one option from a list of choices, perfec
 If users might need to select more than one option, use the **Checkboxes** input type instead.
 :::
 
-![Multiple Choice Example](/assets/multiplechoice.gif)
+![Single choice example](/assets/multiplechoice.gif)

docs/input-types/no-interaction.md

@@ -1,10 +1,10 @@
-# Information Block 📝
+# Text only 📝
 
-The Information Block displays information without requiring any user input. It's perfect for instructions, introductions, explanations, or content that doesn't need a response.
+A Text only block displays information without requiring any user input. It's perfect for instructions, introductions, explanations, or content that doesn't need a response.
 
 ## How to use:
 
-1. Choose **Information Block** as the block type
+1. Choose **Text only** as the block type
 2. Enter the content you want to display
 3. Format your text using markdown for headings, lists, links, and emphasis
 4. Add buttons if you want users to acknowledge the information or make a choice
@@ -26,10 +26,10 @@ The Information Block displays information without requiring any user input. It'
 -   **Thank You Messages**: Acknowledgments for participation
 
 ::: tip Best Practice
-🌟 Keep information blocks concise and visually structured. Use headings, bullet points, and formatting to make content scannable and easy to understand.
+🌟 Keep Text only blocks concise and visually structured. Use headings, bullet points, and formatting to make content scannable and easy to understand.
 :::
 
-## When to use Information Blocks:
+## When to use Text only blocks:
 
 -   When you need to provide context before asking questions
 -   For introductory or concluding information
@@ -38,5 +38,5 @@ The Information Block displays information without requiring any user input. It'
 -   For any informational content that doesn't require user input
 
 ::: warning Note
-Since Information Blocks don't collect any data, they won't appear in your submission results. They're purely for communication with your users.
+Since Text only blocks don't collect any data, they won't appear in your submission results. They're purely for communication with your users.
 :::

docs/input-types/number.md

@@ -7,8 +7,8 @@ The Number input type is specifically designed for collecting numerical data wit
 1. Choose **Number** as the input type
 2. Enter the question or prompt
 3. Configure the number options:
-   - **Decimal Places**: How many decimal digits to allow (0-10)
-   - **Symbol**: Optional character(s) to display before the number (e.g., $, €, %)
+   - **Decimal places**: How many decimal digits to allow (0-10). Leave empty for whole numbers only
+   - **Symbol**: Shown next to the number, e.g. € or kg
    - **Placeholder**: Hint text to show when the field is empty
 4. Toggle the "Required" option if necessary
 
@@ -45,7 +45,7 @@ The Number input type is specifically designed for collecting numerical data wit
 - When you want proper numeric formatting (thousands separators)
 
 ::: warning Note
-Number inputs only accept numeric values. If users might need to add any text or explanations with their numbers, consider using a Short Text input instead.
+Number inputs only accept numeric values. If users might need to add any text or explanations with their numbers, consider using a Short text input instead.
 :::
 
 ## Technical Details:

docs/input-types/phone.md

@@ -4,7 +4,7 @@ This input type is specifically designed for collecting phone numbers with appro
 
 ## How to use:
 
-1. Select **Phone Number** as the input type
+1. Select **Phone** as the input type
 2. Enter the prompt asking for the phone number
 3. Optionally, add a placeholder showing the expected format
 4. Configure validation requirements if needed
@@ -28,7 +28,7 @@ This input type is specifically designed for collecting phone numbers with appro
 🌟 Always specify what the phone number will be used for and include a privacy statement. For international forms, include example formatting or country code instructions.
 :::
 
-## When to use Phone Number input:
+## When to use Phone input:
 
 - When you need to contact users by phone or SMS
 - For authentication or verification purposes