# Cosmetic dentistry: company website using Next.js

A company website blueprint for cosmetic dentistry built with Next.js on Ample. Domain schema: treatments (code, name, description, session_count, price_from): whitening, veneers, bonding and aligner offerings; before_after_galleries (treatment_id, title, consent_reference, published): consented, de-identified case galleries; locations (name, address, phone, opening_hours): practice locations; financing_options (name, provider, terms_summary): payment plans presented publicly; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: treatment catalog with session counts, consented case galleries, financing options, locations and hours. Kept out of scope until handling is reviewed: patient photographs without documented consent, clinical records, payment details. Case photographs are patient data; publish only with documented consent and de-identification. Technical basis verified on Next.js: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.

## You need

- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- Bucket credentials from `ample bucket create` passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
- A review of which cosmetic dentistry data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

- build npm run build --if-present
- install npm install
- runtime node
- sizes-1vcpu-1gb
- start npm run start
- template node-22

## Steps

1.  **Model the cosmetic dentistry domain.** Create the tables treatments, before_after_galleries, locations, financing_options, asset_versions. Whitening, veneers, bonding and aligner offerings live in treatments; keep the sensitive classes (patient photographs without documented consent, clinical records, payment details) out of this schema.

2.  **Workflow step 1.** Model the public catalog as tables and render pages from them.

3.  **Workflow step 2.** Build the site and publish versioned static assets to the CDN bucket.

4.  **Workflow step 3.** Keep every sensitive data class out of the site; link to separate, authorized systems instead.

5.  **Workflow step 4.** Deploy and verify the public URL and the CDN asset URL.

6.  **Deploy.** Run the synchronous deploy once and read the result. Re-running with no change is a no-op.

```
    $ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
    ```

7.  **Verify.** Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the cosmetic dentistry workflow.

```
    $ ample logs <deployment_id> --kind build
    ```

## How it was checked

✓ app responds on its public URL· http get/ → “ample canary next js patterns”  
✓ versioned-static-assets self-test from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”

## Evidence

1. November 5, 2026 · canary run
   
   Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's Cosmetic dentistry schema and workflow below build on that verified basis.

## Tested examples

- **Next.js pattern fixture.** Verified public web service basis for this blueprint.

## What it doesn’t cover

- The technical basis (public web service on Next.js) was verified with the pattern fixture; the cosmetic dentistry schema and workflow are an original design for this blueprint, built on that basis.
- Case photographs are patient data; publish only with documented consent and de-identification.
- Verified on the node-22 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture); `ample bucket upload-url` returns presigned upload URLs.
