# Publishing: Documentation Site Using Laravel

## Summary  
A documentation site blueprint for publishing built with Laravel on Ample.  
**Domain schema:**  
- **titles** (isbn_or_slug, title, author, imprint, published_at): the catalog of titles  
- **editions** (title_id, format, version, object_key): editions and versioned files  
- **customer_workspaces** (name, license_type, seat_count): institutional or trade customers  
- **customer_assets** (workspace_id, title_id, object_key, license_expires_at): licensed files per customer  
- **state_transitions** (record_type, from_state, to_state): the allowed state machine.  
**Public information:** title catalog and author pages, release schedules, rights and permissions contact.  
**Kept out of scope until handling is reviewed:** unreleased manuscripts, royalty statements, customer license keys.  
**Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace.**  
**Technical basis verified on Laravel:** a workspace-scoped table, an explicit state machine (draft to review to published) that rejects invalid transitions, and a cross-workspace read that returns nothing (transitions=true isolation=true).

## Representative Queries
- Publishing: documentation site using Laravel  
- Where can I host Publishing: Documentation site built with Laravel?  
- I need a genuinely specialized documentation site workflow covering editorial roles, publication versions and rights-scoped assets.

## Workflow Steps
1. **Model the publishing domain**  
   Create the tables titles, editions, customer_workspaces, customer_assets, state_transitions. The catalog of titles lives in titles; keep the sensitive classes (unreleased manuscripts, royalty statements, customer license keys) out of this schema.  
2. **Workflow step 1**  
   Model versioned documents with a state machine (draft, review, published) scoped to a product version  
3. **Workflow step 2**  
   Publish assets for released versions to the CDN bucket  
4. **Workflow step 3**  
   Serve only published versions publicly  
5. **Workflow step 4**  
   Deploy and verify the version list and a published page  
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/relational-records) and your own acceptance checks for the publishing workflow.  
   `ample logs  --kind build`

## Limitations
- The technical basis (relational records on Laravel) was verified with the pattern fixture; the publishing 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. Manuscripts and royalty data are confidential; licensed files are authorized per customer workspace.
- Public content and synthetic examples only until actual data-handling requirements have been reviewed.
- Verified on the php-8.5 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified.
  
## Success Checks
- **App responds on its public URL**
  - Kind: http_get  
  - Path: /  
  - Expect: ample canary laravel patterns
- **Relational-records self-test from the example**  
  - Kind: http_get  
  - Path: /p/relational-records  
  - Expect: see the pattern fixture checks

## Cost Estimate
- **Currency:** USD  
- **Monthly Amount:** 10.0  
- **Basis:** size prices from pricing.toml (loaded by the API) at build revision 1ac5595375130d45290090e82ed0f554ccd45405-dirty

### Components
- **App server**  
  - Size: s-1vcpu-1gb  
  - Quantity: 1.0  
  - Monthly Amount: 5.0  
- **Managed PostgreSQL database**  
  - 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
- **Browse the catalog index**  
  - Operation ID: catalog_index  
  - Method: GET  
  - Relative Path: /v1/catalog

- **Search published recipes by intent, stack and constraints**  
  - Operation ID: search_recipes  
  - Method: POST  
  - Relative Path: /v1/catalog/search  
  - Parameters:  
    - Body: {"limit": 5, "query": "Publishing: documentation site using Laravel"}

- **Prepare a side-effect-free deployment plan for an authorized project**  
  - Operation ID: plan_deployment  
  - Method: POST  
  - Relative Path: /v1/catalog/plan  
  - Parameters:  
    - Body: {"inputs": {}, "projectId": "", "recipeId": "page:blueprints:publishing:documentation-site:laravel", "recipeRevision": "r1"}

\-
- **Read the existing agent authentication setup**  
  - Operation ID: existing_auth_setup  
  - Method: GET  
  - Relative Path: /mcp/setup

- **Browse Publishing**  
  - Operation ID: browse_node  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/industry%3Apublishing

- **Browse Documentation site**  
  - Operation ID: browse_node  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/workload%3Adocumentation-site

- **Browse Laravel**  
  - Operation ID: browse_node  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/stack%3Aframework-laravel

- **Browse Deploy web app**  
  - Operation ID: browse_node  
  - Method: GET  
  - Relative Path: /v1/catalog/nodes/intent%3Adeploy-web-app