# Create and edit a Page

Start with a blank canvas or template, arrange accessible content, save your draft, and review it before publishing.

## Create your first draft

Select the intended organization, open **Pages**, and choose **Create Page**. Choose a starting option, give the Page a clear title, and confirm with **Create Page**.

| Starting option | Use it when |
| --- | --- |
| **Blank Page** | You want to build a focused layout yourself. |
| **Official Template** | You want a complete editable starting design. Review all sample content and connections. |
| **Duplicate existing Page** | You want an independent draft based on one of your organization’s Pages. |
| **Import JSON** | You have a compatible exported Page definition. Review its resource references before use. |

Each creates an independent draft. A template is a starting design; it does not automatically configure your business process, reserve appointments, or connect your services.

## Build a simple service page

1. In **Library**, add a **Section** with a clear service heading and a short explanation.
2. Add **Text** describing who the service is for and what happens after a request. Add an **Image** with meaningful alternative text if it helps explain the service.
3. Add a **Form** with labeled inputs inside it. Start with a name, a contact address, and a request description. Give each input a unique field name.
4. Customize the form’s submit label to **Send request**. Connect its submission using the [workflow action guide](/pages/actions/).
5. Add a short expectation such as “We’ll review your request and contact you to discuss availability.” Avoid promising a confirmed booking.
6. Choose **Save draft**, check for issues, and open **Private preview** to review the saved draft.

Private preview suppresses workflow execution and Line launches. Use it for layout and configuration review; test real submissions deliberately after publishing with synthetic information and a suitable test workflow.

## Find your way around Studio

**Library** contains widgets and reusable **Blocks**. A block is a group of widgets, such as an FAQ or gallery. **Structure** shows the nested layout. Choose **Page root** before adding a top-level sibling; select a container before adding children inside it.

Select a widget to edit its inspector:

| Inspector area | What you change |
| --- | --- |
| **Content** | Visible text, labels, images, and widget-specific options. |
| **Appearance** | Available visual styles. |
| **Layout** | Nesting, position, alignment, and spacing. |
| **Data** | Records and visible field mappings. |
| **Actions** | What a submission, click, or selection does. |
| **Conditions** | Visibility or availability based on a field value. |

Use a **Structure name** to identify a widget in the editor; change **Content** to edit what visitors read. Move widgets with drag and drop or **Move earlier**, **Move later**, and **Place inside**.

## Edit text and reuse a layout

Double-click editable canvas text, or focus it and press **Enter** or **F2**. Enter finishes a short heading; **Ctrl+Enter** on Windows or **Cmd+Enter** on macOS finishes a paragraph. The **Content** inspector edits the same text. Bound text must be changed through its source or binding.

Use **Copy**, **Paste widget**, and **Duplicate** for reusable pieces. **Ctrl+Z** or **Cmd+Z** undoes a canvas edit; **Ctrl+Shift+Z** or **Cmd+Shift+Z** redoes it. When a text field has focus, text editing shortcuts apply to that field.

## Check small screens and keyboard use

Switch the canvas toolbar between **Phone**, **Tablet**, and **Desktop**. Use **Focus mode** for more canvas space. On a phone, switch between Library, Canvas, and Inspector.

Keep headings in a logical order and input labels visible. Check that long text wraps, buttons remain readable, tables can be used on a narrow screen, and visitors can reach controls with Tab. For a dialog, check opening, closing, and Escape. Use text as well as color for a status.

## Save and recover your work

Studio starts with manual saving. Choose **Save draft** regularly, or enable **Auto Save** for your organization and user in this browser. Both save only the draft. Watch **Saved**, **Saving**, **Unsaved changes**, and **Save failed**.

Keep the editor open if saving fails. Retry after checking connectivity. A revision conflict preserves local edits; export a copy before discarding them or reloading. When leaving with changes, choose **Save and leave**, **Discard changes**, or **Keep editing**.

**Draft history** lets you inspect and restore a saved checkpoint. Restoring a draft creates a new revision; visitors see it only after another publish. Use **Advanced → Export JSON** to keep a design copy. Imported database, workflow, and Line references must be reviewed against resources available to the destination organization.

Continue with [data connections](/pages/data/), [visitor actions](/pages/actions/), or [publishing](/pages/publishing/).
