How arthelokyo/astrowind works
Project type and purpose
• AstroWind is a static-first, component-based website template built with Astro 5.0 and Tailwind CSS.
• Its primary purpose is to generate a high-performance, SEO-friendly site (including a blog) at build time, with optional hybrid/SSR support.
File structure
• Top-level configuration: astro.config.ts, tailwind.config.js, netlify.toml, docker-compose.yml, Dockerfile, GitHub Actions workflows, and Vercel/Netlify deploy files—indicating CI/CD and containerization support.
• Public assets (public/): static files (robots.txt, headers, Decap CMS assets).
• Source code (src/):
• assets/ (styles, images, favicons)
• components/ (Astro components organized by feature: blog, common, ui, widgets)
• layouts/ (page templates)
• pages/ (file-based routing for pages and dynamic blog routes)
• content/ and data/ (Markdown/MDX posts, frontmatter configuration)
• utils/ and navigation.ts (helper functions for routing, permalinks, image optimization)
• config.yaml (site metadata, blog settings, analytics config)
• No traditional backend or database: blog content is sourced from Markdown/MDX files.
README for additional insights
• Core stack: Astro + Tailwind CSS + MDX + built-in image optimization (Astro Assets and Unpic).
• Features: SSG/hybrid output, blog engine (categories, tags, RSS), SEO (Open Graph, sitemap), analytics integrations (Google Analytics, Splitbee).
• Deployment: static export (dist/) to any host, plus first-class support for Netlify and Vercel.