page:blueprints:endodontics:campaign site:next js
Endodontics: campaign site using Next.js
A campaign site blueprint for endodontics built with Next.js on Ample. Domain schema:
- procedures (code, name, description, typical_visits): root canal and retreatment procedures;
- referral_guides (procedure_id, referring_dentist_checklist, imaging_needed): public guidance for referring practices;
- locations (name, address, phone, opening_hours): clinic locations;
- endodontists (name, registration_number, technologies): specialists and equipment listed publicly;
- asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.
Public information: procedure catalog, referral guidance for general dentists, specialist profiles and technology, locations. Kept out of scope until handling is reviewed: referral letters with patient identity, imaging files, clinical notes. Referral documents carry patient identity; keep them out of these workflows until handling is reviewed. 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
- Endodontics: campaign site using Next.js
- Where can I host Endodontics: Campaign site built with Next.js?
- I need a genuinely specialized campaign site workflow covering public specialty pages and practice contact routing; no patient intake.
Workflow Steps
- Model the endodontics domain
Create the tables procedures, referral_guides, locations, endodontists, asset_versions. Root canal and retreatment procedures live in procedures; keep the sensitive classes (referral letters with patient identity, imaging files, clinical notes) out of this schema. - Workflow step 1
Model the campaign's offers and locations as tables with start and end dates. - Workflow step 2
Build the site and publish versioned static assets to the CDN bucket. - Workflow step 3
Collect no personal data on the site itself; hand off to an authorized system. - Workflow step 4
Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date. - Deploy
Run the synchronous deploy once and read the result. Re-running with no change is a no-op.ample deploy . --name <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=... - Verify
Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the endodontics workflow.ample logs <your logs option> --kind build
Success Checks
- App responds on its public URL.
- Versioned-static-assets self-test from the example.
Limitations
- The technical basis (public web service on Next.js) was verified with the pattern fixture; the endodontics 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. Referral documents carry patient identity; keep them out of these workflows until handling is reviewed. 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.00
- Basis: size prices from pricing.toml
- Components:
- app server: s-1vcpu-1gb, 1.0 units, $5.00/month
Evidence Summary
- Next.js pattern fixture deployed on Ample; 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 Endodontics schema and workflow below build on that verified basis and were not separately executed.