Edit a website's code directly
Switch on the Code editor, move a site into it, and let the agent make changes you approve. Moving a site is permanent.
The written steps below are complete. The Video script tab shows exactly what the video will cover.
The Code editor is an alternative to the workbench for people comfortable with HTML and CSS. It shows a site as files, with a code editor and an agent that can read and change any file. It is off until the workspace owner switches it on. Read step 2 carefully: a site that moves into the Code editor cannot move back.
By the end you can
- Switch on the Code editor
- Understand that moving a site into it is permanent
- Approve or reject the agent's changes
- Restore an earlier state and publish
Screens used
Steps
- 1
Switch it on
On: /settings/code-ideOpen Settings and choose Code IDE. Turn the switch on. Only the workspace owner can.
You should see: "Saved."
- 2
Decide before you move a site
On: Project, Web DesignOpen a site in Web Design and press Code editor at the top. A message asks you to confirm, because this is permanent: the site's pages move into files, and the workbench can no longer edit them. Practise on a copy or a test site first. To start a new code project instead, choose New app when creating a site.
You should see: A file tree on the left, a code editor in the middle and the site chat on the right.
- 3
Edit a file
On: Code IDEOpen a page or a stylesheet from the file tree and edit it. Standard editor shortcuts work, such as find and replace. Press ▶ Preview to see the site in a new tab.
You should see: Your edit is saved as a draft. The live site does not change.
- 4
Ask the agent
On: Code IDEDescribe a change in Site chat, for example "make every button use rounded corners". You can paste a screenshot to show what you mean. The agent reads and searches files by itself, but asks before it writes, changes or deletes one, and shows the difference first.
You should see: A proposed change waiting for your approval.
- 5
Approve, and undo if needed
On: Code IDEApprove the changes you want; Approve all accepts every change in that answer. Before each approved change the editor saves a checkpoint. Press ↻ History to open Checkpoints and Restore an earlier state.
You should see: The files show the change, or are back as they were.
- 6
Publish
On: Code IDEPress Publish at the top of the Code editor. It opens the same publish window as any other site.
You should see: The live site shows the change.
Tips
- Most page-by-page edits are faster in the workbench. Move a site to the Code editor only when you need to work on its files.
- ⤓ Download saves the whole site as a .zip you can open or host anywhere.
- ❖ Sections, ▤ Form and ✦ Themes insert ready-made sections, build a form and change colours and fonts without writing code.
- Switching the Code IDE off in Settings does not delete anything built in it.
Troubleshooting
- There is no Code editor button on the site.
- The Code IDE is switched off for the workspace, or your role cannot edit the design. Ask the workspace owner.
- You cannot switch a site back to the workbench.
- This is by design. Once a site's pages are files, only the Code editor can change them. Use Checkpoints to undo changes.
- "You don't have permission to publish"
- Your project role can edit but not publish. Ask a project owner to publish.
One row per shot, in the same order as the guide. Estimated length 2:52, recorded signed in as Owner. Use made-up data only. How to record
Say: Edit a website's code directly. Switch on the Code editor, move a site into it, and let the agent make changes you approve. Moving a site is permanent.
Hold until you see: Lesson title on screen for three seconds.
Say: Open Settings and choose Code IDE. Turn the switch on. Only the workspace owner can.
Hold until you see: "Saved."
Say: Open a site in Web Design and press Code editor at the top. A message asks you to confirm, because this is permanent: the site's pages move into files, and the workbench can no longer edit them. Practise on a copy or a test site first. To start a new code project instead, choose New app when creating a site.
Hold until you see: A file tree on the left, a code editor in the middle and the site chat on the right.
Say: Open a page or a stylesheet from the file tree and edit it. Standard editor shortcuts work, such as find and replace. Press ▶ Preview to see the site in a new tab.
Hold until you see: Your edit is saved as a draft. The live site does not change.
Say: Describe a change in Site chat, for example "make every button use rounded corners". You can paste a screenshot to show what you mean. The agent reads and searches files by itself, but asks before it writes, changes or deletes one, and shows the difference first.
Hold until you see: A proposed change waiting for your approval.
Say: Approve the changes you want; Approve all accepts every change in that answer. Before each approved change the editor saves a checkpoint. Press ↻ History to open Checkpoints and Restore an earlier state.
Hold until you see: The files show the change, or are back as they were.
Say: Press Publish at the top of the Code editor. It opens the same publish window as any other site.
Hold until you see: The live site shows the change.
Say: That is edit a website's code directly. The written steps are on this lesson's page in the ItzSEO course.
Hold until you see: End card with the lesson link.
Reference articles on this topic
Mark it complete to keep your place in the course.
Related lessons
Change text and styles by clicking, ask for bigger changes in the chat, add ready-made sections and undo a change.
Check the site for issues, publish it to a free address, connect your own domain and roll back if something goes wrong.
Show a client their finished website behind a pay page, take the advance into your own account and unlock it.