# Pediatric dentistry: company website using Laravel

## Summary
A company website blueprint for pediatric dentistry built with Laravel on Ample. Domain schema: services (code, name, age_range, description): age-appropriate services; first_visit_guides (age_range, checklist, what_parents_bring): public preparation guidance; locations (name, address, phone, opening_hours, child_facilities): practice locations; providers (name, registration_number, pediatric_certification): clinicians; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: services by age range, first-visit guidance, locations with child facilities, provider credentials. Kept out of scope until handling is reviewed: minor patient identity and guardians, clinical records, school and consent forms. Data about minors is doubly sensitive; only public practice information belongs in these workflows. No compliance is claimed.

## Technical basis
Verified on Laravel: 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
- Pediatric dentistry: company website using Laravel
- Where can I host Pediatric dentistry: Company website built with Laravel?
- I need a genuinely specialized company website workflow covering public age-group content navigation and caregiver-facing information; no child records.

## Resource Requirements
- primitive: compute
- primitive: cdn

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

## Framework
Laravel

## Workload
Company website

## Industry
Pediatric dentistry

## Release Status
Published

## Support Status
Verified

## Execution Status
Ready

## Docs Only
False

## Prerequisites
- A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ (php-server with the index.php fallback) reading PORT on the php-8.5 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 pediatric dentistry data classes may be handled at all; this blueprint models public information only

## Workflow Steps
1. **Model the pediatric dentistry domain** - Create the tables services, first_visit_guides, locations, providers, asset_versions. Age-appropriate services lives in services; keep the sensitive classes (minor patient identity and guardians, clinical records, school and consent forms) 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. Command: 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 pediatric dentistry workflow. Command: ample logs  --kind build.

## Examples
- **Laravel pattern fixture** - Verified public web service basis for this blueprint.

## Success Checks
1. app responds on its public URL
2. versioned-static-assets self-test from the example

## Limitations
- The technical basis (public web service on Laravel) was verified with the pattern fixture; the pediatric dentistry 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.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.

## 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
- A 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.

---