For marketers whose website
lives in a developer's repository.
Your site's code is on GitHub, so every headline change is a ticket. Refinar runs it in a live preview where you change it, then publish or ask for review.
Is your site a fit?
Code in a GitHub repository
Refinar works on code in a GitHub repository, across 22 frameworks including Next.js, Astro, Vite and plain HTML. If your site is built in Webflow, WordPress, Framer or Squarespace, its pages live inside that tool, and Refinar can't open them.Not sure where the code is?
Ask whoever built the site where the code is. If the answer is a GitHub link, read on.Changing a page
01
Open the site
Your site runs in a preview in the browser, started from its own code, so what you're looking at is the real page with its real components.
02
Point at the part that's wrong
Use Select an element in the preview and click the headline, button or section, or switch to Edit text and type over the words themselves.
03
Adjust the look
Style edits cover text colour, background, font size, weight and alignment. Bigger jobs, like a new section or a whole campaign page, you describe in plain words.
04
Check it, then publish
Click through the page as a visitor would. Publishing puts the change on the site's main branch, where whatever deploys the site picks it up. Or send it for review and a developer approves it first.
A few typical requests
- Rewrite the hero headline and button
What happens: Done in the preview, published by you
Why: Words and layout are yours to change
- Add a customer-logo strip under the hero
What happens: Built as a new section
Why: A new section only adds to the page
- Build a landing page for a campaign
What happens: Built from the site's own components
Why: A new page leaves the existing ones alone
- Change the price on the pricing page
What happens: Usually held for a developer
Why: It may change what customers are charged
- Add a newsletter sign-up that emails people
What happens: The form can be built; turning on the emails waits
Why: Messages sent to real people can't be taken back
| What happens | Why | |
|---|---|---|
| Rewrite the hero headline and button | Done in the preview, published by you | Words and layout are yours to change |
| Add a customer-logo strip under the hero | Built as a new section | A new section only adds to the page |
| Build a landing page for a campaign | Built from the site's own components | A new page leaves the existing ones alone |
| Change the price on the pricing page | Usually held for a developer | It may change what customers are charged |
| Add a newsletter sign-up that emails people | The form can be built; turning on the emails waits | Messages sent to real people can't be taken back |
What stays with a developer
Charging, sign-in and deleting data
The agent won't change what customers are charged, who can sign in or what data gets deleted, even when the change looks like one line on a page. It also stops before switching on anything that sends messages or calls another service by itself. The words and layout of those pages are still yours: a checkout page can be restyled while its logic waits for a developer.Text that lives in your app's data
Some text comes from the app's data rather than its code, such as posts from a CMS. Refinar marks that text as living in your app's data, and it's changed wherever that content is normally edited.Questions marketers ask
Does it work with WordPress or Webflow?
No. Refinar needs the site's code in a GitHub repository, and sites built in those tools keep their pages inside the tool.
Can the agent be kept to marketing pages?
Yes. An owner or admin can write Rules for the AI on each app, such as "only update text and images on the marketing pages", and the agent hands anything outside them back to the team. They can also require approval before anything goes live.
What if I break something?
Changes are made on a copy and can be rewound until they're published. Publishing writes to the main branch, so if the site deploys automatically, that's when it goes live. After that, a mistake is reversed on GitHub like any other change.
Can the rest of the team use it?
Yes. Plans include 20 teammates, and nobody but the person who connects the site needs a GitHub account (pricing).
Product details are from Refinar's app and documentation, checked on 7 October 2026. More on the marketing side in how marketing teams update a website without developers and Claude Code for marketers.