page:blueprints:general dentistry:knowledge base:laravel

General dentistry: Knowledge Base using Laravel

A knowledge base blueprint for general dentistry built with Laravel on Ample. Domain schema:

• services (code, name, description, duration_minutes, price_from): the treatments a practice offers;
• locations (name, address, phone, opening_hours, accessibility_notes): each practice location;
• dentists (name, registration_number, specialties, location_id): the clinicians listed publicly;
• insurance_plans (name, accepted_at_location_id): plans accepted per location;
• asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket.

Public Information:

• Service catalog with prices, locations, hours and parking, clinician profiles, and accepted insurance plans.

Kept out of scope until handling is reviewed: patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed; nothing here establishes compliance.

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

• General dentistry: knowledge base using Laravel
• Where can I host General dentistry: Knowledge base built with Laravel?
• I need a genuinely specialized knowledge base workflow covering public service catalog and location-specific information; no patient data.

Framework and Workload

• Framework: Laravel
• Workload: Knowledge base
• Industry: General dentistry

Resource Requirements

• Compute: Verified
• CDN: Verified

Prerequisites

• A Laravel project (composer install --no-dev from composer.lock, then FrankenPHP serving public/ 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 general dentistry data classes may be handled at all; this blueprint models public information only.

Workflow Steps

1. Model the general dentistry domain: Create the tables services, locations, dentists, insurance_plans, asset_versions. Keep sensitive classes out of this schema.
2. Workflow step 1: Model articles and categories as tables keyed to the public catalog entities.
3. Workflow step 2: Build the site with versioned assets served from the CDN bucket.
4. Workflow step 3: Keep articles free of any sensitive data class.
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.
   • 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 and your own acceptance checks.
   • Command: ample logs --kind build

Examples

• Laravel pattern fixture: Verified public web service basis for this blueprint.
  • Source Ref: tests/deploy-canaries/laravel-patterns

Success Checks

1. App responds on its public URL:
   • Kind: http_get
   • Path: /
   • Expect: ample canary laravel patterns
2. 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 was verified with the pattern fixture; the general dentistry schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No compliance claims made; patient data should be kept out of these workflows until handling requirements have been reviewed.
• Verified on the php-8.5 template; other size limits are unknown or unverified.
• PutObject and GetObject operations are verified; other S3 operations are not.

Cost Estimate

• Currency: USD
• Monthly Amount: 5.0
• Basis: size prices from pricing.toml at build revision
• Components:
  • App server, size: s-1vcpu-1gb, quantity: 1.0, 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.

Next Actions

1. Browse the catalog index: GET /v1/catalog.
2. Search published recipes by intent, stack and constraints: POST /v1/catalog/search with query: General dentistry: knowledge base using Laravel.
3. Prepare a deployment plan: POST /v1/catalog/plan.
4. Read existing agent authentication setup: GET /mcp/setup.
5. Browse General dentistry: GET /v1/catalog/nodes/industry%3Ageneral-dentistry.
6. Browse Knowledge base: GET /v1/catalog/nodes/workload%3Aknowledge-base.
7. Browse Laravel: GET /v1/catalog/nodes/stack%3Aframework-laravel.
8. Browse Deploy web app: GET /v1/catalog/nodes/intent%3Adeploy-web-app.