How to Update a Code-Based Website Without Waiting on Developers
Why changes to a Next.js or Astro marketing site get stuck in the dev queue, and four ways marketing teams can ship them every week without breaking things.
Key takeaways
- Most website changes wait because nobody owns the site between launches. The changes themselves are usually small.
- Sort every request into content, page or code changes. Each lane has a different fastest path.
- Pull requests with previews let marketing ship while engineering keeps control of the repo.
- A weekly rhythm with one priority list and one review slot beats a stream of tickets.
- Track lead time: the days from “we should change this” to live.
On this page
Your marketing site is built in Next.js or Astro. It loads fast, it looks exactly like the brand, and every small change to it waits for a developer. The FAQ you wanted on the pricing page has been in the backlog since the last launch.
The short answer: you can ship most website changes every week without waiting, as long as you split requests by type, give each type its own path to production and keep a person approving every change. Here is how teams set that up.
Why website changes get stuck
Code-based sites are great for performance and design control. The cost shows up after launch. Every change, even a sentence, becomes a code change, and code changes go through the engineering queue.
That queue is full of product work. A marketing request competes with a customer bug and loses, every time. So the request waits for “next sprint”, and then for the one after.
What’s usually missing is an owner. Nobody’s job is to run the website week to week, so changes only happen when someone has spare time.
Sort every request into one of three lanes
Before you change your process, look at your last 20 website requests. Almost all of them fall into three lanes:
| Lane | Typical requests | Fastest path |
|---|---|---|
| Content | Copy edits, new blog posts, FAQ entries, team photos | Markdown files or a CMS, published by marketing |
| Pages | Landing pages, new sections, pricing changes | A pull request built from existing components, approved in a preview |
| Code | Tracking, integrations, performance, new components | Engineering, planned like any other ticket |
Most teams find that content and page changes make up the bulk of the backlog. Those are the ones that should never wait on a sprint.
Option 1: Move content into Markdown or a CMS
If your blog posts and legal pages live in Markdown files, marketing can already edit them in GitHub’s web editor. That covers more than people expect.
For pages edited by many people every week, a headless CMS adds a friendlier editor. It also adds a second system to maintain, and it only helps with the content lane. A CMS will not build you a new landing page.
Option 2: Give marketing a pull-request workflow
This is the change with the biggest payoff. Instead of filing a ticket, someone on the marketing side opens a pull request:
- The change is made on a branch, using the site’s existing components.
- The hosting platform (Vercel, Netlify, Cloudflare) builds a preview link.
- Marketing reviews the preview on desktop and mobile.
- A person with merge rights approves it, and it goes live.
Engineering keeps every guardrail it has today: branch protection, checks, code review. What changes is who starts the work. If you want to go further, read what to check before an AI agent gets repo access.
Option 3: Book a weekly website slot with engineering
If marketing can’t make code changes yet, protect a small, fixed slot instead. Two hours every Thursday, one engineer, one prioritized list from marketing. Whatever is at the top gets done.
It sounds small. Over a quarter that is 26 hours of focused website work, which is more than many marketing sites get in a year.
Option 4: Let AI agents draft the change
AI agents can now read a repo, make a change with your components and open a pull request with a preview. That turns “please add an FAQ to the pricing page” into a reviewable change in minutes.
The rule that makes this safe is simple: the agent proposes, a person approves. Nothing merges on its own. We wrote a longer guide on what an AI website agent is and where it needs a human.
How to measure if it’s working
Pick one number: lead time, the days from “we should change this” to the change being live. Log it for every request for a month.
- Content changes should take hours.
- Page changes should take days.
- Code changes can take a sprint.
If content and page changes still take weeks, one of the lanes is broken. Fix that lane first, then run a monthly website maintenance checklist so small issues don’t pile up again.
This is the problem Centipage was built for: agents that turn your website backlog into approved pull requests every week. You can see how it works on the homepage.
Frequently asked questions
Can marketers edit a Next.js or Astro site without coding?
Yes, for text and images that live in a headless CMS or in Markdown files. New sections, layouts and tracking changes still touch code, so someone (a developer or an AI agent) writes the change and a person approves it through a pull request with a preview.
Is it safe to let non-developers open pull requests?
Yes, as long as branch protection stays on. Every pull request builds a preview and runs the same checks as any other change, and only people with merge rights can put it live.
How long should a small website change take?
Copy fixes and new FAQ entries should be live the same day, and a new landing page within a week. If a one-line change regularly takes longer than a week, look at the process before the code.
Do we need a CMS for a code-based marketing site?
Not always. A CMS helps when many people edit text every week. If most of your requests are new sections, page changes and experiments, a pull-request workflow with previews gets you further than a CMS does.
Keep reading
All resources-
Core Web Vitals for Marketers: What to Fix First
LCP, INP and CLS in plain words: what each one measures, the thresholds Google uses, and the fixes that usually move a marketing site from red to green.
-
Website Maintenance Checklist for B2B SaaS Teams
A weekly, monthly and quarterly maintenance checklist for SaaS marketing sites: forms, speed, SEO, broken links, analytics and content that has gone stale.
-
AI Search Optimization: How to Get Cited by ChatGPT and Perplexity
What AI search engines look for when they pick sources, and the practical changes that make a SaaS website more likely to be cited in their answers.
Your website, 1% better every day.
Centipage’s agents find what to improve on your site, make the change and wait for your approval before it goes live.