---
title: "HTML/CSS/JS Runtime For Deploying Static Websites | Hostman Docs"
description: "Learn how to deploy HTML, CSS, and JavaScript static websites on App Platform, including project structure, build output requirements, and deployment settings."
---

> For the complete documentation index for AI agents, see [llms.txt](https://hostman.com/llms.txt).

The **HTML/CSS/JS** runtime is designed for deploying pre-built frontend applications and static websites. It is suitable for projects generated with tools such as Hugo, Astro, VitePress, Jekyll, and similar static site generators.

Unlike applications built with frameworks such as Vue.js or React, App Platform does not build the application during deployment. Instead, it serves the pre-generated static assets directly from your repository.

## Preparing Your Project

Before deployment, build the project locally. The build process should generate a directory containing the static assets for your site, for example:

-   `dist`
-   `build`
-   `public`

The output directory must include an `index.html` file together with all required assets.

Example for Hugo:

```shell
hugo
```

After the build completes, the generated files will be available in the public directory.

## Deployment Behaviour

For HTML/CSS/JS applications, the following deployment options are not available:

-   Build command
-   Build directory
-   Dependency settings

This is because the application is treated as already compiled and does not require a build step during deployment.

## Project Directory

If the generated static files are located outside the repository root, specify the path to the directory containing the build output.

For example, if the compiled site is located in `/public`, use:

```shell
public
```

App Platform will then serve files directly from this directory.