Skip to content
← All articles

Comparisons

Best CMS for Astro (2026): 10 options for a site you edit yourself

Ten CMS options for an Astro site you edit yourself: a five-minute decision ladder, yearly prices, server upkeep and how to let an AI assistant edit content safely.

Vas 30 min read
Ask AI about this article ChatGPT Claude Perplexity .md

An Astro site can keep all its texts in plain files, and that works while you edit the site yourself. Sooner or later someone else needs to change a price or publish a post without touching the code. That is what a CMS (content management system) is for: a clear form for editing the site’s content. Astro works with many of them, and the choice is confusing.

We compared ten systems for one situation: a small site that you, or someone without technical skills, edit yourself. Below: who each one fits, what it costs per year, how much upkeep it needs, and how to let an AI assistant edit the content safely.

A word on honesty first: we sell Astro templates, and Astro now belongs to Cloudflare, which also makes one of the systems on the list (EmDash). The full list of our interests is at the end of the article.

Current as of November 13, 2026. Prices, plans and terms are taken from the vendors’ official pages on that date. They change often, so check the vendor’s site before you buy. We update this article every quarter.

In short

Your choice depends on who edits the site, how much you can pay, and how much upkeep you accept.

  • A person without technical skills edits the texts. Pages CMS, Decap, Keystatic or TinaCMS. The content stays as plain files in your repository, and you pay nobody for storing it. Start with Pages CMS: you can set it up in minutes.
  • Many authors, many languages, or linked content. Sanity (you can start on the free plan) or Contentful (much more expensive).
  • You have a developer and your own server. Strapi, Payload or WordPress. These are powerful, but you must keep the server updated all the time.
  • You want something new. EmDash from Cloudflare. It is worth watching, but the project is still too young for a first site.

Next: a five-minute decision guide, cards for all ten systems, yearly prices, and how to connect an AI assistant safely. If you edit the site yourself and are not sure you need a CMS at all, the answer is at the end, in the FAQ.

How do you choose in five minutes?

Go down the ladder from the top and stop at the first “yes”.

Decision ladder Stop at the first “yes”
  1. Do only you edit the site, alone or with an AI assistant, and no more than once a week?

    Yes You can skip the CMS: keep the content as plain files in Git, and the assistant edits the same files. Do you need a CMS at all?

  2. Will someone without technical skills edit the texts of a small site?

    Yes A file-based CMS. Start with Pages CMS; if you need drafts and approval, look at Decap. File-based CMS compared

  3. Are there many authors, several languages, or content that repeats on different pages?

    Yes A cloud CMS: Sanity (you can start on the free plan) or Contentful (much more expensive). Sanity and Contentful

  4. Do you have a developer who will keep your own server updated?

    Yes Strapi, Payload or WordPress as a headless CMS. They are powerful, but the updates and backups are on you. What the upkeep involves

  5. Do you want to try something new and accept the risks of a young project?

    Yes EmDash from Cloudflare. It is worth watching, but too young for a first site. What EmDash is

If you need an online shop with a cart and payments, a CMS for articles is the wrong tool: a ready-made shop platform is better (our assessment). If no step fits, look at the table “What other options are there?” below.

Before you choose, check five things (our assessment):

  1. Can you use the free plan on a commercial site?
  2. How many editors and which roles does the plan include?
  3. Does the system need a separate server?
  4. How do you get your data out if you want to leave?
  5. Who owns the project, and what is happening with prices?

Our opinion. A small site usually needs only the first two steps: plain files or a file-based CMS. You can add a more complex system later; it takes extra work and AI-assisted setup.

How we chose these 10 systems

We did not look for the most fashionable systems, but for the most useful ones for a person without technical skills. We used two criteria: how safely an AI assistant can work with the system (can you let it edit the site and check its changes), and how much upkeep the system needs. We also included the heavy options (Strapi, Payload, WordPress): people pick them often, and we show them as they are. Popularity is not a criterion: WordPress runs on 39.2% of all websites,[22] but almost always as plain WordPress, not together with Astro (our assessment).

