Checklists

# ZajLibrary — authoring reference

You are a **hands-on assistant**. You help the user adapt and use the authoring reference below in their own project.

**Mission:** Help the user adapt and use the authoring reference below in their own project, keeping its structure intact.

## Metadata
- title: Checklists
- url: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/build-checklists/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: navigation
- topic: library-shelves
- description: Verify you completed every step.

## How to use this page
- Treat the body as a reusable artifact: help fill it in, tailor it, or apply it to the user’s project while keeping its structure intact.
- Stay practical — prefer the page’s commands, tables, and snippets over re-explaining theory.
- Cite section headings when pointing to a specific part.

---

# Checklists

<p class="eyebrow">Build · checklist</p>

:::start
**You are here:** [Build](/zajlibrary/navigation/library-shelves/resources/reference/build/) → **Checklists**
**This type is for you if:** you need a binary gate list — pre-merge, pre-deploy, launch sign-off.
**Not this?** [Playbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-playbooks/) = narrative + phases · [Runbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-runbooks/) = command sequence.
:::

## The map

```mermaid
graph LR
  CL["Checklist"] --> Gate["Gate"]
  Gate --> Yes["All items checked"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel/CodeCanyon — Checklists"
    description="Launch and post-launch sign-off gates — distilled tick-box verification for the setup-new playbook."
    href="/tech-stack/laravel/codecanyon/build/checklists/"
  />
</CardGrid>

## Available checklists

| Category | Status | Hub |
| --- | --- | --- |
| [Laravel/CodeCanyon](/tech-stack/laravel/codecanyon/build/checklists/) | In progress | [Open hub →](/tech-stack/laravel/codecanyon/build/checklists/) |

Until standalone checklist pages land, the heaviest gates still live inside the playbook:

<CardGrid>
  <LinkCard title="Phase 10 · Audit & QA sign-off" description="Pre-launch audit gate inside setup-new." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/" />
  <LinkCard title="Phase 11 · Pre-customer" description="Business go/no-go before first customer." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/" />
</CardGrid>

<details>
<summary>Understand everything — checklist shape</summary>

Checklists are almost always **one file** — a list of verifiable items. Link them from playbook phase gates when the same list is reused across projects.
</details>

# Checklists

> Source: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/build-checklists/

<p class="eyebrow">Build · checklist</p>

:::start
**You are here:** [Build](/zajlibrary/navigation/library-shelves/resources/reference/build/) → **Checklists**
**This type is for you if:** you need a binary gate list — pre-merge, pre-deploy, launch sign-off.
**Not this?** [Playbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-playbooks/) = narrative + phases · [Runbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-runbooks/) = command sequence.
:::

## The map

```mermaid
graph LR
  CL["Checklist"] --> Gate["Gate"]
  Gate --> Yes["All items checked"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel/CodeCanyon — Checklists"
    description="Launch and post-launch sign-off gates — distilled tick-box verification for the setup-new playbook."
    href="/tech-stack/laravel/codecanyon/build/checklists/"
  />
</CardGrid>

## Available checklists

| Category | Status | Hub |
| --- | --- | --- |
| [Laravel/CodeCanyon](/tech-stack/laravel/codecanyon/build/checklists/) | In progress | [Open hub →](/tech-stack/laravel/codecanyon/build/checklists/) |

Until standalone checklist pages land, the heaviest gates still live inside the playbook:

<CardGrid>
  <LinkCard title="Phase 10 · Audit & QA sign-off" description="Pre-launch audit gate inside setup-new." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/" />
  <LinkCard title="Phase 11 · Pre-customer" description="Business go/no-go before first customer." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/" />
</CardGrid>

<details>
<summary>Understand everything — checklist shape</summary>

Checklists are almost always **one file** — a list of verifiable items. Link them from playbook phase gates when the same list is reused across projects.
</details>

Build · checklist

You are here: Build → Checklists This type is for you if: you need a binary gate list — pre-merge, pre-deploy, launch sign-off. Not this? Playbooks = narrative + phases · Runbooks = command sequence.

The map

graph LR
  CL["Checklist"] --> Gate["Gate"]
  Gate --> Yes["All items checked"]

Start here

Laravel/CodeCanyon — Checklists Launch and post-launch sign-off gates — distilled tick-box verification for the setup-new playbook.

Available checklists

Category	Status	Hub
Laravel/CodeCanyon	In progress	Open hub →

Until standalone checklist pages land, the heaviest gates still live inside the playbook:

Phase 10 · Audit & QA sign-off Pre-launch audit gate inside setup-new.

Phase 11 · Pre-customer Business go/no-go before first customer.

Understand everything — checklist shape

Checklists are almost always one file — a list of verifiable items. Link them from playbook phase gates when the same list is reused across projects.

# ZajLibrary — authoring reference

You are a **hands-on assistant**. You help the user adapt and use the authoring reference below in their own project.

**Mission:** Help the user adapt and use the authoring reference below in their own project, keeping its structure intact.

## Metadata
- title: Checklists
- url: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/build-checklists/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: navigation
- topic: library-shelves
- description: Verify you completed every step.

## How to use this page
- Treat the body as a reusable artifact: help fill it in, tailor it, or apply it to the user’s project while keeping its structure intact.
- Stay practical — prefer the page’s commands, tables, and snippets over re-explaining theory.
- Cite section headings when pointing to a specific part.

---

# Checklists

<p class="eyebrow">Build · checklist</p>

:::start
**You are here:** [Build](/zajlibrary/navigation/library-shelves/resources/reference/build/) → **Checklists**
**This type is for you if:** you need a binary gate list — pre-merge, pre-deploy, launch sign-off.
**Not this?** [Playbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-playbooks/) = narrative + phases · [Runbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-runbooks/) = command sequence.
:::

## The map

```mermaid
graph LR
  CL["Checklist"] --> Gate["Gate"]
  Gate --> Yes["All items checked"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel/CodeCanyon — Checklists"
    description="Launch and post-launch sign-off gates — distilled tick-box verification for the setup-new playbook."
    href="/tech-stack/laravel/codecanyon/build/checklists/"
  />
</CardGrid>

## Available checklists

| Category | Status | Hub |
| --- | --- | --- |
| [Laravel/CodeCanyon](/tech-stack/laravel/codecanyon/build/checklists/) | In progress | [Open hub →](/tech-stack/laravel/codecanyon/build/checklists/) |

Until standalone checklist pages land, the heaviest gates still live inside the playbook:

<CardGrid>
  <LinkCard title="Phase 10 · Audit & QA sign-off" description="Pre-launch audit gate inside setup-new." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/" />
  <LinkCard title="Phase 11 · Pre-customer" description="Business go/no-go before first customer." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/" />
</CardGrid>

<details>
<summary>Understand everything — checklist shape</summary>

Checklists are almost always **one file** — a list of verifiable items. Link them from playbook phase gates when the same list is reused across projects.
</details>

# Checklists

> Source: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/build-checklists/

<p class="eyebrow">Build · checklist</p>

:::start
**You are here:** [Build](/zajlibrary/navigation/library-shelves/resources/reference/build/) → **Checklists**
**This type is for you if:** you need a binary gate list — pre-merge, pre-deploy, launch sign-off.
**Not this?** [Playbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-playbooks/) = narrative + phases · [Runbooks](/zajlibrary/navigation/library-shelves/resources/reference/build-runbooks/) = command sequence.
:::

## The map

```mermaid
graph LR
  CL["Checklist"] --> Gate["Gate"]
  Gate --> Yes["All items checked"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel/CodeCanyon — Checklists"
    description="Launch and post-launch sign-off gates — distilled tick-box verification for the setup-new playbook."
    href="/tech-stack/laravel/codecanyon/build/checklists/"
  />
</CardGrid>

## Available checklists

| Category | Status | Hub |
| --- | --- | --- |
| [Laravel/CodeCanyon](/tech-stack/laravel/codecanyon/build/checklists/) | In progress | [Open hub →](/tech-stack/laravel/codecanyon/build/checklists/) |

Until standalone checklist pages land, the heaviest gates still live inside the playbook:

<CardGrid>
  <LinkCard title="Phase 10 · Audit & QA sign-off" description="Pre-launch audit gate inside setup-new." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/10-audit-qa/" />
  <LinkCard title="Phase 11 · Pre-customer" description="Business go/no-go before first customer." href="/tech-stack/laravel/codecanyon/build/playbooks/setup-new/11-pre-customer/" />
</CardGrid>

<details>
<summary>Understand everything — checklist shape</summary>

Checklists are almost always **one file** — a list of verifiable items. Link them from playbook phase gates when the same list is reused across projects.
</details>