Working with surfaces
Surfaces are the runtime renders of accepted Receipts. This guide covers the day-to-day operations once a surface exists.
Surface basics
A surface is a single composable render — a page, dashboard, or embed. It is materialised from an accepted Receipt that names every block, prop, capability, and theme token. Each time you change a surface, PhiCo proposes a new Receipt; nothing publishes until you accept the diff.
Surface properties
Each surface has configurable properties:
- Title — The page title shown in browser tabs
- Slug — The URL path for your surface
- Description — SEO meta description
- Thumbnail — Preview image for sharing
Organizing with tags
PhiWebs organises surfaces by tags, not folders. Each Receipt carries
a tags array — a flat label set that travels with the surface and the
marketplace listing if you publish one. A single surface can have
multiple tags, so a tag behaves like a virtual folder you can stack
freely. There is no nested folder tree, by design.
Tag-based filter and search in the Studio surface list is 🔵 planned —
the data model is already in place (Receipt.tags), the listing UI ships
in a future release. Until then, use clear Receipt titles and
descriptions for organisation.
Duplicating surfaces
Right-click any surface to duplicate it. This is useful for creating variations or templates for future use.
Version history
Every accepted Receipt is an immutable snapshot. Access the version history to roll back to any previous Receipt or diff two versions line by line. Retention by plan: Pro 7 days, Team 30 days, Enterprise 90 days. Basic plan does not include version history.
Next
- Using blocks — Learn about the different block types and how to use them effectively.