> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/tutorials/creating-a-basic-website/css-and-images.md).

# CSS and Images

Our homepage is currently missing the CSS and image files. To include these files:

1. Open File Explorer and navigate to both your Umbraco project folder and the Custom Umbraco Template folder.

{% hint style="info" %}
The Umbraco project folder refers to the folder created during the [Umbraco installation](/umbraco-cms/get-started/installation.md).
{% endhint %}

2. Copy the **css** and **images** folders from the *Custom Umbraco template* folder.
3. Paste them inside the **wwwroot** folder of your Umbraco project.
4. Go to the **HomePage** template in the **Settings** section.
5. Make sure the stylesheet reference in the HTML is `/css/main.css`.

   ![Stylesheet reference](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-280196bad3a54d993edb2fc0d6a1bcf26a7f5cb6%2Fstylesheet-reference.png?alt=media)

## Stylesheet Reference

Use the Developer Tools in Chrome/Firefox/Edge and refresh the frontend: `http://localhost:xxxx.`

* Check the **Network** tab to confirm no CSS or image files are missing.
* If you see any errors, double-check for typos and confirm the folders are placed correctly inside the **wwwroot** folder of your Umbraco project.

## How Static Files Are Served

Umbraco serves static files such as stylesheets and images from the **wwwroot** folder. This folder acts as the web root in ASP.NET Core applications. Any files placed here are publicly accessible and can be served directly by the application when requested by the browser.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-cms/develop-with-umbraco/tutorials/creating-a-basic-website/css-and-images.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.