> ## Documentation Index
> Fetch the complete documentation index at: https://wisty.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Edit without AI

> Change text, styling, or source code directly, without using credits.

Open **Edit** in your project to change text or styling in the preview. Click **Save** when you're happy with the result; manual edits cost no credits.

Use a desktop browser for visual editing and the code editor.

## Make a visual change

<Steps>
  <Step title="Select an element">
    Open **Edit** and click the element you want to change in the preview. The left panel shows the controls available for that element.

    <Frame caption="Selecting the heading opens its text and styling controls. No changes have been made yet.">
      <img src="https://mintcdn.com/wisty/p0KgmgXmvqDkXTFQ/images/visual-editor.png?fit=max&auto=format&n=p0KgmgXmvqDkXTFQ&q=85&s=707c98c2be77b79cf9b286ddea096757" alt="Visual editor with the Sales Command Center heading outlined and its text, typography, color, and spacing controls on the left." width="2560" height="1640" data-path="images/visual-editor.png" />
    </Frame>
  </Step>

  <Step title="Make the change">
    For text, click the selected text again and type in the preview. For styling, use the panel's controls.

    Depending on the element, you can change typography, colors, spacing, or icon size. You can also reorder an element among its siblings or delete it.
  </Step>

  <Step title="Save or reset">
    Check the result in the preview, then click **Save**. The changes are written to your project's source and saved in its history.

    Click **Reset** to discard pending visual edits.
  </Step>
</Steps>

<Note>
  A repeated element can share the same source. If the panel says **Applies to N
  instances**, your edit affects all those instances. For example, changing one
  repeated record card can change every card.
</Note>

### When a control is locked

Some styles come from responsive rules or computed values that the visual editor can't rewrite. The control shows the current value read-only.

Ask for that change in chat, or make it in the code editor. If you have unsaved code edits, save or discard them before opening **Edit**.

## Edit the source code

You don't need to read code to use Wisty. The **Code** tab is available when you want to inspect a file or make a precise change yourself.

Reading, editing, and downloading code need a paid plan. On a trial, the **Code** tab shows file names only. [Choose a plan](/docs/billing/manage-subscription#choose-your-first-paid-plan) to open it.

1. Open **Code** and select a file from the tree.
2. Edit the file. A dot marks an unsaved draft.
3. Click **Save** to apply it. The preview reloads with your change.

**Reset** discards the selected file's unsaved draft. The editor is read-only while Wisty is generating.

Platform files are also marked **read-only**. These include build configuration, Salesforce integration helpers, and the shared UI library. Wisty refuses changes to those files so generated code can't alter the controls on its Salesforce access.

To add or remove a dependency, ask in chat. The `package.json` file is managed through that flow.

## Download the project

Open **Code** and click **Download project** below the file tree. Wisty prepares a ZIP containing your source, assets, and a README for working with the export.

<Frame caption="Download project is below the file tree in Code.">
  <img src="https://mintcdn.com/wisty/p0KgmgXmvqDkXTFQ/images/code-editor.png?fit=max&auto=format&n=p0KgmgXmvqDkXTFQ&q=85&s=28c9ad08c9b4f6039b427cd23f6500d8" alt="Code tab with App.tsx open and the Download project button below the file tree." width="1748" height="1616" data-path="images/code-editor.png" />
</Frame>

A developer can reuse the components and styles outside Wisty. Salesforce access, record actions, and user or record context need an integration in the new host. The exported README identifies the helpers to replace; downloading doesn't include a working Salesforce connection for another host.

After a manual edit, [publish changes](/docs/publishing/publish) when you're ready for viewers to use them. You can undo saved edits by [restoring a version](/docs/building/projects#restore-an-earlier-version).