# Assets

This folder stores generic static assets that might be required for a certain WordPress website. This might contain fonts, images, videos, icons and similar assets that are more part of design, rather than content. Assets that are more part of the content will probably come from WordPress directly since they will be editable content.

## Include static assets in Twig files

In order to reference static files inside Twig templates, custom `get_frontend_static_asset` function has to be called from Twig template.

```twig
<!-- "assets/images/my-image.png" corresponds to file that has path "/html/assets/images/my-image.png" -->
<img src="{{ function('get_frontend_static_asset', 'assets/images/my-image.png') }}" />
```

Name of the asset you want to insert requires full path that is has inside `/html` folder. For example, file that has path `/html/assets/images/my-image.png` file has `assets/images/my-image.png` as path inside assets and that is used as argument for this function.

Any folder inside `/assets` also supports nesting so assets can be organized as needed. This directory structure will be reflected in the path that is needed for `get_frontend_static_asset` (e.g. `assets/images/logo/main-logo.png`).

> If you are wondering from where these paths are grabbed and what value they have, just check the generated manifest JSON file (`/wp-content/themes/linde/frontend/manifest.json`) that is being output by Webpack.