## Documentation index

This index lists every available documentation page and its Markdown source.

- [Documentation](https://veta.varavel.com/docs/index.md)
  - [Getting Started](https://veta.varavel.com/docs/getting-started/index.md)
  - [Installation](https://veta.varavel.com/docs/installation/index.md)
  - [Guides](https://veta.varavel.com/docs/guides/index.md)
    - [Project Structure](https://veta.varavel.com/docs/guides/project-structure/index.md)
    - [Configuration](https://veta.varavel.com/docs/guides/configuration/index.md)
    - [Pages](https://veta.varavel.com/docs/guides/pages/index.md)
    - [Data](https://veta.varavel.com/docs/guides/data/index.md)
    - [Markdown](https://veta.varavel.com/docs/guides/markdown/index.md)
    - [Templates](https://veta.varavel.com/docs/guides/templates/index.md)
    - [Components](https://veta.varavel.com/docs/guides/components/index.md)
    - [Filters](https://veta.varavel.com/docs/guides/filters/index.md)
    - [Assets And Tailwind CSS](https://veta.varavel.com/docs/guides/assets-and-tailwind/index.md)
    - [Themes](https://veta.varavel.com/docs/guides/themes/index.md)
    - [Development Server](https://veta.varavel.com/docs/guides/development-server/index.md)
    - [Build And Output](https://veta.varavel.com/docs/guides/build-and-output/index.md)
    - [Deployment](https://veta.varavel.com/docs/guides/deployment/index.md)
  - [Reference](https://veta.varavel.com/docs/reference/index.md)
    - [CLI Reference](https://veta.varavel.com/docs/reference/cli/index.md)
    - [Config Reference](https://veta.varavel.com/docs/reference/config/index.md)
    - [Page Generators Reference](https://veta.varavel.com/docs/reference/page-generators/index.md)
    - [Template Context Reference](https://veta.varavel.com/docs/reference/template-context/index.md)
    - [Troubleshooting](https://veta.varavel.com/docs/reference/troubleshooting/index.md)
  - [API](https://veta.varavel.com/docs/api/index.md)
    - [JavaScript API](https://veta.varavel.com/docs/api/javascript/index.md)
    - [File API](https://veta.varavel.com/docs/api/files/index.md)
    - [HTTP Client](https://veta.varavel.com/docs/api/http-client/index.md)
    - [Parse API](https://veta.varavel.com/docs/api/parse/index.md)
    - [Template Functions](https://veta.varavel.com/docs/api/template-functions/index.md)
    - [Environment And Console](https://veta.varavel.com/docs/api/environment-and-console/index.md)
    - [Markdown Frontmatter](https://veta.varavel.com/docs/api/frontmatter/index.md)


## Documentation content

The documentation for the current page follows, reproduced verbatim.


# Assets And Tailwind CSS

Static assets live in `public/`. Tailwind CSS is configured through `veta.yaml` and uses one or more stylesheets inside `public/` as entrypoints.

## Public Assets

Files in `public/` are copied to the output root:

```txt
public/robots.txt           -> dist/robots.txt
public/images/logo.svg      -> dist/images/logo.svg
```

Public files are copied as-is. Veta does not minify or transform copied public assets.

Use the `url` template function when linking copied assets from templates. It returns a path relative to the current page, so the generated site can be served from a domain root, a subdirectory, or static storage without a configured base URL:

```html
<link rel="stylesheet" href="{{ url("/styles.css") }}">
<img src="{{ url("/images/logo.svg") }}" alt="Logo">
```

## Tailwind CSS Entrypoints

The starter uses `public/styles.css`:

```css
@import "tailwindcss";
```

Configure it with:

```yaml
tailwindcss:
  stylesheets:
    - styles.css
  minify: true
```

`stylesheets` entries are relative to `public/`, so `styles.css` means `public/styles.css`.

You can configure multiple entrypoints:

```yaml
tailwindcss:
  stylesheets:
    - styles.css
    - admin.css
  minify: true
```

## Generated CSS Output

Veta writes each compiled stylesheet to the build output using the same path:

```txt
public/styles.css           -> dist/styles.css
public/admin.css            -> dist/admin.css
```

Tailwind scans the materialized output directory, so classes used in generated HTML are included.

If an entrypoint should scan a narrower set of files, configure that in the CSS file with Tailwind's `@source` directive.

## Minification

`tailwindcss.minify: true` minifies the generated stylesheet through Tailwind CSS.

This setting is separate from `html.minify`, which only affects generated `.html` files.

## Disabling Tailwind CSS

Remove `tailwindcss.stylesheets` or leave it empty:

```yaml
tailwindcss:
  stylesheets: []
  minify: true
```

Without `stylesheets`, Veta does not run Tailwind CSS.

## Practical Pattern

Use `public/styles.css` for your Tailwind entrypoint and keep images, fonts, and static files under `public/`:

```txt
public/
  styles.css
  fonts/inter.woff2
  images/logo.svg
  robots.txt
```