Starting points for building your own viewer of Pascal projects. Each folder is a complete, standalone app: fork it, change the lighting, the post stack or the interface, and deploy it anywhere. None of them needs Pascal's editor packages.
| Template | What it shows | Source |
|---|---|---|
listing |
A published project's 3D file, with floors, room names and areas, and doors and windows that open | Baked 3D file |
Every template reads Pascal's public read, GET https://editor.pascal.app/api/projects/{id}/scene. It answers a project's published revision with the scene graph, its materials and short-lived links to the baked 3D file. Public projects need no key.
npx degit pascalorg/viewer-templates/listing my-viewer
cd my-viewer
npm install
npm run dev
# open http://localhost:5173/?project=<published project id>Or deploy a copy straight away:
Each template's AGENTS.md explains the read, what the 3D file contains and how to customise it, for you and for your coding agent.
- Never put a Pascal API key in the browser. Private projects need a server you control.
- Signed 3D file links last ten minutes; read the scene again to renew them.
- A template must build, typecheck and pass its smoke test in CI.
MIT