Astro with Tailwind

Also with...

• flowbite https://github.com/manfredengler/astro-tailwind-boilerplate/tree/flowbite
• DaisyUI https://github.com/manfredengler/astro-tailwind-boilerplate/tree/daisyui

This directory is a brief example of an Astro site that can be deployed to Vercel with zero configuration. This demo showcases:

• / - A static page (pre-rendered)
• /ssr - A page that uses server-side rendering (through Vercel Edge Functions)
• /ssr-with-swr-caching - Similar to the previous page, but also caches the response on the Vercel Edge Network using cache-control headers
• /image - Astro Asset using Vercel Image Optimization
• /edge.json - An Astro API Endpoint that returns JSON data using Vercel Edge Functions

Learn more about Astro on Vercel.

Deploy Your Own

Deploy your own Astro project with Vercel.

Live Example: https://astro-tailwind-boilerplate.vercel.app/

Project Structure

Astro looks for .astro, .md, or .js 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 or layouts.

Any static assets, like images, can be placed in the public/ directory.

Commands

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

Command	Action
pnpm install	Installs dependencies
pnpm run dev	Starts local dev server at localhost:3000
pnpm run build	Build your production site to ./dist/
pnpm run preview	Preview your build locally, before deploying
pnpm run start	Starts a production dev server at localhost:3000
pnpm run astro ...	Run CLI commands like astro add, astro preview
pnpm run astro --help	Get help using the Astro CLI