Astro Visual Editor: Give Non Technical Users Edit Access

  • Farhad
  • September 20, 2026
Astro Visual Editor: Give Non-Technical Users Edit Access

Astro ships bare-bones. There’s no admin panel, no login screen, and definitely no editor UI. Your content just sits there as Markdown files in src/content/. Want to change a word? You open the code repo.

So how can you enable others to edit your Astro site?

To be fair, there’s a fix. Connect your repository to an Astro visual editor like Sitepins. Setup takes about 10 minutes, and you won’t touch a single line of code… Point it at your src/content/ folder, invite your editor by email, and they’re in. They work in a form-based interface, believe it or not, so they never see Markdown or Git. Every save becomes a commit in your repository, which triggers your existing Vercel or Netlify deploy.

Look, here’s what we wish someone had said earlier. This tutorial covers the complete setup for Astro sites. It also covers the exact editor experience your non-technical user will have once it’s live.

TL;DR, Key Takeaways

  • Astro sites built with Content Collections work out of the box. No astro.config.mjs changes required
  • Editors see a clean form interface, not code or file trees
  • Every save becomes a Git commit, so your deploy pipeline triggers automatically
  • Editors don’t need a GitHub account
  • 34% of Sitepins users build on Astro, so the CMS is purpose-tested against Astro’s content model
  • Setup takes 10 to 15 minutes. Editor onboarding takes under 5

What Is an Astro Visual Editor?

In plain English, an Astro visual editor gives your content team a dedicated web interface to create, edit, and publish content. They just hit a URL. We get why this trips people up: not your codebase. No Markdown files, frontmatter syntax, or Git in sight.

Under the hood, the editor writes straight to your existing files. It touches the same .md and .mdx files in src/content/ that you use as a developer, and the difference is purely presentation because you open a .md file in VS Code and edit raw text while your editor opens a form with labelled fields (Title, Date, Body, Featured Image) and a rich text toolbar.

The body field is a WYSIWYG editor. Make sense? Text appears close to how it will publish. So an Astro WYSIWYG editor removes the gap between writing and previewing.

When they save, the CMS commits the updated file to your GitHub or GitLab repository. It looks identical to a commit you made yourself, and the file changes are in Git history, reversible, and auditable.

What it’s not: An Astro visual editor isn’t a page builder, drag-and-drop layout tool, or site redesign interface. It manages content: words, images, metadata. This is the part that frustrates people. It doesn’t manage design or code structure. If you are searching for a visual builder for Astro and expecting a layout canvas, this is a different category of tool.

Why Non-Technical Editors Struggle with Astro by Default

Astro is built for developers, and its content layer is a great fit for them because it’s powerful and predictable. The setup relies on Content Collections, frontmatter schemas defined in src/content/config.ts, and Markdown and MDX files. But for non-technical editors, this specific structure creates three major headaches.

1. No editing interface ships with Astro.

Now, here’s where it gets interesting. Astro doesn’t come with a built-in CMS panel or any kind of admin UI. If you hand a non-technical user access to a GitHub repository, they’re staring at a file tree, not an editorial interface… They simply cannot edit content without a solid grasp of Git, Markdown syntax, and how the files are organized.

2. Frontmatter syntax is fragile for non-developers.

You know, here is what a content entry in Astro actually looks like:

---
title: "How We Built Our Product"
date: 2026-03-15
description: "A case study about our build process."
image: "/images/product-build.jpg"
draft: false
tags: ["product", "engineering"]
---

Body content starts here...

Basically, a non-technical editor making a direct edit to this file on GitHub can easily break the frontmatter syntax with just one small mistake. Frankly, a missing quote, a misformated date, or a stray character causes a build failure. The editor sees nothing happen, you see, but the entire site deploy breaks…

3. Publishing requires understanding Git.

Even if an editor manages to successfully edit a file in GitHub’s web interface, they still need more context to move forward… They need to understand what “commit to main” means and what a pull request is, for starters. They also need to know why their changes may not appear immediately on a branch.

In plain English, a dedicated CMS layer removes all three problems.

Getting Ready: What You Actually Need

  • Your Astro site needs content in src/content/ using Content Collections, or just plain .md files in src/pages/
  • Host the site on GitHub (works on all plans) or GitLab (requires Team plan or higher)
  • Private repositories are supported on every plan
  • A Sitepins account, which you can start at sitepins.com
  • Your Astro site already deployed on Vercel, Netlify, or Cloudflare Pages (optional, but required for the automatic deploy pipeline)
  • Your editor’s email address

You do not need to install any npm packages, modify your astro.config.mjs, or make any changes to your repository before starting.

Hooking Sitepins Up to Your Astro Site

Step 1: Create a project in Sitepins

Go to app.sitepins.com and hit New Project. So what does that involve? The platform asks which Git provider you’re using, so pick GitHub, or select GitLab if you’re on the Team plan or higher, then authorize the OAuth connection. A searchable list of your repositories will appear right away.

Here’s the thing: pick the repo holding your Astro site and click Continue.

