CMS

A CMS like Framer's, for a site in code.

Collections, items and fields that work the way your team knows from Framer. The content lives in your GitHub repo as files, AI builds the pages around it, and Echo is where your team writes, translates and publishes.

For Astro sites on the Allsite CMS. Your content stays in your repo.

Items

Write and edit like you did in Framer.

Open an item and its fields are on one panel: title, slug, status, images, dates, options, references and formatted text with headings, links, lists and images. Switch the language at the top. Everything is a draft until someone with the Publish right publishes.

  • Every collection's items in a table you can sort, filter and search
  • Live and Draft per item, with required fields checked
  • Open the page an item makes, straight from the panel

Fields

The field types you know, and new ones in a click.

Add a field from the same list as Framer's: plain or formatted text, date, link, image, gallery, list, colour, toggle, number, option, file, and a reference to another collection. Give it a description, make it required, set its options.

  • Text fields get one value per language by default
  • New fields show up in the page code AI writes next
  • Fields the site uses are marked, so nobody deletes them by mistake

Translations

See what still needs translating.

Switch the CMS to German and every field still the same as the English one is marked in yellow, in the table and in the item's panel. Each language has its own settings: a fallback language, whether new content is translated or waits, and the style translations should follow.

  • Untranslated fields marked in the table and the panel
  • A fallback language for anything not translated yet
  • As many languages as your site needs, on every plan

Import

Bring your Framer CMS with you.

Export a collection from Framer's CMS as a CSV file and import it into Echo. Match each column to a field, let Echo make the ones that are missing, and see how many items are new and how many get updated before anything changes.

  • Columns matched to fields by name, and changeable
  • Missing fields made with the right type
  • New and updated items counted before you import

And the rest

The small things that make a CMS feel finished.

New collections

Add a collection from the sidebar, name it, then add its fields and items.

Language settings

Language, region, fallback, and whether new content is translated.

Field settings

Name, description, required, and the options of an option field.

Export as CSV

Any collection as a CSV file, for a spreadsheet or another tool.

Publish

Publish is one commit to your repo.

Drafts from the whole team wait in Echo. Someone with the Publish right publishes them together: one commit to your GitHub repo with their name, and the site's own Cloudflare build puts it live. Undo is a new commit, so nothing is ever lost.

  • Rights per person: Content, SEO, Publish and Admin
  • Every publish in Versions, with what changed
  • Claude, ChatGPT or Cursor can change and publish through Echo's connector, when you say so

FAQ

Questions.

Is Echo's CMS like Framer's CMS?

It's built to feel the same: collections in a sidebar, items in a table, an item's fields on one panel, the same field types and a status for drafts. The difference is where the content lives: as files in your own GitHub repo, so AI tools and developers can build pages on it.

Can I move my Framer CMS content into Echo?

Yes. Export each collection from Framer's CMS as a CSV file and import it into Echo's CMS. Echo matches the columns to fields, makes missing fields and shows how many items are new or updated. Images keep their addresses until you replace them.

Which field types does it have?

Plain text, formatted text, date, link, image, gallery, list, colour, toggle, number, option, file and reference (one or several items of another collection), plus slug and status.

How do translations work?

Text fields hold one value per language. Switch the language at the top of the CMS and every field still the same as the default language is marked in yellow. Each language has a fallback, so a page never shows an empty field.

Where is the content stored?

In your site's GitHub repo, as JSON files under src/content. Echo keeps only drafts that aren't published yet. Publish writes them to the repo as one commit.

What does the site need?

An Astro site with the Allsite CMS content format, in a GitHub repo your company owns, built by Cloudflare. Allsite Studio sets it up as part of a move from Framer, or your developer adds it.

Keep the CMS your team knows.

Start with Echo for free, or have Allsite Studio move your Framer site and its CMS to code.