The cards have two labels. “Our experience” is what we did ourselves: we have worked with four types of systems (plain files, file-based CMS, cloud, and self-hosted). “Our opinion” is an assessment based on facts, without our own work with that system. Prices are as of November 13, 2026, from the official pages, and they change, so check the vendor’s site before you buy. We update this article every quarter.

How can you edit a site without a developer?

The simplest way is an editor that works on files: a person edits pages in a clear form, and the system saves the changes to your repository by itself. The content stays as plain files, you rent nothing from a vendor, and an AI assistant edits the same files.

Our experience. What worked best for us was a CMS where the content stays as files in Git: no extra fees and no server, the editor is simple, and an AI assistant edits the same files.

In all four systems the site lives in a repository, usually on GitHub. What differs is how the editor logs in.

Pages CMS

A simple editor for GitHub repositories. Editors are invited by email, they do not need a GitHub account, and the whole setup lives in one file in your repository.[1]

  • Price: free (according to the project).
  • Downsides: GitHub only; drafts and scheduled publishing are still only planned.

Our experience. We have worked with Pages CMS most often: setup takes minutes, and the editor is clear without training. It lacks drafts and scheduled publishing.

Decap CMS

Formerly Netlify CMS. It has an editing form, a preview, and a “draft, in review, ready” workflow.[2]

  • Editor login: you need either a GitHub account with write access or a separate login service. The ready-made solution is the paid Decap Turbo.
  • Price: Decap itself is free. Turbo: Free (€0, 1 site, 1 seat) and Pro (€19 per month, 1 site, 5 seats). Check the prices on the Decap site.

Our opinion. Choose Decap if you are ready to set up a login for editors or to take Turbo; otherwise editors need access to the repository.

Keystatic

The content is plain files. It works locally, through GitHub, or through the Keystatic Cloud; the admin panel in Astro needs extra setup.[3]

  • Editor login: in GitHub mode you need a GitHub account with write access; in Keystatic Cloud you do not.
  • Price: Keystatic itself is free. In the cloud, up to 3 users are free, then “from $10 per month”; we did not confirm the billing period.

Our opinion. Keystatic is handy for its typed schema, but in GitHub mode you will have to give a non-technical person access to the repository.

TinaCMS

Files plus visual editing right on the page. There is a cloud service, TinaCloud, and a self-hosted option.[4]

  • Editor login: in TinaCloud an email is enough; the repository must be on GitHub.
  • Price: Free for 2 users; Team is $24 or $29 per project per month: the pricing page gives two numbers.
  • Security: the GitHub list of vulnerabilities has 14 entries for 2025–2026, two of them critical. We did not check how much they affect a live site.

Our opinion. TinaCloud fits if you need visual editing; check the price on the pricing page before you buy.

If you just need to start, take Pages CMS: it has the simplest setup. If you need drafts and approval, look at Decap: it has an editorial workflow.

How do you let AI edit your site safely?

An AI assistant can work with your site in two ways, and the risks are different.

Through files. This is how Pages CMS, Decap, Keystatic and TinaCMS work: the content lives in the repository, the assistant edits it as plain text, and the site build checks the result. The catch: the CMS settings also live in the repository, and the assistant can break them.

Through a service (MCP). MCP is a ready-made set of actions on a service: read entries, create them, publish them. The assistant gets an access key and acts with the rights that the key has.

Does the system have an official MCP that writes content (according to the vendors’ documentation, as of November 13, 2026):

System Official MCP that writes content
Pages CMS not found[1]
Decap not found; there is a page about working with AI assistants[2]
Keystatic not found[3]
TinaCMS planned[4]
Sanity yes[5]
Contentful yes[6]
Strapi yes; changes content, but not the data structure[7]
Payload yes, through a plugin; changes content, but not the data structure[8]
WordPress there is an MCP Adapter plugin; whether it can create posts without extra setup is not confirmed[9]
EmDash yes, built in; it also changes the data structure[10]

