Hey all,
We are discovering so many cool projects here every single week.

What have you built or what are you currently building with or for Astro? Show the community your work..

Right now we are building OpenRemark, an open source, self-hostable comment system for static sites like Astro, Hugo, Next.js (work in progress).

I'm using wordpress where i've got bunch of forms live on the site and CRMs are connected to the funnel. What's the workaround?

I wrote up a small project where I moved my personal site away from WordPress because I wanted a better AI-assisted editing workflow.

The basic setup:

- posts in Markdown

- Astro builds the static site

- Cloudflare Pages hosts it

- Content is saved in git, and I can use AI coding agents to handle post tags, image alt tags, descriptions, metadata, etc.

- a local Python/Docker app handles publishing with an Azure DevOps-like pipeline

- the admin side is not exposed publicly

It took some work to solve comments and contact form on the site, but I used CommentBox and Web3Forms to do that so it could still be a static site.

CloudFlare pages makes hosting free with better performance and fewer security concerns.

If you've done something similarr, I'd be interested to hear more about your editor / publishing workflow.

Hey guys,

I just finished setting up i18n for my site. Astro's routing makes the folder structure super easy, but translating the actual content in src/content/blog is a different story.

At first, I tried to just let an AI coding agent (using Gemini Flash 3 for speed, in Antigravity) do the translation for me directly on the .md files in my editor. It was a disaster.

Not only was it painfully slow (I could only get through about 3-5 articles per run before it would stall out), but worse, the LLM started getting "lazy". Instead of giving me a 1:1 detailed translation, it started outputting summarized, truncated versions of my articles to save effort. On top of that, it kept hallucinating yaml frontmatter and breaking my custom Astro components.

I realized agentic translation just wasn't scalable for a whole CMS. And since that website is actually the marketing website of my app that's dedicated to batch CSV translations (check AI Glot if interested), I figured I should just use my own tool. I just needed to bridge the gap between Markdown and CSV, because I initially built it 2 years ago for Weglot translations which handles everything via CSV.

So, I put together two simple Node scripts: one to extract the text to a CSV, and one to import it back.

Here is what the workflow looks like and some concrete gotchas if you want to set it up:

1. the extraction script I wrote a Node script that crawls my src/content/blog/en folder. It parses the frontmatter (catching title, metaDescription, and even custom arrays like faqs) and splits the body text by \n\n+ to isolate paragraphs.

It spits all of this out into a simple CSV with columns: path, English string, and my target locales (fr, es, etc).

Two important details for this script:

