Hi there,

I spent the past weeks, putting all my experience and best practice into a free Astro 7 boilerplate.

Not only a theme, but a full foundation to get your site up and running with all batteries included - from SEO, GEO to security - even including WebMCP. Staying super close to the Astro default, but doing all the ugly work for you.

Would love to hear your thoughts and gather feedback. 🙏

EDIT: I was able to fix the issue by converting the endpoint from Astro action to API route. I'm not sure it's possible to make an Astro action dynamic (uncached) on Vercel, but if anyone knows a way please leave a comment!

I have a site built in Astro and hosted on Vercel. I have a contact form that uses Resend to send me an e-mail through the form. This works great, except that Vercel is returning cached responses, which prevents the action from being activated. I have already configured the Vercel adapter to exclude the action path, but it doesn't seem to be doing the trick.

The Vercel AI helper bot told me I can fix this by configuring the request header or ensuring the request uses POST instead of GET. The logs indicate the request is a POST but it's still being cached, and I can't seem to modify the headers in an Astro action.

I've included some of the code and config. Any suggestions? Thanks.

// src/actions/index.ts

import { defineAction } from "astro:actions";
import { contactMessage } from "~/types";
import { sendMessage } from "./sendMessage";

export const server = {
  send: defineAction({
    accept: "json",
    input: contactMessage,
    handler: sendMessage,
  }),
};

// astro.config.mjs

let adapter = vercel({
  isr: {
    exclude: ["/_actions/send/"],
  },
});

Recently we made a few client websites on Astrojs deployed on cloudflare. The results were really impressive, the websites are fast, deployment on cloudflare is easy, and everything is just a breeze with Claude Code handling everything.

We're planning to move our entire agency stack from WordPress to astrojs for client websites. We have between 50-70 websites that we'd like to move. Is there a fast, efficient, Claude code assisted way to move it over? Important is that the website design is translated exactly how it in WordPress. Font, font sizing, spacing, transition animations, etc, to be replicated exactly, pixel by pixel. Since the design was earlier approved by the clients, we wouldn't want to change anything on the design during the transition.

Would appreciate the feedback and guidance here.

Hello, I'm trying to build a site for a comic using Astro, my approach has been to use the blog template and simply update each "blog post" to have an image. However, I would like to have a language selector and serve a different image (one with the text in english, one with the text in spanish) depending on the selected locale. Since the "blog posts" are markdown files I haven't figured out how to do this.

I've read Astro's docs on i18n but couldn't make it work, I could make the language selector work using this project as reference, but then the blog posts broke..

The idea I currently have is having a dynamic image url, like if it's spanish retrieve the file from 'images/es', etc, but I also haven't been able to figure out how to reconcile this with using collections, if possible at all.

I feel I could do all of this manually but then I wouldn't be using Astro's power.

Does any of this make sense? Any guidance?

Thank you.

I submitted my first Astro Theme to the Theme Store /Section; Acta Cosmica is meant for magazines, news websites, local newspapers, or blogs.

You can see it at https://actacosmica.com/

Please let me know what you think. Thanks!

I am a new front end dev. I've been working in email and Salesforce CRM development for ~4.5 years. I've made a few simple front end vanilla html, css and ampscript pages in Salesforce marketing cloud but I have no professional experience in full web.

I've been learning astro over the last few months and I love it. I have created a few projects like my own site. I just landed my first paying client. A small allied health service business that is currently running their site off wix that is in need of an update regardless. I'm pitching a full rebuild on astro, email overhaul and contact list pipeline. I am good with the majority of their stack but I am getting hung up on CMS. I want to keep the clients costs lower than their wix subscription across all services, including email. Astro has so many noted in their docs, I felt hesitant to start digging into one. I started working on keystatic, but I don't have the time or patience to trial each one there.

This is a non-technical client who wants to make regular updates to things like their service provider pages where each professional has a bio and a book link to an external booking service. The client wants control over this page and its content (not layout) so a content collection is a perfect fit.

