Edit project source in Code and check the result in Preview.
For a first check, choose a visible, bounded change such as revising a heading on an existing page.
Find the source
Open Code in the intended project. Use Files to browse the source or Search to find text that appears on the page.
Confirm the file belongs to the route or component you intend to change. If similar text appears in several places, inspect how each occurrence is used before editing it.
Make the change
Edit the relevant file and save it. For the heading example, change only the displayed wording first.
If you're using an agent to make the edit, review the changed files in Code rather than relying only on its summary.
Check the running preview
Open Preview, select the development preview target, and navigate to the affected route. Check the domain and URL: Preview can also show a deployed environment. Confirm the changed heading appears, then check nearby content and interactions.
For a responsive layout change, check both a wide and narrow view. For an agent or tool change, exercise the relevant task and inspect its result, rather than checking only whether the page opens.
Diagnose a preview failure
Use Console for browser-side errors such as a component failing to render. Use Logs for runtime or server failures.
If the old behavior remains, confirm the file was saved, the preview is showing the intended project and route, and the running preview has picked up the change. Repeat the original check after correcting the problem.
Review before deployment
Preview checks development behavior. Publish a release to deploy the change. When the change is ready for Git review, follow Move Studio changes into Git.
Next
- Deploy a project: Create a release and deploy the reviewed change.