Overview
Start Here
Installation
Tutorial
Architect App Builder
Todo List App
Beacon Beats Audio Store
UCAL App
Authoring
Dynamic Apps
Static Apps
dev_docs
Why Pharos Feels Different
Architect Builder
Framework
Artifacts & Layout
Configuration
Outbound Email
How to Use CLI
Contracts
YAML Authoring
Action Hooks and Middleware
Feature Transaction Primitives
Generated Surfaces
Declarative CRM
Input Validation
Identity and Tenancy
UI Surface Library
Social Connections
Payment Provider Management
Integration Adapters
Reference
Contract, UI, and Surface Reference
Styling UI Elements
Architect Media Artifacts
API Docs
Use Cases
Dynamic SPAs
Generated Admin and APIs
Scheduling and Marketplaces
Multi-App Hosting
Release Notes
Vision
Pharos Framework

← Back

Static Apps

static_app is the smallest checked static-pages app in the repository.

What you will build

static_app shows the basic Pharos static app shape:

  • a checked app root under apps/static_app/
  • a canonical app manifest source in pharos.app.yml
  • app-owned static assets and content
  • a packaged build artifact under dist/apps/static_app/

Build

pharos build app static_app --build-dir dist

Expected artifact root:

dist/apps/static_app/

Verify

pharos verify app static_app --build-dir dist

Serve

pharos serve app static_app --build-dir dist --port 8080

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/

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