Oral surgery: company website using Next.js

Summary

A company website blueprint for oral surgery built with Next.js on Ample. Domain schema: procedures (code, name, description, anesthesia_options, recovery_days): extractions, implants and corrective surgery; pre_op_instructions (procedure_id, instructions, fasting_rules): public preparation guidance; post_op_instructions (procedure_id, instructions, warning_signs): public recovery guidance; locations (name, address, phone, opening_hours, emergency_line): surgery locations; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: procedure catalog with recovery expectations, pre- and post-operative instructions, emergency contact per location. Kept out of scope until handling is reviewed: surgical records and consent forms, medication lists, insurance pre-authorizations. Surgical and medication records are health data; only public guidance belongs here. No compliance is claimed. 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.

Representative Queries

• Oral surgery: company website using Next.js
• Where can I host Oral surgery: Company website built with Next.js?
• I need a genuinely specialized company website workflow covering public procedure-category content and referral-contact directory; no clinical referrals.

Resource Requirements

• primitive:compute
• primitive:cdn

Infrastructure Requirements

• Compute
  Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.
• CDN
  The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.

Workflow Steps

1. Model the oral surgery domain
   Create the tables procedures, pre_op_instructions, post_op_instructions, locations, asset_versions. Extractions, implants and corrective surgery lives in procedures; keep the sensitive classes (surgical records and consent forms, medication lists, insurance pre-authorizations) 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  --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 oral surgery workflow.

   ample logs --kind build
   

Success Checks

• app responds on its public URL
  • kind: http_get
  • path: /
  • expect: ample canary next js patterns
• versioned-static-assets self-test from the example
  • kind: http_get
  • path: /p/versioned-static-assets
  • expect: see the pattern fixture checks

Limitations

• The technical basis (public web service on Next.js) was verified with the pattern fixture; the oral surgery schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Surgical and medication records are health data; only public guidance belongs here. No compliance is claimed.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the node-22 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Evidence Summary

• Kind: canary_run
  Summary: 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 Oral surgery schema and workflow below build on that verified basis and were not separately executed. Observed At: 2026-09-21T02:34:39Z

Next Actions

• Action: Browse the catalog index
  Method: GET
  Relative Path: /v1/catalog
• Action: Search published recipes by intent, stack and constraints
  Method: POST
  Relative Path: /v1/catalog/search
• Action: Prepare a side-effect-free deployment plan for an authorized project
  Method: POST
  Relative Path: /v1/catalog/plan