Cheat sheets

# 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: Cheat sheets
- url: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/resources-cheatsheets/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: navigation
- topic: library-shelves
- description: Glanceable facts, commands, and IDs — lookup, not narrative.

## 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.

---

# Cheat sheets

<p class="eyebrow">Resources · cheat sheet</p>

:::start
**You are here:** [Resources](/zajlibrary/navigation/library-shelves/resources/reference/resources/) → **Cheat sheets**
**This type is for you if:** you need commands, IDs, or tables at a glance — no story.
**Not this?** [Guides](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) = narrative how-to · [Reference](/zajlibrary/navigation/library-shelves/resources/reference/resources-reference/) = site authoring docs.
:::

## The map

```mermaid
graph LR
  CH["Cheat sheet"] --> Lookup["Glanceable facts"]
  G["Guide"] --> Story["Read top to bottom"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel · Operations"
    description="Deploy commands, customization decision tree, and gotchas — glanceable cards for CodeCanyon Laravel."
    href="/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/"
  />
</CardGrid>

## Available cheat sheets

| Category | Cards | Hub |
| --- | --- | --- |
| [Laravel · Operations](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) | 3 | [Open hub →](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) |

<CardGrid>
  <LinkCard title="Component library" description="Starlight components quick reference for authors." href="/zajlibrary/authoring/content-system/resources/reference/component-library/" />
  <LinkCard title="Authoring capabilities" description="Plugin and token inventory." href="/zajlibrary/authoring/content-system/resources/reference/authoring-capabilities/" />
</CardGrid>

<details>
<summary>Understand everything — cheat sheet shape</summary>

Cheat sheets stay **single-file** — almost never a folder. Command crib sheets, glossaries, ID tables. If it needs diagrams and sections, it's probably a [guide](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) or [handbook](/zajlibrary/navigation/library-shelves/resources/reference/learn-handbooks/) page instead.
</details>

# Cheat sheets

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

<p class="eyebrow">Resources · cheat sheet</p>

:::start
**You are here:** [Resources](/zajlibrary/navigation/library-shelves/resources/reference/resources/) → **Cheat sheets**
**This type is for you if:** you need commands, IDs, or tables at a glance — no story.
**Not this?** [Guides](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) = narrative how-to · [Reference](/zajlibrary/navigation/library-shelves/resources/reference/resources-reference/) = site authoring docs.
:::

## The map

```mermaid
graph LR
  CH["Cheat sheet"] --> Lookup["Glanceable facts"]
  G["Guide"] --> Story["Read top to bottom"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel · Operations"
    description="Deploy commands, customization decision tree, and gotchas — glanceable cards for CodeCanyon Laravel."
    href="/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/"
  />
</CardGrid>

## Available cheat sheets

| Category | Cards | Hub |
| --- | --- | --- |
| [Laravel · Operations](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) | 3 | [Open hub →](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) |

<CardGrid>
  <LinkCard title="Component library" description="Starlight components quick reference for authors." href="/zajlibrary/authoring/content-system/resources/reference/component-library/" />
  <LinkCard title="Authoring capabilities" description="Plugin and token inventory." href="/zajlibrary/authoring/content-system/resources/reference/authoring-capabilities/" />
</CardGrid>

<details>
<summary>Understand everything — cheat sheet shape</summary>

Cheat sheets stay **single-file** — almost never a folder. Command crib sheets, glossaries, ID tables. If it needs diagrams and sections, it's probably a [guide](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) or [handbook](/zajlibrary/navigation/library-shelves/resources/reference/learn-handbooks/) page instead.
</details>

Resources · cheat sheet

You are here: Resources → Cheat sheets This type is for you if: you need commands, IDs, or tables at a glance — no story. Not this? Guides = narrative how-to · Reference = site authoring docs.

The map

graph LR
  CH["Cheat sheet"] --> Lookup["Glanceable facts"]
  G["Guide"] --> Story["Read top to bottom"]

Start here

Laravel · Operations Deploy commands, customization decision tree, and gotchas — glanceable cards for CodeCanyon Laravel.

Available cheat sheets

Category	Cards	Hub
Laravel · Operations	3	Open hub →

Component library Starlight components quick reference for authors.

Authoring capabilities Plugin and token inventory.

Understand everything — cheat sheet shape

Cheat sheets stay single-file — almost never a folder. Command crib sheets, glossaries, ID tables. If it needs diagrams and sections, it’s probably a guide or handbook page instead.

# 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: Cheat sheets
- url: https://library.zajapps.com/zajlibrary/navigation/library-shelves/resources/reference/resources-cheatsheets/
- shelf: Resources
- doc_type: authoring reference
- status: current
- kind: reference
- category: zajlibrary
- subcategory: navigation
- topic: library-shelves
- description: Glanceable facts, commands, and IDs — lookup, not narrative.

## 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.

---

# Cheat sheets

<p class="eyebrow">Resources · cheat sheet</p>

:::start
**You are here:** [Resources](/zajlibrary/navigation/library-shelves/resources/reference/resources/) → **Cheat sheets**
**This type is for you if:** you need commands, IDs, or tables at a glance — no story.
**Not this?** [Guides](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) = narrative how-to · [Reference](/zajlibrary/navigation/library-shelves/resources/reference/resources-reference/) = site authoring docs.
:::

## The map

```mermaid
graph LR
  CH["Cheat sheet"] --> Lookup["Glanceable facts"]
  G["Guide"] --> Story["Read top to bottom"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel · Operations"
    description="Deploy commands, customization decision tree, and gotchas — glanceable cards for CodeCanyon Laravel."
    href="/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/"
  />
</CardGrid>

## Available cheat sheets

| Category | Cards | Hub |
| --- | --- | --- |
| [Laravel · Operations](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) | 3 | [Open hub →](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) |

<CardGrid>
  <LinkCard title="Component library" description="Starlight components quick reference for authors." href="/zajlibrary/authoring/content-system/resources/reference/component-library/" />
  <LinkCard title="Authoring capabilities" description="Plugin and token inventory." href="/zajlibrary/authoring/content-system/resources/reference/authoring-capabilities/" />
</CardGrid>

<details>
<summary>Understand everything — cheat sheet shape</summary>

Cheat sheets stay **single-file** — almost never a folder. Command crib sheets, glossaries, ID tables. If it needs diagrams and sections, it's probably a [guide](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) or [handbook](/zajlibrary/navigation/library-shelves/resources/reference/learn-handbooks/) page instead.
</details>

# Cheat sheets

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

<p class="eyebrow">Resources · cheat sheet</p>

:::start
**You are here:** [Resources](/zajlibrary/navigation/library-shelves/resources/reference/resources/) → **Cheat sheets**
**This type is for you if:** you need commands, IDs, or tables at a glance — no story.
**Not this?** [Guides](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) = narrative how-to · [Reference](/zajlibrary/navigation/library-shelves/resources/reference/resources-reference/) = site authoring docs.
:::

## The map

```mermaid
graph LR
  CH["Cheat sheet"] --> Lookup["Glanceable facts"]
  G["Guide"] --> Story["Read top to bottom"]
```

---

## Start here

<CardGrid>
  <LinkCard
    title="Laravel · Operations"
    description="Deploy commands, customization decision tree, and gotchas — glanceable cards for CodeCanyon Laravel."
    href="/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/"
  />
</CardGrid>

## Available cheat sheets

| Category | Cards | Hub |
| --- | --- | --- |
| [Laravel · Operations](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) | 3 | [Open hub →](/tech-stack/laravel/codecanyon/resources/cheatsheets/operations/) |

<CardGrid>
  <LinkCard title="Component library" description="Starlight components quick reference for authors." href="/zajlibrary/authoring/content-system/resources/reference/component-library/" />
  <LinkCard title="Authoring capabilities" description="Plugin and token inventory." href="/zajlibrary/authoring/content-system/resources/reference/authoring-capabilities/" />
</CardGrid>

<details>
<summary>Understand everything — cheat sheet shape</summary>

Cheat sheets stay **single-file** — almost never a folder. Command crib sheets, glossaries, ID tables. If it needs diagrams and sections, it's probably a [guide](/zajlibrary/navigation/library-shelves/resources/reference/learn-guides/) or [handbook](/zajlibrary/navigation/library-shelves/resources/reference/learn-handbooks/) page instead.
</details>