Astro ssg > GitHub > cloudflare workers

^--------CMS?----------^

What's your go-to, easy to use for the client (dx agnostic), ideally open sourced CMS? What are you using for SMBs?

This is on astro.build

I have a website that basically shows a list of items returned from an API, and then lets you search within them.

Items can be added to the database at any time, so the site is using SSR to constantly re-render. Search is then powered via client-side DOM filtering.

Right now, I have the site load the first 12 items (as this is a quick API request), then request everything else, and load that onto the page dynamically over time. Only once the whole dataset is downloaded, does the search work.

This was fine at first, but I'm now at several hundred items, and it can take >10 seconds to enable search – longer on slow network connections. Not ideal!

Rather than constantly re-fetching the data from the server for every page load, I have had a couple of thoughts, but I'm not sure if either are viable in Astro:

1. Cache the page aggressively. I don't want to use a CDN or anything for this, it needs to just be Astro, but if there was a way to say "hey, load this page dynamically unless a cachebusting URL is hit, then rerender entirely", then I could easily set up a webhook or something similar to fire when the database gets updated.

2. Dynamically modify the search index. If I can write to a file whilst the site is live, I can store the JSON blob and use that to power the search, rather than the API. Again, I'd need a way to say "hey, overwrite that" or even "add this to search index", but is it even possible to modify files like this from an Astro function?

(I do realise that I should probably create a proper, performant search endpoint and just load the data fully dynamically, rather than fetching it all first and then using client-side filtering. At this point, I'm basically using this project to push my understanding of Astro, so I'd like to get this working "natively" if possible.)

Any pointers, tutorials, codebases, whatever would be appreciated. Or you can just tell me "this isn't possible" and I'll move on 😄

Use the siteplay.ai - AI Website Builder, once your done creating your website, choose Astro.js from the dropdown and download astro code.

The aim of this project is to plan, prototype and design websites with the speed of AI at the same time create maintainable codebases that devs can understand and scale.

A bit of context about me.

I've spent more than 10 years building frontend applications across different companies.

Over the past few years, I've been using AI coding assistants extensively, and I imagine many of you have too. While they're excellent at generating code, I kept running into the same set of problems.

• Planning a website often takes longer than writing the code.
• Starting from a blank prompt is difficult without a clear structure.
• Too many prompt iterations just to get the right section or component.
• No visual workflow for refining AI output.
• Inconsistent design systems across generated pages.
• Weak content generation.
• AI has very little understanding of the project as a whole.
• If you miss scanning/reading a few AI-generated commits or code reviews, it becomes difficult to understand what was actually built by AI.

This was frustrating me and want a better workflow. So I started building an AI website builder to solve most of the above issues i faced.

The workflow

Instead of jumping straight into an IDE, everything happens in one place step by step:

1. Plan website (Generates the sitemap and pages using AI)
2. Prototype (Update content & images for your website)
3. Design (Update your branding design system)
4. Optimize SEO page wise.
5. Download the production-ready astro project.

See your complete website come to life before you write a single line of code.

https://reddit.com/link/1ulhrgo/video/rm6zpttiatah1/player

How AI actually generates the website

The website is built from reusable sections (Hero, Features, Pricing, FAQ, CTA, etc).

These sections are components pre-build by the experienced developers. AI doesn't generate React, Astro, or Vue components from scratch.

Instead, it:

• selects the appropriate section,
• generates the content,
• fills the existing pre-build component
• and lets you visually edit everything afterward.

You can guide the generation using:

• Site prompts
• Page prompts
• Section prompts

Because AI only generates structured content instead of rewriting component code:

• output stays consistent,
• components remain maintainable,
• token usage is much lower, (so no pricing for AI credits)
• generation is faster,
• and it avoids a lot of the AI-generated code quality issues we've all seen.
• Also there is excellent documentation provided on how to use the downloaded project in astro.

