Developer tools: documentation site using Laravel

Summary

A documentation site blueprint for developer tools built with Laravel on Ample. Domain schema:

• customer_workspaces (name, plan, api_key_count): customer organizations
• doc_versions (product_version, title, object_key, published_at): versioned reference docs and guides
• sdk_releases (language, version, changelog_object_key, released_at): SDK releases and changelogs
• customer_assets (workspace_id, title, object_key, visibility): customer-specific artifacts
• state_transitions (record_type, from_state, to_state): the allowed state machine.

Public information: versioned API reference and guides, SDK release notes, status page links. Kept out of scope until handling is reviewed: customer API keys and usage logs, private integration details. API keys and usage logs are secrets or personal data; keep them out of documentation workflows.

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

• Developer tools: documentation site using Laravel
• Where can I host Developer tools: Documentation site built with Laravel?
• I need a genuinely specialized documentation site workflow covering organization access, versioned technical docs and build artifacts.

Framework

Laravel

Workload

Documentation site

Industry

Developer tools

Release Status

Published

Support Status

Verified

Execution Status

Ready

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)
• A PostgreSQL driver reading DATABASE_URL (auto-provisioned when omitted)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which developer tools data classes may be handled at all; this blueprint models public information only

Tested Configuration

• Template: php-8.5
• Runtime: php
• Size: s-1vcpu-1gb
• Install: composer install --no-dev --prefer-dist --no-interaction --no-progress --optimize-autoloader
• Start: frankenphp php-server --listen :$PORT --root public

Next Actions

1. Browse the catalog index
   • Operation: GET /v1/catalog
2. Search published recipes by intent, stack and constraints
   • Operation: POST /v1/catalog/search
   • Parameters: {"body":{"limit":5,"query":"Developer tools: documentation site using Laravel"}}
3. Prepare a side-effect-free deployment plan for an authorized project
   • Operation: POST /v1/catalog/plan
   • Parameters: {"body":{"inputs":{},"projectId":"","recipeId":"page:blueprints:developer-tools:documentation-site:laravel","recipeRevision":"r1"}}
4. Read the existing agent authentication setup
   • Operation: GET /mcp/setup
5. Browse Developer tools
   • Operation: GET /v1/catalog/nodes/industry%3Adeveloper-tools
6. Browse Documentation site
   • Operation: GET /v1/catalog/nodes/workload%3Adocumentation-site
7. Browse Laravel
   • Operation: GET /v1/catalog/nodes/stack%3Aframework-laravel
8. Browse Deploy web app
   • Operation: GET /v1/catalog/nodes/intent%3Adeploy-web-app