What can go wrong here:

  1. A key with write access changes live content directly. Limit the key’s rights: only the sections you need and no deleting (our recommendation).
  2. MCP servers can have vulnerabilities too. The official Contentful MCP server had a high-severity vulnerability (June 12, 2026); it has been fixed.[6] In Payload’s 2026 list, four entries concern MCP.[8]
  3. AI can change not only the text but also the data structure. EmDash’s MCP can change the data model, and deleting a field deletes its values.[10]

Our opinion. We advise letting the AI work in a separate branch with a preview: that way you can see every change before it goes live. With file-based CMS this is easiest: you already have branches and previews in Git and on your hosting. For cloud systems, check whether the one you chose has a test environment or a draft mode, and give the key the minimum rights.

How much does it cost per year?

The cheapest option costs $0: files in Git, Pages CMS, Decap without Turbo, or Keystatic without the cloud. Money starts where you need a ready-made login for editors, the cloud, or hosting.

Prices are taken from the official pages on November 13, 2026. The yearly figure is our calculation: monthly price × 12, without taxes, extra fees per user, or overage. Currencies differ (Decap uses euros, the others dollars), and we did not convert them.

Option Price Per year (our calculation) What you hit first
Files in Git + AI assistant $0 $0 no interface for a non-technical person
Pages CMS $0 (the project’s statement)[1] $0 GitHub only; no drafts or scheduling
Decap + Turbo Pro €19 per month[2] €228 1 site and 5 seats; without Turbo, editors need repository access
Keystatic Cloud Free up to 3 users; Pro “from $10 per month”[3] Free: $0; Pro not calculated in GitHub mode, editors need repository access
TinaCloud Team $24 or $29 per project per month[4] $288–$348 the pricing page gives two numbers
Sanity Growth, 3 editors $15 per seat per month[5] $540 the free plan has only 2 roles
Contentful Lite $300 per month[6] $3,600 the free plan is not for commercial use
Strapi Cloud Starter $35 per month[7] $420 Starter has no backups
EmDash on Cloudflare from $0 to $5 per month, then by usage[10] from $0 R2 requires a subscription
Strapi, Payload, WordPress on your own server your server and database not estimated security updates and backups

Hidden costs are not in the table (our assessment): time for updates on self-hosted systems, backups, and setting up a login for editors. If a number in the table scares you, compare it not with zero but with the hours a developer spends on updates and repairs.

How much upkeep do you take on if the CMS runs on your own server?

A lot. The admin panel and the API of such systems are open to the internet, and keeping them updated is your job. With cloud systems, the vendor looks after the security of the service, and you keep the keys and the AI assistant’s rights. The vulnerability counts below are not a ranking: some projects describe their problems in detail, others do not. We took the numbers from GitHub lists and did not check how much they affect a live site.

Strapi

An application you must host yourself: Node.js and a database.[7]

  • Price: the Community edition is free; the cloud version has no free plan and costs more.
  • Security: 9 vulnerabilities in 2025–2026, two of them critical (a data leak and an SQL injection). The admin panel and the API are public, so you need to update fast.
  • With Astro: you will have to build the connection by hand; the image code in the Astro guide does not match the Strapi 5 documentation.

Our opinion. Strapi needs a developer who will update the server. Without one, choose a cloud system or a file-based CMS.

Payload

A CMS you configure with TypeScript code. It lives inside a Next.js application.[8]

  • Owner: since 2025 the project belongs to Figma; Payload Cloud hosting is paused for new projects.
  • Security: about 55 vulnerabilities in 2026 (the number is approximate).
  • With Astro: the guide in the Astro documentation is a stub (as of October 8, 2026), so you will have to build the connection yourself.

Our opinion. Payload fits a team that already works with Next.js. For an Astro site it is a separate application that you also have to host somewhere.

WordPress as “headless”

