← Back

Tutorial: Build A Static Pharos App

This tutorial uses static_app_template, the smallest checked static-pages app in the repository.

What you will build

static_app_template shows the basic Pharos static app shape:

• a checked app root under apps/static_app_template/
• an app manifest in pharos.app.json
• app-owned static assets and content
• a packaged build artifact under dist/apps/static_app_template/

This is the simplest way to see the Pharos model: the app owns its files, and the framework owns packaging and serving behavior.

Build

pharos build app static_app_template --build-dir dist --text

Expected artifact root:

dist/apps/static_app_template/

Verify

pharos verify app static_app_template --build-dir dist --text

Serve

pharos serve app static_app_template --build-dir dist --port 8080 --text

Open:

http://127.0.0.1:8080/

What this shows

This flow demonstrates the current static-pages contract:

• the app owns its manifest, content, and assets
• Pharos builds the final artifact layout
• the build output is predictable and easy to inspect
• the shared runtime can serve the built artifact without extra app-local framework glue

Inspect the packaged app

Look at:

dist/apps/static_app_template/

You should see the files that matter for packaging and serving, including the finalized app manifest and the app content copied into the artifact.

Next

• Build and serve the documentation app
• Build a declarative dynamic app