Asset starter hub template

When to use

• Path: <category>/<subcategory>/<topic>/resources/templates/<bundle>/index.mdx (hub) + sibling leaf pages per file
• Not page-authoring templates (meta/page-templates/) — these are project files to copy
• Diátaxis mode: reference (which file to copy when)
• Readers served: operators grabbing Deployer/env snippets during playbook phases

Design rationale

• One asset per leaf page — reference docs should be atomic for copy-paste (Diátaxis reference).
• Hub explains when to use each file — context lives on hub; leaf is the artifact (Google code sample intro pattern).
• Link to playbook for why — asset templates don’t re-teach deployment (separation of concerns).
• Distinct from kit pages — single-file starters vs multi-file bundles + seed.sh (templates vs kits).

Copy-paste skeleton (hub)

---
title: "<Topic> deployment starters"
description: Copy-paste starter files for &lt;operation&gt; — link to playbook for context.
kind: template
status: current
tags: [template, topic]
---

<p class="eyebrow">Resources · asset starters · &lt;topic&gt;</p>

Use these **single files** during [Playbook phase](/tech-stack/laravel/codecanyon/build/playbooks/setup-new/04-deploy-pipeline/). For full agent setup, see [Kits](/zajlibrary/navigation/library-shelves/resources/reference/resources-kits/).

| File | When to use | Page |
| --- | --- | --- |
| Deployer recipe | Phase 4 pipeline | [01-deployer](/tech-stack/laravel/codecanyon/resources/templates/deployment/01-deployer/) |

Copy-paste skeleton (leaf)

---
title: "Deployer starter"
description: …
kind: template
format: code
---

## When to copy

<Playbook step link.>

## File

\`\`\`php
// paste-ready content
\`\`\`

## Customize

| Key | You set |
| --- | --- |

Anti-patterns

• Do not put multi-file install procedures here — use a kit page.
• Do not use playbook step spine on asset leaf pages.

Worked example

• Laravel deployment starters

Sources

• Diátaxis — Reference documentation — atomic lookup files.
• Google developer documentation style guide — Code samples — context before sample.
• Good Docs Project — Templates — reusable starter artifacts.
• Writing style → Doc-type spines