Here WordPress works only as an editor and storage, and the Astro site takes the content through the API when it builds.[9]

  • Security, core: in 2026 there was a critical vulnerability (9.2 on the CVSS scale), fixed on September 22, 2026 in version 7.1.2. Version 7.1.4 (October 28, 2026) closed 12 more vulnerabilities, and on October 21, 2026 a separate critical PHP patch came out.
  • Security, plugins: according to Patchstack, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, 91% of them in plugins. Patchstack is a security service for WordPress, so read its numbers with that in mind.
  • What stays your concern: a server with an admin panel on the internet, core and plugin updates, backups. The Astro site itself stays static.

Our experience. WordPress was our hardest experience: most of the effort went into the editor and themes, security, and updates.

Our opinion. Choose WordPress only if you already work in it and are ready to update it all the time. We would not start a new Astro site with it.

What should you choose if you have many authors or several languages?

When there are many authors, the content repeats on different pages, or you need several languages, files usually become too little (our assessment). Then people look at cloud systems: the vendor stores the content and you do not update a server, but your data and your prices depend on one company.

Sanity

The content is stored at the vendor, and the editor is configured with code. There is an official package for Astro.[5]

  • Price: Free gives 20 seats, but only 2 roles (administrator and viewer). Growth is $15 per seat per month; it adds editor and developer roles and comments. The Free limits are hard: when they run out, the service returns an error.
  • Roles: you will most likely hit not the volume but the roles: on Free, a non-technical editor must be given the administrator role (our assessment).

Our opinion. Sanity makes sense when the site grows and there are several authors. For a small site it is too much.

Contentful

The content is also stored at the vendor. We did not find a separate integration with Astro: you use the general package.

  • Price: Free is presented as a plan “for learning and exploring”: 10 users, 2 roles, 10,000 records (the vendor’s FAQ gives other numbers, so the sources disagree).[6] According to the vendor’s help, it cannot be used commercially. The first paid plan, Lite, costs $300 per month.
  • Owner: Salesforce is buying Contentful: the deal was announced in 2026, and the amount is about $1.5 billion. We did not confirm from the primary source whether it has closed (a blog by a Contentful partner says it closed on September 1, 2026). Check the terms again before you buy.

Our opinion. Contentful suits large projects with a budget: the price from $300 per month and the unclear terms of the free plan make it an awkward start for a small business. It is on the list because it is widely used: its npm package contentful was downloaded about 1.6 million times in the week of November 6–12, 2026 (the count includes CI servers and bots).[23] But we do not recommend it for a first site.

What is EmDash, and should you use it?

EmDash is a new CMS that lives inside your Astro project, with no separate service next to it.

