A Framer CMS alternative your marketing team can actually use.
Echo's Website tab gives a code site a CMS that works like Framer's: collections, items, fields, drafts and Publish, edited by the marketing team in a visual interface. The difference is where the content lives: in your own GitHub repository as files, not in a vendor's database, so it's yours whatever tool you use next.
In short
- Astro and other code frameworks have no editor of their own, so a marketing team needs a CMS on top.
- Headless CMSs like Sanity, Storyblok and Contentful are strong, but they add a second service and a developer to wire it up.
- Markdown files in Git are free and simple, but most marketers won't edit a site that way.
- Echo edits content files in your repository with a visual CMS, so content stays yours and the team works the way it did in Framer.
What does the team keep from Framer's CMS?
The parts they used every day, in one place.
- Collections and items
- Blog posts, case studies, jobs, team, changelog: each a collection with its own fields, each item with its own page.
- Fields
- Text, long text, formatted text, images and files, and a draft or live status, in every language the site has.
- Drafts and Publish
- Every change is a draft until someone with the Publish right makes it live. Publish is one commit, and Undo puts it back.
- Per-page SEO
- Titles, descriptions and social images for every page and CMS item.
- Edit on the page
- Signed in with Echo, a team member edits a page's text on the live site with a pencil.
What are the options for a CMS on a code site?
Each is right for someone.
There are three common ways to give a code site a CMS. Here's how they compare for a marketing team that's used to Framer.
- A headless CMS
- Sanity, Storyblok, Contentful and others. Powerful and well documented. Content lives in their database, it's another service and bill, and a developer connects it to the site.
- Markdown in Git
- Free, fast and fully owned. Fine for a developer's blog; most marketers won't edit files in a code editor.
- Echo's Website tab
- A visual CMS over content files in your own repo. Owned like Markdown, edited like Framer, and in the same place your team watches AI visibility.
Why keep content in your own repository?
Content in the repository is versioned with the code: every change has an author, a date and a way back. AI tools read and write it directly, so a prompt can draft an article or translate a page. And nothing is locked in: if you stop using Echo, the content is still there as files and the site stays online.
What else does the CMS do inside Echo?
Echo is an AI visibility platform, so the CMS sits next to what tells you what to write. When Echo finds a page AI answers misquote, Fix this puts the correction into the right CMS field as a draft. Content briefs and drafts go to the CMS as draft items. Sitemap, AI crawlers and the pages AI cites are a click away.
What do you need to run a code site from Echo?
Plainly, before you plan anything.
Echo's Website tab edits sites built on the Allsite CMS, an open content layer for Astro sites. Your content lives in your own repository as files, and Echo is the screen your team uses to change it.
- A GitHub repository
- Owned by your company. The site's code and content live there, with the full history of every change.
- An Astro site with the Allsite CMS
- Set up by Allsite Studio, Echo's design team, or by Echo's team with your developer. Echo doesn't convert a Framer project by itself.
- A host that builds from the repo
- Cloudflare is what we use and recommend. Every Publish in Echo is one commit, and the host deploys it.
- An Echo plan
- Editing in Echo needs an active plan. If it ends, editing stops and the site stays online, because it's yours.
More guides
Moving from Framer to code.
- Migration guideA step-by-step guide to moving a Framer site to Astro: rebuild the pages with AI, move the CMS into your repo, keep every URL and run it from a visual CMS.Read the guide
- Export a Framer siteFramer has no built-in export of a published site to a code project. What export plugins give you, what they leave out, and the better way to get a code site.Read the guide
- Framer to AstroMoving from Framer to code? Astro suits marketing sites: fast pages, content as files, JavaScript only where needed. When Next.js is the better pick, and why.Read the guide
- Framer vs custom codeWhen Framer is still the right website builder and when a custom-code site run from a visual CMS fits better: control, cost as you grow, SEO and AI search, and editing.Read the guide
On the blog
Read more.
- Framer vs custom code: which website stack AI search reads bestYour website stack decides how much control you have over the HTML, schema and crawler rules AI search reads. Framer and custom code, compared.Read the article
- How to leave Framer without losing your Google rankings or AI citationsMoving from Framer to a code site? Keep your URLs, redirect the rest, carry over metadata and structured data, and check what AI answers cite before and after.Read the article
- The Framer migration checklist: what to list before you leaveBefore you move a Framer site to custom code, list every page, CMS collection, form, script, integration and owner. A checklist that turns a guess into a plan.Read the article
- How a marketing team runs an AI-built website without a developerAI builds the pages, a visual CMS handles content, approvals keep it safe. Who does what on a custom-code website after Framer, and the rules that keep it on brand.Read the article
FAQ
Questions.
What's the best CMS for an Astro site?
It depends on who edits. A developer-run site does well with Markdown in Git. A team that wants a separate content platform picks a headless CMS like Sanity or Storyblok. A marketing team that wants Framer's way of working with content in its own repo can use Echo's Website tab with the Allsite CMS.
Can I move my Framer CMS collections?
Yes. Export each collection as CSV from Framer; each item becomes a content file in your repository with the same slug and fields, so URLs stay the same.
Is Echo a headless CMS?
Not in the usual sense. It doesn't store your content in its own database. It edits the content files in your repository and commits each Publish there.
What happens to the content if we cancel Echo?
Nothing. It's in your repository, and the site stays online. Only editing through Echo stops.
Keep Framer's CMS, own the content.
See how the move from Framer works, or have Allsite Studio set it up.