# Business and individual examples

Practical Page designs for inquiries, service catalogs, community events, personal projects, dashboards, and public-safe tracking.

## Start with the outcome

These are **design examples you configure**, not live demonstrations or ready-connected workflow downloads. Choose a small first version, use sample information, and review the complete visitor journey before publishing. Official templates and Library Blocks can help with the layout; your organization still needs its own data, workflows, and Lines.

| Audience | A useful first Page | Main building blocks |
| --- | --- | --- |
| Consultant or freelancer | Service inquiry page | Section, Text, Form, ChatigramLine |
| Small business | Service or product catalog | Database, Repeater, Cards, request Form |
| Operations team | Administrator dashboard | Private publication, KPI, Table, timeline |
| Service team | Public-safe progress lookup | Tracking, status fields, optional Line |
| Community organizer | Workshop information and requests | Tabs, Text, DateTime, Form |
| Individual or creator | Portfolio and reading collection | Images, Cards, Repeater, Links |

## Business: turn a service inquiry into a follow-up

**Visitor goal:** understand your service and ask for a conversation.

Create a Page with a clear headline, three service summaries, an explanation of the next step, and a short inquiry form. Add name, email, and a description of the work. If a preferred date is useful, explain that it is a preference rather than a reservation.

Connect the Form submission to an enabled webhook workflow. Configure the workflow to validate the fields, save the inquiry, and notify the person responsible. Add a Line if visitors may need help before submitting.

**Sample copy:** “Tell us what you need. We’ll review your request and reply with the next steps.” Use “Request received” for the receipt. Confirm actual availability later through your process.

**Try first:** submit one synthetic inquiry and check its saved values, notification, and receipt. Related guidance: [forms and workflows](/pages/actions/) and [website service request workflow](/recipes/website-service-request/). The workflow recipe needs your own Page field mapping.

## Business: publish a catalog with an inquiry path

**Visitor goal:** compare available services or products and request more information.

Prepare a database table with a title, short description, category, public image address, and any price you intentionally publish. Bind a Repeater to those fields and place a Card, Image, and Text inside the repeated design. Include clear empty-state text.

Add an inquiry Form or an explicitly configured item-selection action. Use stable record identifiers when a workflow needs to identify a selected item. Check current availability and authoritative prices within the business process before confirming an order.

**Sample copy:** “Browse our services, then send a request for availability and a final quote.” A catalog and request form do not by themselves provide payment processing or a completed checkout.

**Try first:** review a missing image, a long description, an empty category, and the phone layout. See [database collections](/pages/data/).

## Business: give administrators an operations view

**Team goal:** see current workload and recent updates in one place.

Create a dashboard with a KPI for open requests, a status table, and a recent-events timeline. Bind appropriate records or a Workflow Live Feed. A scheduled workflow can calculate a summary; a request workflow can update a public-safe or private feed as appropriate.

Set visibility to **Private · Organization administrators only** before publishing. This current access model suits authorized administrators, not an assumed staff-wide or customer portal.

**Sample headings:** “Requests awaiting review”, “Recent activity”, and “Last updated”. Choose an update mode and show freshness clearly. Missing values should have an explicit empty state.

**Try first:** verify access using the intended administrator account and confirm that the private link is unavailable to a signed-out visitor. Do not put confidential information in a public Page while testing. See [publishing access](/pages/publishing/).

## Business: offer a public-safe progress lookup

**Visitor goal:** check a general status without contacting the team.

Use a Tracking widget with a reference and status mapping. Generate a random UUIDv4 reference per request. Publish only fields such as a general stage, a public-safe description, and last updated time. Your authorized workflow or team updates the status record.

**Sample result:** “In review — updated today. We’ll contact you if we need more information.” A reusable reference is not identity verification; keep confidential details out of the mapping.

**Try first:** check a valid, unknown, duplicate, and expired reference with synthetic records. Read the [tracking guidance](/pages/data/#offer-a-public-safe-tracking-lookup) before sharing references.

## Individual: create a professional portfolio

**Visitor goal:** understand what you make and how to contact you.

Start with a short introduction, a few selected projects, and a contact link or inquiry form. Use Cards for project summaries, Images with alternative text, and descriptive Links to work you are allowed to share. A database-backed Repeater can help if the collection changes often.

**Sample copy:** “Selected design projects and the problems they solve.” Explain your role in each project and provide a clear contact action. Remove client information or assets you do not have permission to publish.

**Try first:** open every project link, navigate with a keyboard, and check that images and long titles work on a phone.

## Individual or community: organize a workshop

**Visitor goal:** find the details and send an attendance request.

Use Tabs for **Overview** and **Visit**, with an agenda, venue information, and accessibility details. Add a Form with name, contact details, and a session preference. Connect it to a workflow that records the request and prepares a reply.

**Sample copy:** “Request a place. We’ll confirm by email after checking capacity.” Collecting a preference does not enforce availability. Add capacity checks and confirmation to your process before promising a reserved place.

**Try first:** review time zones, confirmation language, duplicate requests, and keyboard navigation through the tabs. See [create and edit](/pages/create/) and [appointment request patterns](/recipes/appointments/).

## Individual: curate a public reading collection

**Visitor goal:** find a useful article, resource, or project update.

Store titles, brief original summaries, categories, and source links in a table. Display them as a List or Repeater. Use a workflow to prepare draft summaries if helpful, then review the material before adding it to the public collection.

**Sample copy:** “A small collection of resources I found useful, with links to the original authors.” Publish material you may share and keep private reading notes separate. Collection search covers the loaded records, so keep navigation clear.

**Try first:** check attribution, source links, empty states, and the fields exposed by the public mapping.

## Plan a manageable first release

Choose one visitor goal and one primary action. Prepare a small sample dataset, design the Page, configure its connections, review the saved draft, and publish deliberately. Test the published behavior with synthetic data before sharing widely.

Check [pricing and allowances](/workspace/billing/) for published Pages and their connected resources. For practical checks and recovery steps, use [Pages help](/pages/help/).
