Developers and marketers on the same website: code and chat together
Short answer: The safest way for a developer and a marketer to share one website is to split the work by type. Marketers change words, images and table rows through chat or an editor, and developers change layout and logic in code, on separate branches (private copies of the work) that are reviewed before they go live. Ploy, an AI marketing platform that builds and hosts websites through chat, supports this with GitHub Code Sync, a link between one site and a GitHub repository (a stored, versioned copy of the site's code). Ploy's own docs call it an advanced feature and say conflicts still happen, so set rules before you start.
Your developer wants to work in code. Your marketer wants to type a request in a chat box and see the page change. Both are right, and the risk is a site that only one person understands or one vendor controls.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
The direct answer: give each person a lane. Content (headlines, offers, blog posts, rows in a table) goes to the marketer, through chat or a simple editor. Layout, components and logic go to the developer, through Git, a free tool that records every change to a set of files. Nothing from the developer's lane reaches the live site until a second person has looked at it. If you use a tool with a chat editor and a code link, such as Ploy, the same rule holds, and the main job is to keep the two lanes from editing the same file at the same time.
This page may contain affiliate links from which Blur Studio earns commissions.
The real problem: one vendor or one person knows the code
Teams fail in one of two ways. Either the site lives in a builder, nobody has the code, and a later developer cannot change what the builder does not allow. Or it lives in a repo only one developer understands, and every headline change becomes a ticket for that person.
The fix for both is the same: keep a real copy of the code in a place you control, and keep ordinary content out of the code so non-developers can change it without risk. Related: how to publish website updates without waiting for your developer and who owns your website code and how to get access.
Git in plain words
You need six terms.
- Repository (repo). The folder of site files plus the full history of every change. GitHub is a website where teams store repos and review each other's work.
- Branch. A private line of work copied from the main version. You can change things on a branch without touching the live site.
- Commit. One saved change with a short message.
- Pull request (PR). A request to merge a branch into the main one. It shows what changed and lets a teammate approve first. Merge means combining the branch into the main version.
- Merge conflict. What happens when two people changed the same line, or one person edited a file the other deleted. GitHub's docs say Git cannot safely choose which version to keep, and that you must resolve every conflict before a pull request can be merged.
One more term matters for teams: a protected branch. GitHub lets an owner set rules on the main branch, such as requiring an approved pull request, passing checks and resolved comments before a merge, and blocking force pushes (overwriting history). GitHub's docs say these rules are available on public repositories on its free plan, and on private repositories on its paid plans, so check which plan your repo is on.
Options from least to most effort
Pick the lightest option that keeps the lanes apart. Prices are as of November 2026; check each vendor's page before you buy.
| Option | How the lanes work | Cost shown | Weak point |
|---|---|---|---|
| No tool: a plain copy on your own drive | A developer keeps the code, the marketer sends text by email or a shared document, and you save a dated copy of pages and data yourself. | $0 | Slow, and the copy goes stale unless someone owns the habit. |
| Custom-coded site by a developer | The developer builds in a framework and a repo, and either edits content in code or adds a separate editor. | Quote only; ask for hosting, upkeep and handover in writing | Every change waits on the developer unless a content editor is part of the build. |
| Webflow, a visual website builder | Marketers edit visually. Developers add custom code inside the builder. | Starter free; Basic $15 a month billed yearly; Premium, for content-rich sites, $25 a month billed yearly (Webflow pricing page) | Your site lives in Webflow's system. Check its export rules before you rely on a code copy. |
| v0, an AI tool from Vercel that writes web page code from a text prompt | Developers take the generated code into their own repo. | Check the vendor page | It generates code. It is not an editor for the marketing team. |
| Ploy with Code Sync | Marketers use chat. Developers use a GitHub repo that stays in step with the site. | Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote (Ploy pricing page) | Advanced feature; conflicts still need a person. Details below. |
For a wider comparison of building on a platform versus custom code, see Ploy against a custom Next.js site.
Where Ploy fits (one option of several)
Ploy is built on Astro (a free framework for building websites), React (a library for building page parts) and Tailwind (a styling toolkit), according to its docs, and each site lives in code. Its Code Sync page describes this workflow:
- Code Sync connects one site to one GitHub repository. It is not a workspace-wide setting.
- Ploy's AI agent commits its changes to branches, opens pull requests, and can pull in changes your team pushed to GitHub. Each commit carries a clear message so it can be reviewed like any other.
- To bring developer changes into Ploy, use Sync from GitHub on the site's Developer page, run the command
ploy site code-sync sync, or ask the agent. Ploy says it usesgit pull --rebase --autostashso edits in the editing sandbox are not lost. - If the editor and outside code changes conflict, you can ask the agent to resolve it, or resolve it in GitHub and ask the agent to pull the result. Ploy also says to follow the usual developer practice for source control.
- Only owners and admins of the workspace connect or disconnect Code Sync. Disconnecting leaves the code intact; later edits just stop syncing. Collaborators are invited by their GitHub username.
- Ploy-managed repositories do not support third-party GitHub integrations. Ploy's workaround is to keep a mirror (a second copy) in your own GitHub account and attach the integration there.
The command-line tool (CLI, a program you run by typing commands) adds a second route. ploy site git lets you clone the site's code and push changes with plain Git on every plan, and Member role or higher is needed. If you prefer not to use GitHub, that is the way in.
Free or paid: two statements that disagree
Ploy's docs say Code Sync is free on every plan, including Free, when you set it up through the CLI with ploy site code-sync init, and that connecting it from Workspace Settings in the app needs a paid plan. Ploy's pricing page lists GitHub Code Sync as "via CLI" on Free and included on Starter, Pro and Enterprise. Ploy's own comparison page against WordPress says paid plans get the full source code in Git through GitHub Code Sync. Those do not match, so check the docs and the pricing page for your plan on the day you buy, and ask Ploy if you need it in writing.
What the docs do not say
- Whether GitHub branch protection rules apply to the repo Ploy manages. The docs show the repo URL under Ploy's own GitHub organisation, while the FAQ says "a GitHub repository you control". Ask Ploy who can set rules on it.
- Whether you get a preview link for each pull request, or how simultaneous edits are handled beyond the conflict notes above.
- Code and data export after you cancel. Ploy's terms say your data is available for export for 30 days after termination and its privacy policy says 60 days of retention for export, and neither text covers code beyond the clone command. Keep your own clone.
- SOC 2 status. Ploy's pages differ (a Type 1 report in its Trust Center, a Type II mention on a feature page), so ask Ploy for the report if a client needs it.
A division of work that avoids most fights
This split is my suggestion, not a Ploy rule. Adjust it to your team.
| Type of change | Who | How | Review |
|---|---|---|---|
| Words on a page, offers, images, FAQs | Marketer | Chat with the agent, or edit text in the preview | Marketer checks the preview, then publishes |
| Lists that become pages (team, locations, case studies) | Marketer | Rows in Ploy's database (PloyDB), a spreadsheet-style table where each row can become a page; Ploy says edits usually reach visitors within a minute | Spot check |
| New page layout, new component, forms logic | Developer | Branch, then pull request | A second person approves |
| Anything touching the same file as an open branch | Whoever started first | Post it in the team channel first | Sync before publishing |
Keep content in tables and chat, and layout in code. When requests mostly change rows and text, the agent rarely touches the files the developer is working on.
Worked example
A five-person agency (made-up numbers) has one marketer, Priya, and one developer, Dan. The site has 24 pages. Each week Priya asks the agent for about 15 text and image changes, and Dan opens about two pull requests.
- Monday: Dan creates a branch for the pricing table and tells the channel he is in
PricingTable.astro. - Tuesday: Priya asks the agent to change the pricing page headline. The agent edits the page file, not the component, and commits with a message such as "Update pricing headline".
- Wednesday: Dan finishes and opens a pull request. A second person looks at the changes, runs the preview and approves.
- Wednesday afternoon: Dan merges. Priya asks the agent to sync from GitHub, checks the pricing page in preview and publishes.
- Thursday: Dan pushes a quick fix straight to GitHub. Priya's next publish shows "Publishing paused because storage holds newer changes". Her edits are safe in the preview. She asks the agent to sync, then publishes again. This is the situation Ploy's docs describe, and it is the reason the rule below says no direct pushes to main.
Total cost of the setup in this example: one Starter plan at $50 a month (or $480 billed yearly, as of November 2026) if connecting from the app is needed, and Dan's time to set the rules once. Credits do not roll over, and Starter includes 4,000 a month.
Four rules to write down before the first change
- Main is protected. No direct pushes to the main branch. Everything goes through a pull request with one approval. If you cannot set this on the repo Ploy manages, mirror to a repo you control and use that as the review point.
- Sync before you publish. The marketer syncs first, then reviews the preview, then publishes.
- Roles are limited. Only owners and admins connect Code Sync. See team seats, roles and client access.
- A weekly clone. Run
ploy site git cloneinto a folder you control and keep the dated copy.
Step by step: move an existing site into this setup
- Check which framework you use. Ploy's docs say a compatible Astro repository imports directly. Next.js and Vite with React (other common website frameworks) are ported by your own coding agent into Ploy's Astro starter, and Ploy's docs say that uses no Ploy AI credits. A coding agent is an AI assistant, such as Claude Code or Codex, that edits code on a developer's computer.
- Read the repository contract. The docs ask for a
package.jsonat the root whose name is exactlyploy-web, Astro installed as a dependency, and anastro.config.mjsthat exports a plain config object. They list supported major versions (Astro 6, the Cloudflare adapter (the part that runs the site on Cloudflare's network) 13, React 5, Sitemap 3), and warn that a project that builds elsewhere can still fail on Ploy if versions differ. Check the page for the current list before you start. - Test a small import. Start a free site with a Ploy account, import a copy of one section, and check forms, redirects, images and speed on desktop and mobile. The import command makes a new site each time, so it is a trial.
- Confirm what you can export. Run
ploy site git cloneon the test site and open the files. If you can read and build them, the exit route works. - Ask the vendor about anything unclear. Use the list under "What the docs do not say" as your email.
A full move of a live site has more steps: moving a website to Ploy.
What goes wrong and how to spot it
| Symptom | Likely cause | Fix (per Ploy's docs) |
|---|---|---|
| Publishing paused, storage has newer changes | Someone pushed straight to GitHub | Ask the agent to sync the source, resolve any conflict, publish again |
| Push rejected | The remote has new commits | Run git pull --rebase --autostash locally, resolve conflicts, push again |
| Merge conflict | Two people changed the same lines | Resolve in GitHub, then ask the agent to pull the resolved branch |
Test plan with pass and fail criteria
Run this on a free test site before you commit the team to it.
- Marketer asks the agent for a headline change. Pass: a commit appears with a readable message. Fail: no commit, or an unclear one.
- Developer pushes a small change on a branch and merges it. Marketer syncs. Pass: the change shows in preview with no manual file copying.
- Both edit the same line on purpose. Pass: you resolve it in under 30 minutes. Fail: you lose an edit or cannot tell which version is live.
- Run
ploy site git cloneinto a new folder. Pass: your developer can read the files. - Ask Ploy in writing about branch protection, per-PR previews and export after cancellation. Pass: a clear written answer. Fail: a vague reply. Decide whether you can live with that.
When to skip this setup
- Your site needs logins, payment logic or heavy custom features. That is an application. Custom code is the better pick. See connecting a marketing site to your own app or database.
- Your team has no developer. Code sync adds nothing. Use the chat editor alone and keep a periodic clone.
- Non-technical owners will touch the repo. Do not give them GitHub access. Keep them in chat and the preview.
How I'd approach this
I would not start with a tool. I would start with the split of work: a one-page note that says marketers own words and tables, developers own layout and logic, and nothing from the developer side goes live without a second pair of eyes. Then I would test the setup on a free Ploy site or the tool of your choice, because the cost of finding a limit on a test site is zero. If your site is mostly pages, forms and a blog, and a developer wants a real repo, Ploy with Code Sync is a fair option. If the site is really an app, or you need guarantees the docs do not give, pick custom code or another tool. Blur Studio builds the custom version, including AI agents that use your business knowledge, calendar and CRM connections, finishing a half-built site and taking it live, and ongoing care; see what that includes.
First week. Day 1: write the one-page split and the four rules. Day 2: create a free test site, import one section and run the clone. Day 3: run the five-step test plan, including the deliberate conflict. Day 4: send the vendor your questions. Day 5: decide, using this rule: if the test passes and the written answers are clear, move one low-risk section first; if a test fails, keep the current setup and revisit next quarter.
A closely related page covers the same ground from another angle: Competitor Comparison Pages: Options for Getting Them Built.
A closely related page covers the same ground from another angle: Can Clients Pay for Their Own Website Plan? Billing Options for Agencies.
For the next step, see Agency Partner Programs for Website Platforms: Referral Options.
For the next step, see Who Changed What? How to Keep a Record of Website Edits.
Questions people ask
Can a developer and a marketer edit the same website without breaking each other's work?
Yes, if they work in separate lanes and use branches and reviews. Git cannot choose a winner when two people edit the same line, so conflicts still happen sometimes. The way to reduce them is to keep content in chat and tables, keep layout in code, and merge small changes often.
Does Ploy Code Sync cost extra?
Ploy's docs say Code Sync is free on every plan when set up through its command-line tool, and that connecting it from the app needs a paid plan. Its pricing page lists it as "via CLI" on Free. Its WordPress comparison page says paid plans get it. Check the docs and pricing page on the day you buy.
Can I get my website's code out of Ploy?
Ploy's FAQ says you can clone the full source with ploy site git clone on every plan, with Member role or higher. What happens to code after you cancel is not spelled out in its terms, which mention a data export window of 30 days, and its privacy policy says 60 days. Keep your own dated clone. See who owns your website and content, export and lock-in.
Does GitHub branch protection work on a Ploy site?
Ploy's docs do not say. GitHub's own rules can require approved pull requests and passing checks, but whether they apply to the repo Ploy manages is a question for Ploy. If you need them, ask in writing or use a mirror you control as the review point.
What does Publishing paused mean on Ploy?
Per Ploy's docs it happens when someone pushed commits straight to GitHub, so storage holds newer changes than the editor. Your edits stay safe in the preview. Ask the agent to sync from GitHub, resolve any conflict, then publish again.
Can I move a Next.js or React site to Ploy?
Ploy's docs say your own coding agent ports Next.js and Vite with React sites into its Astro starter, and compatible Astro repos import with a command. It is a rebuild, so test forms and redirects first. See moving a website to Ploy.
Can my marketer use Claude or ChatGPT instead of Ploy's own chat?
Ploy offers a connection that lets AI coding tools such as Claude Code, Codex and Cursor work with a site. See editing your Ploy site from Claude, ChatGPT or Cursor. A person should still review AI-made changes before they go live.
Can I transfer a Ploy site to another workspace?
Ploy's CLI page describes copying a site between workspaces in the same organization with CLI version 0.12.0 or newer, and says Git and deployment history do not move. Those are copies inside one organization. For a move to another organization, the FAQ (updated November 13, 2026) says Ploy support does it on request, and the new organization's plan limits then apply, so email support@ploy.ai and check seats and sites first.
More in this topic: Websites: agency billing, partners and team workflows (6 guides) →