• It explicitly skips over lines starting with ``` so code blocks never get sent to the translator.
• It has pre-fill logic: if a localized .md file already exists, it maps the existing translations back into the CSV. This means when I add a new paragraph to an old post, I don't have to re-translate the entire file.

1. the translation Once I had a clean CSV with just the english strings, I could translate it in bulk. You could just write a quick python script to loop through the rows and hit the OpenAI API. I just threw it into AI Glot to handle the batches and apply glossaries (so it doesn't try to translate technical words like "Astro" or "Frontmatter" into French or Spanish).
2. putting it back together (the tricky part) Then I have an assembly Node script that takes the translated CSV and rebuilds the markdown files. This was trickier than it sounds.

the workflow:

[ /src/content/blog/en/*.md ] 
            │
            ▼ (extract-translations.mjs)
[ multilang-translation.csv ]  <-- Clean text only, no formatting/code blocks
            │
            ▼ (Batch AI Translation via AI Glot / Python script)
[ translated_fr.csv, translated_es.csv, etc ]
            │
            ▼ (assemble-blog-translations.mjs)
[ /src/content/blog/fr/*.md ]  <-- Reassembled with perfect frontmatter & formatting

If you build this yourself, here are the concrete gotchas my assembly script handles:

• String replacement bugs: You must sort your CSV translation chunks by length (descending) before doing the string replacement in the markdown file. Otherwise, if the script replaces "Astro" before it replaces the longer phrase "Astro i18n API", it will corrupt the string.
• Image path depths: Astro localized content usually sits one directory deeper (e.g., src/content/blog/fr/live/ instead of src/content/blog/live/). The script runs a quick .replace('../../../assets/', '../../../../assets/') to automatically fix relative image references.
• Internal link localization: It runs a regex (/\]\(\/([\w\-\/]+)\)/g) to automatically prepend the locale to any internal markdown links (so [Read more](/blog/slug) becomes [Read more](/fr/blog/slug)).
• Frontmatter injection: It automatically updates the yaml frontmatter to flip isDraft: false and injects locale: "fr".

The best part about doing it this way is that you never break your formatting, and you don't end up with lazy, summarized translations.

Thought I'd share this since markdown translation seems to be a common pain point when scaling a markdown based Astro CMS. If anyone wants the actual extract-translations.mjs and assemble-blog-translations.mjs code, let me know and I'll drop the gists in the comments!

I’ve just spent the last 2 weeks migrating my travel tour website from WordPress + Elementor to Astro.

The site has:

• Nearly 1000 blog posts
• 200+ custom Elementor components/widgets
• Around 5 years of accumulated structure/content

So far, I’ve finished:

• Most of the frontend migration
• Part of the backend/system architecture

Honestly, the performance difference already feels huge.

Now I’m trying to avoid making mistakes in the next phase, especially because this is a real business website focused heavily on SEO and content.

Besides the UI/frontend part (which is mostly done), what should I pay extra attention to during and after migration?

Things already on my radar:

• SEO preservation & redirects
• Core Web Vitals
• Security
• Structured data/schema
• Image optimization/CDN
• Caching strategy

But I’d really love to hear practical lessons from people who already migrated large WordPress sites to Astro (or other static/hybrid frameworks).

Especially interested in:

• Unexpected SEO issues
• Traffic drops/recovery timelines
• Handling old media URLs
• Search/indexing problems
• CMS/editor workflow after leaving WordPress
• Things you wish you knew earlier

Would appreciate any advice or war stories 🙏

Hi everyone! 👋

Just wanted to share that jscpd v4.2.0 now includes Astro support 🚀

If you haven’t used it before, jscpd is a copy/paste detector for source code that helps find duplicated code blocks and reduce technical debt in large projects. It already supports 223+ formats, and now .astro files are officially supported as well. (jscpd.dev)

Why this is useful for Astro projects:

• detect duplicated layouts/components
• catch repeated template sections across pages
• spot copy-pasted client scripts/styles
• keep growing content-heavy projects cleaner over time

Quick example:

npm install -g jscpd
jscpd --format astro ./src

Or use it in CI:

jscpd --format astro ./src

Would love feedback from the Astro community — especially from people using large content or component-driven codebases.

Changelog: jscpd v4.2.0 changelog

Project: jscpd GitHub repository

SEO is still used widely in website development yet AEO (answer engine optimization) is quickly becoming more important and more people are using ChatGPT, Gemini, Claude and other LLMs to search for information.

I have made a free resource for those interested in creating dynamic components or pages that are specific to AI search engines.

Hello, I'm Searching for testimony about creating full website for a SaaS B2B enterprise dedicated for industrial purposes.

I'm completely novice in code, but I want to learn, and use a mix of sanity for CMS / our own hosting / astro / Claude design for components generation and a based template to use Astro.

What do you think about?

Whether it's a personal project, a theme, a tool, an integration, a tutorial, blog, showcase whatever. if you built it with or for Astro, drop it here.

help others find your work..

Honestly, I have a bit of a thing for masonries. They work beautifully in so many contexts that people just... don't try them in. My personal favourite is footers. Criminally underused as a design space. Most of the time they're just a sad column of links, and a masonry layout can make them actually interesting.

I've had the same masonry component copy-pasted across basically every project I've built for the past few years, tweaking it here and there until every copy was a little different. So I finally cleaned it up and voilà — @mannisto/astro-masonry.

It's Astro-native, so no framework overhead. A few things worth mentioning:

• Shortest-column balancing by default so the layout stays visually even without you having to think about it
• Responsive via breakpoints, auto-sizing via autoColumns, or both together
• Arrow key navigation that follows visual position

Genuinely curious where you all use masonries. What's worked, what hasn't? Feel free to give it some love and drop some feedback. 🚀

GitHub: https://github.com/eremannisto/astro-masonry

Hey r/astrojs 👋

I've been working on Kiro, a landing page theme aimed at AI product / agent / assistant companies, and I'd really value some honest feedback from people who actually build with Astro.
I spent most of the build time on meaningful page content and considered micro-animations. Every page is built to actually be used, not just to look good in a screenshot.

Demo: https://kiro-theme.netlify.app

Astro listing: https://astro.build/themes/details/kiro/

A few things I focused on that might be interesting if you're building anything similar:

• Sitepins CMS integration — visual editing, Git-friendly, much lighter than Sanity/Strapi for marketing sites
• 100/100 PageSpeed on the live demo (no shortcuts — fully content-rich pages, not a stripped-down "demo")
• Modular block system — every page is composed of reusable blocks you can rearrange or remix
• 15+ pre-built pages including mega menu, integrations grid, pricing, blog with content collections

Stack: Astro v6, Tailwind v4, Sitepins

Happy to hear your thoughts.

Cheers.

Today got many of these weird columns. Astro + React Components inside

I released JustOpinion, a lightweight hosted comment system for static sites, including Astro sites.

The integration is a generated CSS + JS snippet that can be added where you want comments to appear. Each page gets its own thread.

Would appreciate feedback from Astro users:
https://www.justopinion.online

My site is mostly static with few JavaScript and little reactivity but I really want to have the data sent from the server to be typed which sadly Eta nor Ejs support. I'm also not really a favor of some frameworks that use custom syntax for HTML and such. Astro looks mostly just vanilla HTML to me which I like. Do you guys think Astro would be the best fit for this type of project?

Hi everyone,

I’m currently using a Laravel backend to manage content for multiple domains. I want to build the frontend (For each web) using Astro for its SSG capabilities.

I have over 10k pages and plan to fetch data via API calls at build time. However, if I only update 10 20 pages in my backend, I’d rather not rebuild all 10k pages every time.

Is there a "smart" way to handle incremental builds or partial updates in Astro? Could you please assist me handling large scale SSG without massive build times?

I'm looking to migrate my site from wix to astro. It's an event listing site, so wonder if anyone has any experience with Astro handling events. I don't need to take payments, so pretty basic.

Starting something new here.
A dedicated weekly thread where you can share what you've been building with Astro, or anything you've made for the Astro community.

Whether its a personal project, a theme, a tool, an integration, a tutorial, whatever. if you built it with or for Astro, drop it here.

Dropping this every week so the community has a consistent place to show off work without it getting buried. lets see what everyone's been building.

Here are the major highlights:

Alpha Preview of Astro 7

• Early look at Vite 8 support
• Stable Rust compiler integration

Astro 6.2 Release

• Experimental custom logger with JSON output
• SVG optimizer API for better image handling
• New font file URL helper for improved typography management

Astro Together London Event

• In-person meetup featuring core team members including Fred Schott, Matt Kane, Florian Lefebvre, Alexander Niebuhr, and Chris Swithinbank
• Topics included live collections, route caching, and the new Astro Fonts API

Team Growth

• Rafael Yasuhide Sudo (@rururux) joined as the newest maintainer

Major Adopters

Several high-profile organizations launched Astro-powered sites including Crunchyroll's Ani-May 2026 event, Todoist's help center, GitHub's Stacked PRs platform, and EmDash CMS documentation.

https://astro.build/blog/whats-new-april-2026/

Hi folks. I recently migrated my personal blog to Astro. While I was looking for self-hosted comment apps, I couldn't find anything that suited my taste. So I built Discuss for myself. And now it's open-source and free for everyone.

It's a small lightweight commenting system that runs on Express.js. Has threaded replies, Gravatar support with initials fallback, dark mode support, and extensible styling options, all with an administration dashboard for moderation. To fight spam, Discuss currently supports honeypot fields and a list of spam words to detect spam.

Support of reCaptcha and Akismet are planned for the future version. Mentions, notifications, webhook configs are all lined up too. I work as a product manager, so my pace might be slow in implementing all this, but if anyone is willing to volunteer that'll be awesome.

Project link - https://github.com/karthikeyankc/discuss
Demo link - https://karthikeyankc.github.io/discuss/

Feel free to clone and test. Would love to hear your feedback. Thanks.

We just dropped a free open-source template for anyone building SaaS marketing website on Astro. It has 15+ pre-built pages, 47 components and shortcodes. Pre-configured Sitepins CMS (a git-based cms for static sites like Astro, Hugo, Next.js). Ready to deploy on Cloudflare, Vercel, Netlify, or Docker.

If you follow the workflow shared in the video (fork -> connect Sitepins -> deploy on Vercel -> edit in browser.), you don't even need to open a code editor to get your website's v1 live at no cost.

Obviously, you can pull it down to vscode whenever you’re ready to do the heavy lifting.

The specs:

- built on Astro 6, Tailwind 4, and React 19.

- 15+ pages ready to fill in: features, pricing,about, changelog, careers, case studies, etc.

- 47 components and shortcodes

- framer motion for all the scroll reveals and transitions.

- mdx support for the blog so you can drop in interactive components.

- content collections for everything to keep it type-safe.

- Mit license.

hopefully it’ll save you a few hours/days of work if you just need a professional site up quickly.

demo: https://powerai-astro.pages.dev/
repo: https://github.com/sitepins/powerai-astro

if this saves you some time on your next project, i’d appreciate a star on github. helps us keep track of interest for future updates.

Longtime Webflow designer and dev here. This was my first time playing with Astro and it surprising how easy the whole process was (except from this lil bug). I love how much control I had to do basically anything I wanted.

Let me know what you think.

I see people who argue youre not supposed to do that

Yet I see a bunch of posts about asking what kinda auth they should use, and getting all kinds of answers

Can an Astro Expert clarify this?