astrowind Documentation

🚀 AstroWind

🌟 Most starred & forked Astro theme in 2022, 2023, 2024 & 2025. 🌟

AstroWind is a free and open-source template to make your website using Astro v7 + Tailwind CSS v4. Ready to start a new project and designed taking into account web best practices.

• ✅ Production-ready scores in PageSpeed Insights reports.
• ✅ Integration with Tailwind CSS v4 supporting Dark mode and RTL.
• ✅ Fast and SEO friendly blog with automatic RSS feed, MDX support, Categories & Tags, Social Share, ...
• ✅ Image Optimization (using new Astro Assets and Unpic for Universal image CDN).
• ✅ Generation of project sitemap based on your routes.
• ✅ Open Graph tags for social media sharing.
• ✅ Analytics built-in Google Analytics integration.

Table of Contents

• Demo
• Upcoming: AstroWind 2.0 – We Need Your Vision!
• TL;DR
• Getting started
  • Project structure
  • Commands
  • Configuration
  • Deploy
• Frequently Asked Questions
• Contributing
• Acknowledgements
• License

Demo Copy Chapter

📌 https://astrowind.vercel.app/

🔔 Upcoming: AstroWind 2.0 – We Need Your Vision! Copy Chapter

We're gearing up for AstroWind 2.0, and we want it to be shaped by you, our community. Join the discussion and share your ideas, suggestions, and feedback to help us make AstroWind even better.

Share Your Feedback in Our Discussion!

TL;DR Copy Chapter

npm create astro@latest -- --template arthelokyo/astrowind

Getting started Copy Chapter

AstroWind tries to give you quick access to creating a website using Astro v7 + Tailwind CSS v4. It's a free theme which focuses on simplicity, good practices and high performance.

Very little vanilla javascript is used only to provide basic functionality so that each developer decides which framework (React, Vue, Svelte, Solid JS...) to use and how to approach their goals.

Note: Requires Node.js >= 22.12.0. The template currently uses output: 'static', but the blog only works with prerender = true.

Project structure Copy Section

Inside AstroWind template, you'll see the following folders and files:

/
├── public/
│   ├── _headers
│   └── robots.txt
├── src/
│   ├── assets/
│   │   ├── favicons/
│   │   ├── images/
│   │   └── styles/
│   │       └── tailwind.css
│   ├── components/
│   │   ├── blog/
│   │   ├── common/
│   │   ├── ui/
│   │   ├── widgets/
│   │   │   ├── Header.astro
│   │   │   └── ...
│   │   ├── CustomStyles.astro
│   │   ├── Favicons.astro
│   │   └── Logo.astro
│   ├── content.config.ts
│   ├── data/
│   │   └── post/
│   │       ├── post-slug-1.md
│   │       ├── post-slug-2.mdx
│   │       └── ...
│   ├── layouts/
│   │   ├── Layout.astro
│   │   ├── MarkdownLayout.astro
│   │   └── PageLayout.astro
│   ├── pages/
│   │   ├── [...blog]/
│   │   │   ├── [category]/
│   │   │   ├── [tag]/
│   │   │   ├── [...page].astro
│   │   │   └── index.astro
│   │   ├── index.astro
│   │   ├── 404.astro
│   │   ├-- rss.xml.ts
│   │   └── ...
│   ├── utils/
│   ├── config.yaml
│   └── navigation.ts
├── package.json
├── astro.config.ts
└── ...

Astro looks for .astro or .md files in the src/pages/ directory. Each page is exposed as a route based on its file name.

There's nothing special about src/components/, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.

Any static assets, like images, can be placed in the public/ directory if they do not require any transformation or in the assets/ directory if they are imported directly.

🧑‍🚀 Seasoned astronaut? Delete this file README.md. Update src/config.yaml and contents. Have fun!

Commands Copy Section

All commands are run from the root of the project, from a terminal:

Configuration Copy Section

Basic configuration file: ./src/config.yaml

/* Detailed source-code truncated for AI context efficiency. */

Customize Design

With Tailwind CSS v4, all configuration is CSS-first. To customize Font families, Colors or more Elements refer to the following files:

• src/components/CustomStyles.astro — CSS variables for colors and fonts
• src/assets/styles/tailwind.css — Tailwind theme tokens (@theme), custom utilities (@utility), and plugins

Deploy Copy Section

Deploy to production (manual)

You can create an optimized production build with:

npm run build

Now, your website is ready to be deployed. All generated files are located at
dist folder, which you can deploy the folder to any hosting service you
prefer.

Deploy to Netlify

Clone this repository on your own GitHub account and deploy it to Netlify:

Deploy to Vercel

Clone this repository on your own GitHub account and deploy to Vercel:

Deploy to PandaStack

Clone this repository on your own GitHub account and deploy to PandaStack:

Contributing Copy Chapter

If you have any ideas, suggestions or find any bugs, feel free to open a discussion, an issue or create a pull request.
That would be very useful for all of us and we would be happy to listen and take action.

Acknowledgements Copy Chapter

Initially created by Arthelokyo and maintained by a community of contributors.

License Copy Chapter

AstroWind is licensed under the MIT license — see the LICENSE file for details.