# Blade includes vs components: how we decide

Page: https://stenobird.com/podcast/no-compromises-1309932/blade-includes-vs-components-how-we-decide
Text version: https://stenobird.com/podcast/no-compromises-1309932/blade-includes-vs-components-how-we-decide.md
Podcast: [No Compromises](https://stenobird.com/podcast/no-compromises-1309932)
Published: 2025-08-16T05:00:00+00:00
Episode link: https://share.transistor.fm/s/e1200f77
Audio file: https://media.transistor.fm/e1200f77/7ce8d839.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/blade-includes-vs-components-how-we-decide
Duration seconds: 955

## Resource

Blade gives you two big levers for keeping views maintainable: @include and Blade components. When should you use one versus the other? Does it matter? In the latest episode of the No Compromises podcast, we lay out a clear heuristic for when to extract markup for organization (includes) versus when to encapsulate and reuse with controlled scope (components). We also touch on scope pitfalls, “passing for documentation,” and why performance worries usually lie elsewhere. Sign up for the free Mastering Laravel newsletter . The highest value-to-time ratio you will find.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/blade-includes-vs-components-how-we-decide/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/no-compromises-1309932/blade-includes-vs-components-how-we-decide.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.