Sitepins looks at your repository’s file structure during this step. It doesn’t commit anything to your repo during setup.

Step 2: Select your content folder

You will see the directory tree for your repository! Navigate to the folder that holds your actual content files.

But wait, there’s more to consider. For a typical Astro Content Collections project:

  • Pick src/content/blog/ to limit editor access to blog posts only
  • Select src/content/ to expose every collection (blog, docs, authors, etc.)

Hit Confirm… The tool scans the folder, finds your .md and .mdx files, and lists them as editable entries.

Handling multiple content types: You can add several folders as separate sections. Interestingly, editors see these as labelled groups in the sidebar (like Blog, Docs, or Authors) and can switch between them instantly.

Step 3: Confirm your content schema

This is where most people get confused, so let’s clear it up. Sitepins reads the frontmatter fields in your existing content files and builds the editing form for you automatically. There’s no need to define a separate CMS schema.

Verify that the detected fields match your expectations:

  • title becomes a single-line text field
  • date becomes a date picker
  • description becomes a multi-line text area
  • image becomes a media picker with upload support
  • tags becomes a tag-adding widget
  • draft becomes a toggle switch

If you have a Zod schema in src/content/config.ts, required fields will appear in every entry’s form and can’t be saved empty. Optional fields will show up but can be left blank.

Step 4: Pick your media folder

You might be wondering about this, and that’s fair. Decide where uploaded images actually land. Astro projects usually go with one of these:

  • public/images/ serves straight to /images/ on the live site. This works if you reference images by URL in your frontmatter
  • src/assets/ gets processed through Astro’s built-in image optimisation. Use this when you import images inside components

Once an editor uploads a file, Sitepins commits it to that folder and drops the correct path into the content field for you. Everything lives in your repo. There’s no external CDN or third-party asset service in the mix.

Step 5: Get your editor in

Head to Settings → Team → Invite member inside your Sitepins project… Type in your editor’s email and give them the Editor role. Why does this matter? This lets them create, edit, and delete content entries! They won’t see project settings, repo config, or billing.

Hit Send invite. I mean, your editor gets an email with a setup link. They set a password and jump right into the editor… Surprisingly, no GitHub or GitLab account needed.

You’re all set.

What Your Editor Sees and How They Work

The editor’s world is completely separate from your development workflow. Honestly, this is exactly what they’ll be looking at.

sitepins-dashboard-overview

The content list

Right after logging in, they see a clean sidebar listing their content sections like Blog or Docs. Clicking one of those sections shows every entry with titles, publish dates, and draft status, and they can filter by status or sort by date if they need to.

No file tree.

No raw Markdown.

No Git interface.

Opening and editing a post

Clicking an entry pops open the editing view. The frontmatter fields show up as a structured form on the left, or at the top if they’re on a smaller screen. Here’s something most people don’t realize: the body content sits in a rich text editor.

sitepins-single-post-editor-preview

Think of the body editor as a simplified word processor:

  • Visual mode: You get a toolbar with bold, italic, headings from H1 to H4, links, ordered and unordered lists, blockquotes, inline code, code blocks, and image insertion, so you don’t need to know a single bit of Markdown to get work done.
  • Markdown mode: Raw Markdown for editors who actually prefer it, and both modes stay in sync so switching between them keeps all the content intact.

Adding images

The editor clicks the image icon in the toolbar or the image field in the frontmatter form… A media panel opens showing any previously uploaded images, (and this matters) and they can drag in a new file or click to browse. Sitepins handles the upload, the Git commit, and the path insertion without you or any developer having to lift a finger.

Saving and publishing

When the editor hits Save, Sitepins commits the changed file to your repository’s default branch, whether that’s main or master. This might sound obvious, but there’s no separate “publish” step visible to them. Save means the content goes live as soon as your deploy pipeline finishes, which is typically 1 to 2 minutes on Vercel and 1 to 3 minutes on Netlify!

They see a success confirmation with a note that the site is updating. No deploy logs, no build output, no technical feedback to confuse them.

Creating new posts

So, the editor just clicks New Entry in the content section. A blank form pops up, showing every frontmatter field from your schema..! They type in the details, write the body copy, and hit save. Sitepins then generates the actual .md file in your src/content/blog/ folder, or wherever you’ve told it to look.

It pulls the filename straight from the entry title.

How Edits Actually Reach Your Code

Whenever someone hits save, Sitepins generates a standard Git commit! To your developers, it looks exactly like any other routine content change they might make.

Here’s the full breakdown:

  1. Editor clicks Save in Sitepins
  2. Sitepins creates a commit: Update: "Post title" on your main branch
  3. The commit shows up in your GitHub or GitLab history with the changed .md file
  4. Vercel, Netlify, or Cloudflare Pages spots the push and starts a build
  5. astro build runs, pushing your new content out to the CDN
  6. The live site updates, usually within 1 to 3 minutes

Back on your local machine, just run git pull and the changes appear in your working directory as regular files in src/content/. They’re the same files you would write by hand. Sound familiar? No proprietary formats. No weird CMS metadata tacked on.