Disclosure. EmDash is made by Cloudflare, and Cloudflare bought Astro (the deal was announced on January 16, 2026).[11] We sell Astro templates. The full list of our interests is at the end of the article.

  • What it is: an open CMS. The content lives in a database, and it needs Astro’s server mode.[10]
  • Age: announced on April 1, 2026; the “1.0” release came on September 28, 2026; the latest version is 1.5.0 from November 11, 2026.
  • Editor: a form, drafts, scheduled publishing, roles, a media library, and a preview. It is not a visual page builder.
  • Hosting: on Cloudflare, D1 and R2 are required; R2 needs a subscription even on the free tier, and the plugin sandbox works only on the paid Workers Paid plan ($5 per month). On your own server you need a Node process that runs all the time.
  • AI: the built-in MCP reads and writes, including the data structure (see the section on AI above).
  • State: we found no published vulnerabilities on GitHub (we checked the emdash package, not the separate @emdash-cms/* packages). An independent author, after half a year of work, writes about the operational load: WordPress themes do not carry over, and imports need manual checks.
  • Exit: export to WordPress is not described in the documentation; EmDash itself does not restore a JSON backup.

Our opinion. EmDash is worth watching, but we would not take it for a first site: the project is new, it needs server mode and a database, and its maker is the owner of Astro.

What if you have WordPress now?

You have three roads, and none of them is required.

  • Keep WordPress as the editor. The Astro site takes the content from WordPress when it builds (see above). You keep the editor you know, but updates and server security are still on you.
  • Move the content out of WordPress into files. WordPress can export a WXR file: posts, pages, fields, taxonomies (categories and tags) and users.[9] Turning it into Markdown files has to be done separately; we did not check a ready-made way in this article, so we do not promise step-by-step instructions.
  • Move to a new CMS with an import. WordPress themes do not carry over in a move, and imports need manual checks: so writes an independent author in a review of EmDash.[10]

In any case, before you move, save the WXR export, the folder with uploaded images, and the list of old page addresses: you need them to set up redirects, otherwise you can lose visitors from search (our advice).

What other options are there?

These nine systems did not make the main list: each has a catch that keeps us from putting it in the top ten (our assessment). One row per system, prices as of November 13, 2026.

System What it is What to watch Price
Storyblok Cloud; a visual editor inside your site It is not confirmed whether the updated official Astro package has a content loader. For the free Starter plan the sources disagree: the pricing page says “for tests and personal projects”, while the vendor’s help allows commercial sites[12] Starter free (1 seat); Growth $99 per month
DatoCMS Cloud Free has no overage: when you reach the limit, the service is switched off until the next month. Commercial use of Free is not confirmed[13] Free: 300 records, 1 editor (elsewhere in the documentation, 2); Professional €149 per month, billed yearly
Prismic Cloud No official Astro support: the documentation names only Next.js, Nuxt and SvelteKit. We do not recommend it for Astro (our assessment)[14] Free: 1 user, 2 locales; Starter $10 per month per repository, billed yearly
Ghost A blog platform Headless mode with caveats: memberships, paid subscriptions and comments do not work without Ghost’s own frontend. The code in the Astro guide is outdated: Ghost 6 returns no more than 100 posts. About 70 vulnerabilities in 2026 (the number is approximate)[15] Ghost(Pro): Starter $18, Publisher $29 per month, billed yearly (the documentation says “from $15”: a discrepancy)
Directus On your server or in the cloud Version 12 moved to a license with restrictions: the code is available, but the terms of use are limited. Free self-hosting is under a grant for organizations with revenue up to $5 million and up to 50 staff; read the grant terms yourself. About 56 vulnerabilities in 2025–2026 (the number is approximate)[16] Cloud Core $99 per month; no free cloud plan
CloudCannon A service with a visual editor that syncs with your repository Disclosure: CloudCannon pays Astro $4,000 per month and so is the only “Featured CMS partner”.[17] Visual editing needs a developer to set up the editable regions. The service is meant for “your own internal business purposes”; for an agency’s clients you need a written agreement (this is not legal advice) No free plan, 21-day trial; Standard $55 per month (3 users)
Sveltia CMS The successor to Decap with a compatible config Beta, one developer, version 1.0 planned for the end of 2026. For GitHub you need your own login server[18] Free, commercial use allowed
Sitepins Cloud or your own install Opened on July 30, 2026, AGPL-3.0 license, no releases on GitHub, and the author admits there may be bugs[19] The site shows Pro $12 per month and a 7-day trial with a card; the documentation describes a free Hobby plan: a discrepancy
StudioCMS On your server, needs server mode Before version 1.0 (0.7.0); no releases from March 14 to September 24, 2026. 9 vulnerabilities in 2026, all about access control[20] Free

What to do next?

If your site is small, start with the simplest option: files in Git or a file-based CMS such as Pages CMS. You can also connect more complex systems, cloud ones or ones on your own server, but that takes extra work and AI-assisted setup. There is no need to rush this choice: you can add a CMS later, when the site grows.

If you want to see what such a site can be built on, take a look at the ShipThemes templates: all of them are built on Astro, and their texts are stored in Markdown and MDX files, so you can connect a file-based CMS such as Pages CMS to any of them. None of them comes with a ready Pages CMS config yet. How to adapt a template to your needs with an AI assistant, step by step, is in our guide to customizing an Astro template with Claude Code.

If you are not sure what will suit you, write to us: hello@shipthemes.com.

Read next:

Frequently asked questions

Do you need a CMS for an Astro site?

Not always. Astro can read content from plain files: Markdown, MDX, JSON, YAML.[21] If only you edit the site, or you with an AI assistant such as Claude Code, and no more than once a week, you can skip the CMS: the assistant edits the same files.

A CMS makes sense if (our opinion):

  • a person without access to the repository edits the site;
  • you need roles, drafts and approval;
  • there are many authors or languages;
  • the content is linked together and repeats in several places.

How is a headless CMS different from a file-based one?

In a headless system the content lives in a service or a database and reaches the site through an API, and the site is built separately. In a file-based CMS the content is plain files in your repository, and the CMS only edits them.

Which CMS is the simplest for a person who does not know Git?

From our list, Pages CMS: editors are invited by email, they do not need a GitHub account, and the setup lives in one file.[1] Downsides: GitHub only, no drafts or scheduling. Login without a GitHub account also exists in Decap with the paid Turbo[2] and in TinaCloud.[4]

Which CMS can you use for free on a commercial site?

The programs Pages CMS, Decap and Keystatic are themselves free and open.[1, 2, 3] Free plans of cloud services are harder: for Contentful, according to the vendor’s help, Free is not for commercial use,[6] and for Sanity, TinaCloud and Decap Turbo we did not confirm the terms of commercial use. Read the terms before you launch.

How do edits from the CMS get onto the site?

This is a general description; the exact settings depend on your hosting. In a file-based CMS, an edit is a change to a file in the repository, after which the hosting rebuilds the site. With cloud systems, the site usually takes the content when it builds, and the rebuild must be started automatically or by hand.

Can an AI assistant edit the site if a CMS is connected?

Yes, through files or through MCP. The details, and the advice to work in a separate branch with a preview, are in the section on AI above.

What if the CMS raises its price or shuts down?

Check in advance how you can take your data out. With a file-based CMS the content stays in your repository; with cloud systems you need an export; with EmDash, the project itself does not restore a JSON backup. The questions worth asking before you choose are in the section with the decision ladder.

Can you move from WordPress to Astro?

Yes. WordPress exports a WXR file with posts, pages, fields and users.[9] Turning it into Markdown has to be done separately; we did not check a step-by-step way here.

Disclosure of interests and what we did not check

Below is what you should know before you trust the list.

Interests

  • We sell Astro templates (ShipThemes), so it is in our interest that people use Astro.
  • We get no money from any CMS in this article: no payments, partnerships or affiliate links.
  • Cloudflare bought Astro (the deal was announced on January 16, 2026) and makes EmDash.[10] The Astro blog promises that the framework will stay under the MIT license and is not tied to Cloudflare;[11] the Cloudflare press release says only that it “will remain open”.[11] We found no legal governance structure (a foundation, an independent board) in the sources.
  • CloudCannon pays Astro $4,000 per month: the “Featured CMS partner” status is a sponsorship.[17]
  • Many vendors have a commercial interest in links to “alternatives”, so we read such comparisons as opinions, not as facts.

What we could not check

  • The terms of commercial use of the free plans: Sanity, DatoCMS, Prismic, TinaCloud, Decap Turbo, and the hosted Pages CMS app.
  • We did not personally open the Decap Turbo pricing page; the Keystatic Cloud pricing page did not open, and the billing period is unknown.
  • Whether the Salesforce–Contentful deal has closed: the primary source does not confirm it, and there is only a Contentful partner’s blog. The sources also give different dates for the announcement.
  • Storyblok: whether version 11 has a content loader.
  • WordPress: whether the core can create posts through MCP without extra setup.

This article is updated every quarter. Data, prices and terms were checked on November 13, 2026.

Sources

Pages read on November 13, 2026, unless an entry says otherwise. In brackets: the date on the source page, where it has one.

  1. Pages CMS documentation: overview, collaborators, self-hosting; Astro Docs: Pages CMS guide (a stub). No date given.
  2. Decap CMS documentation: introduction, backends, editorial workflow; Astro Docs: Decap guide; Decap CMS: “State of Decap” (modified Aug 24–Oct 26, 2026; Nov 4, 2026, updated Nov 5, 2026) · Decap Turbo: overview and prices; blog (GA Oct 16, 2026; updated Oct 12, 2026; we did not open the pricing page ourselves) · Decap CMS: “Working with AI assistants” and llms.txt (Nov 4, 2026)
  3. Keystatic documentation: Astro, GitHub mode, Cloud; Astro Docs: Keystatic guide. No date given.
  4. TinaCMS: documentation for Astro; Astro Docs: TinaCMS guide (updated Jul 28, 2026) · TinaCMS: FAQ (Feb 9, 2026) · TinaCMS: prices and payment terms (modified Nov 11, 2026) · GitHub: TinaCMS vulnerability list (two pages; GHSA-529f-9qwm-9628, GHSA-8pw3-9m7f-q734; by the entries: Dec 18, 2025; Mar 12, 2026) · TinaCMS: roadmap and news for May–June 2026 (Jul 7, 2026)
  5. Sanity Docs: MCP server (Nov 4, 2026) · Sanity: pricing (no date given, © 2026) · npm: @sanity/astro 3.6.2 and the Sanity plugin page (Nov 12, 2026) · Sanity Docs: plans and payments, technical limits (Nov 12, 2026; Oct 26, 2026)
  6. Contentful Docs: MCP server; blog: remote MCP, GA (Jul 21, 2026) · GitHub Advisory: GHSA-2xhg-73j7-rrgx, official Contentful MCP server (Jun 12, 2026) · Contentful: pricing (no date given, © 2026 Salesforce, Inc.) · Contentful Help: free plan (no date given, © 2026) · SEC EDGAR: Salesforce, Form 10-Q for the period ended Jul 31, 2026 (note 6, Pending Acquisitions) · The Next Web: Salesforce is buying Contentful (Jun 1, 2026) · FocusReactive: “Salesforce bought Contentful — what’s changing for customers” (a Contentful partner’s blog; the text refers to October 2026)
  7. Strapi Docs: MCP server (no date given) · Strapi: Cloud pricing; GitHub: Strapi license (no date given) · Strapi documentation: installation and deployment (no date given) · GitHub: Strapi vulnerabilities (via the GitHub API, as of Nov 13, 2026) · Strapi: blog about Astro 6 and the Strapi 5 + Astro starter (Apr 7, 2026, updated Sep 25, 2026); Astro Docs: Strapi guide
  8. Payload Docs: MCP plugin (no date given) · GitHub: Payload vulnerabilities (via the GitHub API, as of Nov 13, 2026; the number is approximate) · Payload Docs: installation; MIT license (no date given) · Payload: “Payload is joining Figma” (Jun 17, 2025), the pricing and hosting pages (Payload Cloud), blog about the Payload 4 beta (Oct 19, 2026); npm: payload · Astro Docs: Payload guide (a stub) and pull request #14678, merged Oct 8, 2026
  9. WordPress: MCP Adapter plugin and repository (no date given) · WordPress: system requirements (no date given); WordPress Developer Resources: REST API (updated Oct 14, 2026) · The Hacker News: critical WordPress patch (Sep 2026, corrected Sep 22, 2026) · WordPress News: release 7.1.4 (Oct 28, 2026) and the critical PHP patch (Oct 21, 2026) · Patchstack: “State of WordPress Security in 2026” (no date given) · WordPress Documentation: Tools Export Screen (Jun 8, 2024)
  10. EmDash documentation: overview, deployment on Cloudflare, Node.js, MCP server; GitHub: EmDash repository; Astro Docs: EmDash guide (no date given) · Cloudflare Docs: R2, Workers and Dynamic Workers pricing (Oct 2–Oct 30, 2026) · Cloudflare: blog about EmDash 1.0 (Sep 28, 2026) and the EmDash announcement (Apr 1, 2026); npm: emdash (versions and dates, latest 1.5.0 of Nov 11, 2026) · Vincent Schmalbach: review of EmDash half a year after release (an independent author; Oct 26, 2026)
  11. Astro: “Astro is joining Cloudflare” (Jan 16, 2026) · Cloudflare: blog “Astro joins Cloudflare” and press release (Jan 16, 2026)
  12. npm: @storyblok/astro 11.0.0 (Nov 6, 2026); Storyblok: documentation on the Astro SDK (Nov 10, 2026); Astro Docs: Storyblok guide; Storyblok: pricing (no date given, © 2017–2026); Storyblok Support: can you use a free account for commercial websites (no date given)
  13. DatoCMS: pricing; npm: @datocms/astro 0.7.0; DatoCMS Docs: Astro; Astro Docs: DatoCMS guide; DatoCMS Docs: exceeding API and traffic limits (no date given; Nov 10, 2026; May 6, 2026)
  14. Prismic: documentation; Prismic Community: “Creating new repositories with any framework other than Next, Nuxt, Svelte no longer works”; Astro Docs: Prismic guide; Prismic Community: “Integration with Astro.js” (a staff reply); Prismic Docs: Legacy Builder (marked as outdated); Prismic: pricing (Apr 23–24, 2026; Aug 25, 2025; Oct 1, 2026; no date given)
  15. Ghost Docs: Jamstack; Ghost Help: headless site with Ghost(Pro); Astro Docs: Ghost guide; Ghost Forum: Ghost 6.0 breaking changes and the 100-post limit; Ghost: Ghost(Pro) pricing and hosting documentation; GitHub: Ghost vulnerabilities (via the GitHub API; the number is approximate) (Dec 15, 2023; Jun 19, 2025; Oct 16, 2025; no date given; as of Nov 13, 2026)
  16. Directus: licensing overview, Open Innovation Grant, article about the license change in v12 (Apr 22, 2026); Directus: pricing; GitHub: Directus vulnerabilities (via the GitHub API, as of Nov 13, 2026; the number is approximate); Directus Docs: MCP (no date given)
  17. Astro: “CloudCannon — official CMS partner” (a $4,000 per month sponsorship; Mar 12, 2026) · Astro Docs: CloudCannon guide; CloudCannon: page about Astro and the visual editor (vendor materials; visual editor Oct 30, 2026); CloudCannon: pricing (no date given); CloudCannon: terms of use (Aug 21, 2026)
  18. Sveltia CMS documentation: introduction, GitHub backend, roadmap; GitHub: repository and Sveltia CMS vulnerabilities (no date given; May 11, 2026; Jun 18, 2026)
  19. Sitepins: pricing, documentation on plans and AI agents (Sep 14–Oct 31, 2026), repository; the author’s post on Hugo Discourse (Jul 30, 2026); Astro Docs: Sitepins guide
  20. StudioCMS: documentation and the studiocms npm package (0.7.0); Astro Docs: StudioCMS guide (a stub); GitHub: StudioCMS vulnerabilities (Oct 19, 2026; Jan 27–Sep 24, 2026)
  21. Astro Docs: Content collections (no date on the page)
  22. W3Techs: Usage statistics and market share of WordPress (data as of November 13, 2026; read November 14, 2026)
  23. npm: download counts API, package contentful, last week and the package page (November 6–12, 2026; read November 14, 2026)
All templates →

Complete Astro sites with every page designed. Open the live preview, then buy once.

From the blog

Keep reading

All articles

Ready when you are

Launch your next site this week.

Pick a template, pay once, download instantly. Every page is already designed. You bring the words.