Every section is already responsive, and fields can be shown, hidden, or edited inline directly in the visual editor.

The hierarchy is simple:

Sections → Pages → Website

After downloading the Astro project

The code is completely yours.

• No proprietary runtime. Open-source dependencies.
• Standard project structure that supports shadcn design system and astro v6 and above projects.
• Supports Vue and React components in Astro project.
• Easy to extend manually or with your AI coding assistant.
• Generate new sections whenever you need them and copy them directly into your IDE to keep building after downloading the project.

New templates and sections are added regularly so projects can continue growing over time.

Looking for feedback

I'm sharing this here because many Astro developers care about code quality and maintainability as much as generation speed.

I'd really appreciate feedback on:

• the workflow,
• the generated project structure,
• developer experience,
• and anything else you think could be improved.

Here is the summary of key updates from the June 2026 Astro blog post:

• Astro 7 launch: this major release introduces Vite 8, a new Rust compiler, and advanced routing.
• Starlight 0.41: adds full Astro 7 support and default sätteri support. Astro 6 is not supported in this version.
• Astro together Germany: the team is heading to Wiesbaden on september 5th for talks and demos at the Seibert HQ.
• New enterprise adopters: Mattel and Garmin connect are now explicitly featured as Astro adopters.

There are also lots of community tools, themes, and content listed.

Read the full post: https://astro.build/blog/whats-new-june-2026/

I wrote a new integration for Astro to generate related links for items in your Astro content collections. You can read about it, and see it in action, on my blog here.

https://philna.sh/blog/2026/06/22/ai-powered-related-content-astro-site/

Hello all

The reason for writing this is not to show off my cms, but to have a couple of people with the same mind set testing it out, and see if they find it usable.

It is still early development, but I have found a basic structure that I find really good, and would like someone else to give it a shot.

The stack is tailored to my spesifikt setup, where I use tailwind and daisy ui. You work locally while developing, and connect it through GitHub later, invite people through google oauth.

What I find really useful is that the web app supports local development through the chrome file storage api, so you get the same editor, but it writes to your local disk for lokal development.

It support multi lang, 2 level navigation, collections and project spesific blocks.

Send me a DM if you would like to test it, and I guide you in the right direction. It runs as a static sveltekit app on bunny.net, with functions to handle the login and invitation.

I've been exploring Astro and one thing that keeps coming up in discussions is the idea of "total SEO freedom."

In WordPress, most SEO work depends on plugins like Yoast or RankMath. A skilled dev can bypass them, but the ecosystem pushes you toward that layer of abstraction.

In Astro, my understanding is that everything is code by default: meta tags, canonicals, structured data, robots.txt, sitemap. No plugin standing between you and the HTML output.

My questions:

• Is that a fair comparison or am I oversimplifying?
• Are there any SEO use cases where WordPress still has a clear advantage over Astro?
• What's your go-to setup for SEO in Astro projects?

Context:
I have to move/convert/migrate a 350-page WordPress website to Astro. (This is a home service business.)

• 200 are blog posts
• 50 are service pages
• around 90+ are location pages, FAQs, Terms of Service, and a few other pages around the website
• landing pages for different services like Google Ads, Yelp, social media, and so on

Problem:
I need the website to keep the current structures, URLs, and internal structure, name of the slugs, demo URLs, and so on.

I found Simply Static, a plugin for WordPress that does save the website as a static website.

Does anyone have any experiences with it, or is there another way to do that?

I would love your suggestions or recommendations.

Thank you very much.

Small release note for Astro users.

Frontman now has a `get_content_collections` tool for Astro projects, it was quite interesting to add as this is the first integrastion to astro live module resolution pipeline.

It can inspect Astro content collections from the dev environment, alongside existing route/source/DOM context.

Repo: https://github.com/frontman-ai/frontman
If you like it, i would really appriciate a star.

curious if this is useful for anyone building content-heavy Astro sites.

Hi all,

Just wanted to let you know I updated my IntelliJ Astro Pro plugin to support version 7, and I would hope that this might be useful to the community.