Your Git history stays tidy. Sitepins labels its commits clearly. Want to undo a specific change? Just git revert that one editor commit. Need to know who changed what? git blame the file and see the full history.

Adding a Review Step with Branches

Out of the box, Sitepins writes straight to your main branch, so whatever an editor saves goes live immediately. If your process needs a check before publishing, and this matters, you can hook up a staging branch!

Setting up the review workflow:

  1. Create a staging branch in your GitHub repository
  2. Head to Sitepins Settings → Project → Branch and switch the target from main to staging
  3. Editors save to staging now. Nothing hits production until you or they merge that branch.

When an editor is ready to go live, Sitepins lets them open a pull request from staging to main right from the CMS interface. Funny enough, they don’t need to know GitHub.

Look, you look at the PR, merge it when you’re happy, and Vercel or Netlify picks up the merge to deploy the production build.

This works well for:

  • Teams where a developer or manager checks content before it goes public
  • Sites where a mistake is expensive, like legal or compliance review
  • Multi-author setups needing a centralised review step

Frequently Asked Questions

Which Git-based CMS work best for Astro websites?

You’ve got some strong contenders for Astro, including Sitepins, TinaCMS, CloudCannon, Keystatic, and Decap CMS. Both Sitepins and TinaCMS offer visual editing right out of the gate, but Sitepins plugs into native Astro Content Collections without any configuration, so you skip the setup headaches entirely.

How can non-technical editors update an Astro site without touching code or Git?

Give them a Git-backed visual CMS like Sitepins. They get a clean interface where every change writes straight back to your GitHub repo as standard Markdown or MDX commits. Developers stay in Git, content managers stay in the web UI! No terminal commands required.

How can I enable others to edit my Astro site?

Hook your Astro repo up to a visual editor like Sitepins. Point it at your src/content/ folder, invite your editor by email, and they’re in. The encouraging bit is that they see a form-based interface and never have to look at Git or Markdown syntax. Every save commits to your repository and kicks off your existing deploy pipeline.

Setup takes about 10 minutes, and you don’t change a thing in your Astro project.

Does adding Sitepins require any changes to my Astro project?

No. You don’t touch astro.config.mjs, install npm packages, alter your content collection configuration, or add files to your repo. What does this mean for you? Sitepins connects externally through your Git provider’s API to read and write your existing Markdown files. Your project structure stays exactly the same.

Can Sitepins work with Astro’s Content Collections schema defined in config.ts?

Yes. Sitepins reads your frontmatter fields and shows them in the editing form! Fields marked required in your Zod schema show up as mandatory form fields that you can’t save empty, while optional fields appear too but you can leave them blank. Sitepins doesn’t read the src/content/config.ts file directly; it infers field types from your existing content.

If you need precise schema mapping, you can manually configure field types in Sitepins project settings…

What happens to my Astro site’s content if I stop using Sitepins?

Nothing changes. All your files stay right where they were in src/content/, still plain Markdown or MDX, and your repo keeps every commit you ever made. Stopping Sitepins just pulls the editor out of the picture, and that’s it. Your Git history, your build pipeline, everything else stays exactly the same.

Do editors need to know Markdown or Git?

Nope. The visual editor handles headings, lists, links, images, bold, italic, and code without you ever typing a single Markdown character. If someone prefers raw Markdown they can flip to raw mode, but most folks never see a Git command. Git lives completely behind the scenes.

Can I use Sitepins with an Astro site deployed on Vercel?

Absolutely. Sitepins talks to the same Git repo that Vercel watches, so when you hit save Sitepins pushes a commit and Vercel kicks off a build automatically via the standard GitHub webhook… There’s no extra step you have to add, and it works out of the box.

What if my Astro site has content outside src/content/?

If you keep plain .md files in src/pages/ (or any other folder) without using Content Collections, Sitepins works just the same, you just point it at that folder. You can even add several content directories and treat each as its own section inside the same Sitepins project. Easy as that.

Can multiple editors work on the same Astro site?

Yes. Pro opens the door for three users per organization across three roles, and Team or Agency bumps that up to five users per organization… Every editor logs in with their own account, and if two people open the same entry at once the second one gets a lock notice so they know it’s being edited already.

What does it cost?

Plans start with a 7-day free trial on Sitepins Cloud, and self-hosting is free and open source. Here’s the breakdown:

  • Pro, $12/month ($10/month if you pay yearly). You get 6 sites, 2 organizations, 3 users per org, and 3 roles.
  • Team, $29/month ($24/month if you pay yearly). This bumps you up to 15 sites, 5 organizations, 5 users per org, and adds GitLab support.
  • Agency, $49/month ($40/month if you pay yearly). Good for larger setups with 30 sites, 10 organizations, and 5 users per org.

Prefer to pay once? Lifetime licenses are available for $249 for Pro, $519 for Team, and $729 for Agency. Every new account gets a 7-day Pro trial. No credit card required.

Try Sitepins free. Give your Astro site a visual editor in 10 minutes. Start your free trial

Share this story :

Get Started with Sitepins