# \[Support Guide\] Protecting Visual Editor Against Broken Code in Netlify Create **URL:** \ **Category:** Support Guides\ **Tags:** netlify-create, support-guide\ **Created:** [February 13, 2024, 10:18pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400 "2024-02-13T22:18:28Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![sid.m](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/sid.m/32/50638_2.png) [@sid.m](https://answers.netlify.com/u/sid.m)\ **Post date:** [February 13, 2024, 10:18pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/1 "2024-02-13T22:18:28Z")
_Last reviewed by Netlify Support in July 2025_ A strategy for working around bugs that appear in the branch that content editors use to visually edit their site. Netlify Create’s visual editing experience uses the code from a configured [_working_ Git branch](https://docs.netlify.com/create/features/cloud-project/publishing#working-branch). This is rarely the production branch, and it is often used to stage changes prior to releasing to production. As a result, it’s possible that a bug gets introduced which prevents content editors from making further changes to the site until the issue is resolved. ## Intermediary QA Environment To protect against this (and _improve quality_), you can establish an intermediary environment where all code changes considered _ready to deploy_ by developers can be reviewed easily by content editors (or dedicated QA) before being approved and deployed. ### Setting Up a QA Project Assuming you have a site called `awesome-site` with typical configuration, you can set up a QA environment with the following steps: 1. Create a branch in your repository for the site (e.g. `qa`, `acceptance`, etc.). 2. [Create a new project](https://create.netlify.com/import) by selecting _Use my repository_, and choose `preview` as the _target branch_ and your new branch (`qa`) as the _working branch_. Append “QA” to the end of the project name (e.g. `awesome-site (QA)`). ### QA Project Workflow The new workflow could then move like this: 1. Once this site is established, developers would merge their code from feature branches into `qa` (and _not_ into `preview`). 2. Those who have access to the new `awesome-site (QA)` project can then visually review new code in the `qa` branch. 3. Users with an _Owner_ or _Developer_ role for that project will be able to _publish_, which would merge the code from `qa` into `preview`. (This could also be done on GitHub.) 4. Once these changes are merged, editors working in the `awesome-site` project can then edit with confidence that the code in the branch is production-ready. ### Accounting for Headless CMS If your project uses a headless CMS, you can decide whether to have the QA project connect to the same CMS content. Or it could use staging or placeholder content that you configure using the project creation wizard. ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [April 10, 2024, 3:15pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/2 "2024-04-10T15:15:42Z")
Automatically bumped on April 10, 2024, 3:15pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [June 11, 2024, 11:32pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/3 "2024-06-11T23:32:51Z")
Automatically bumped on June 11, 2024, 11:32pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [August 15, 2024, 7:47am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/4 "2024-08-15T07:47:04Z")
Automatically bumped on August 15, 2024, 7:47am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [October 15, 2024, 5:03pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/5 "2024-10-15T17:03:44Z")
Automatically bumped on October 15, 2024, 5:03pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [December 15, 2024, 12:13am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/6 "2024-12-15T00:13:44Z")
Automatically bumped on December 15, 2024, 12:13am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [February 11, 2025, 7:06am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/7 "2025-02-11T07:06:07Z")
Automatically bumped on February 11, 2025, 7:06am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [April 7, 2025, 1:47pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/8 "2025-04-07T13:47:26Z")
Automatically bumped on April 7, 2025, 1:47pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [June 1, 2025, 7:03pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/9 "2025-06-01T19:03:59Z")
Automatically bumped on June 1, 2025, 7:03pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [July 25, 2025, 12:28am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/10 "2025-07-25T00:28:06Z")
Automatically bumped on July 25, 2025, 12:28am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [September 16, 2025, 6:51am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/11 "2025-09-16T06:51:53Z")
Automatically bumped on September 16, 2025, 6:51am UTC ---
**Author:** ![ibrahim\_olayiwola](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/ibrahim_olayiwola/32/67688_2.png) [@ibrahim\_olayiwola](https://answers.netlify.com/u/ibrahim_olayiwola)\ **Post date:** [September 16, 2025, 11:13pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/12 "2025-09-16T23:13:09Z")
thanks i love you idea it is short and meaningful ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [November 7, 2025, 1:18pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/13 "2025-11-07T13:18:14Z")
Automatically bumped on November 7, 2025, 1:18pm UTC ---
**Author:** ![jackcooper](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@jackcooper](https://answers.netlify.com/u/jackcooper)\ **Post date:** [December 21, 2025, 9:53am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/14 "2025-12-21T09:53:12Z")
This is a solid approach and highlights a common pain point when visual editors depend directly on a mutable code branch. Introducing a dedicated QA environment creates a clear buffer between development changes and content editors, which helps prevent productivity blocks when broken code slips in. It also formalizes review and accountability without slowing down development. [Netlify Visual Editor overview | Netlify Docs](https://docs.netlify.com/create/features/cloud-project/publishing#working-branch) The workflow mirrors best practices used in media and content pipelines, where edits are validated in a staging environment before being released—similar to how creators test timelines or effects in tools like [CapCut Pro APK](https://capcutproapk.com.co/) before exporting final assets. Keeping editors insulated from experimental changes significantly improves reliability and confidence. Overall, this setup seems like a practical balance between flexibility for developers and stability for non-technical editors. ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [February 5, 2026, 12:25am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/15 "2026-02-05T00:25:18Z")
Automatically bumped on February 5, 2026, 12:25am UTC ---
**Author:** ![stumbleguys1](https://avatars.discourse-cdn.com/v4/letter/s/9de053/32.png) [@stumbleguys1](https://answers.netlify.com/u/stumbleguys1)\ **Post date:** [February 17, 2026, 6:17pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/18 "2026-02-17T18:17:58Z")
This QA branch strategy is actually a smart safeguard — separating staging (`qa`) from preview prevents broken commits from blocking editors in **Netlify Create**. We use a similar workflow mindset when testing updates and performance tweaks before publishing live guides. For example, when covering updates and optimization strategies for **Stumble Guys** , we stage and validate everything before pushing to production to avoid broken assets or outdated builds. Full breakdown here: 👉 [[https://thestumbleguysapk.com/](https://thestumbleguysapk.com/)]([https://thestumbleguysapk.com/](https://thestumbleguysapk.com/)) Clean staging + controlled publishing = smoother experience for both developers and end users. ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [April 10, 2026, 7:28am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/19 "2026-04-10T07:28:16Z")
Automatically bumped on April 10, 2026, 7:28am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [April 14, 2026, 7:46am UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/21 "2026-04-14T07:46:56Z")
Automatically bumped on April 14, 2026, 7:46am UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [June 2, 2026, 1:22pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/22 "2026-06-02T13:22:47Z")
Automatically bumped on June 2, 2026, 1:22pm UTC ---
**Author:** ![system](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/system/32/13_2.png) [@system](https://answers.netlify.com/u/system)\ **Post date:** [July 22, 2026, 7:33pm UTC](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400/23 "2026-07-22T19:33:30Z")
Automatically bumped on July 22, 2026, 7:33pm UTC [Next page](https://answers.netlify.com/t/support-guide-protecting-visual-editor-against-broken-code-in-netlify-create/109400.md?page=2)