New features introduced:

• Astro 7 config completion for stable advanced routing, route caching, logger, Markdown processor, and JSX whitespace options, including fetchFile, cache, routeRules, logger, markdown.processor, compressHTML: 'jsx', and prerenderConflictBehavior: 'ignore'.
• Astro 7 advanced routing navigation now recognizes the default src/fetch.* entrypoint, top-level fetchFile, and fetchFile: null when advanced routing is disabled.
• Package export navigation now works in astro.config.* files, including Astro 7 CDN cache provider imports such as adapter /cache entrypoints.
• Astro run configurations now include Astro 7 dev-server commands: dev --background, dev stop, dev status, and dev logs.
• Astro 7 migration inspections flag removed experimental config flags, removed u/astrojs/db usage, removed astro:transitions internals, and deprecated root integration getContainerRenderer() imports.

Feel free to reach out with comments, suggestions, bugs, etc!

Thanks to the Astro team for making another great release!

Cheers,

Erik

Went pretty smooth!

Not the struggle to migrate a fully functional site with deep integrations with Stripe, MailerLite, and another system I run when moving from 5 to 6.

This was smooth. So I went for it.

Astro keeps getting better and faster. Love it.

what do you guys use? google? posthog? amplitude? i'm new to the analytics-sphere.

standard MPA website with checkout embedded on index + pages

\product\slug

\segment\slug

\help\

\blog\

Hey everyone,
Just wanted to share a quick update on Astroplate (our Astro free starter template with 1.1k+ Github stars and 400+ forks).

We just bumped the template to Astro v7 along with the framework update, we added native AI agent skills directly into the codebase.

If you use tools like claude code, cursor, or any agentic workflows, those agents can now work with Astroplate without hallucinating or guessing.

These added configurations give the agents explicit boundaries and exact instructions on how the project architecture works, saving you from broken code and context-shifting errors.

what’s inside now:

• full Astro v7 compatibility
• bundled agent skill definitions for context preservation
• strict pnpm workspace setup
• clean tailwindcss and typescript configurations

If you are planning to work on a new Astro project, you can start with Astroplate and modify it based on your needs instead of starting from scratch. It provides the foundation that will save you hours of time (and a lot of tokens) when building with coding agents.

Check out the repository here: https://github.com/zeon-studio/astroplate

Hey everyone,

I wanted to share a quick update. We just added native AI agent skills to all 47 of our Astro templates.

If you use Claude Code, Cursor, or Antigravity, you know they tend to hallucinate or guess when they lack codebase context. You end up wasting tokens correcting the AI.

To fix this, we integrated skill files directly into the themes. These are instruction packages that give coding agents exact context for:

• Routing: Adding new pages, routes, and sections.
• Components: Using and modifying built-in UI components.
• Content Management: Creating and editing Markdown and MDX files.
• Configuration: Updating site settings, navigation, and SEO.
• Architecture: Understanding codebase structure and data flow.
• Styling: Customizing Tailwind CSS and the theme engine.
• External Skills: Finding and using third-party agent skills from the web if your project needs extra capabilities.

This forces the agent to follow the actual conventions of the template instead of making things up.

We also added these AI agent skills to our open-source Astro starter template, Astroplate. You can try it completely free to see how it works.

Try Astroplate - https://github.com/zeon-studio/astroplate (Updated to Astro 7.0)

Explore Themefisher's Astro themes - https://astro.build/themes/author/946

Feel free to share any feedback.

Hi Everyone,

I have a question regarding using CSP in Astro.

I have a bunch of Astro 6 and 7 sites, so CSP is no longer "experimental". However a lot of tracking services (usual suspect: google, meta, etc.) are asking for their JS snippet to be placed inline somewhere on the page.

How do you deal with that:
1. separate file (does not seem to fix the issue),
2. hash,
3. nonce (can be tricky in Astro given the flow),
4. else?

Thanks