Customising stubs

docs:install and make:doc both write markdown files from Blade templates that ship with the package. Publish those templates to control exactly what new pages look like in your project.

#Publishing

php artisan vendor:publish --tag=laradocs-stubs

Two files land in stubs/laradocs/:

The commands always prefer a published stub over the package's copy, so any file you leave in stubs/laradocs/ wins. Delete a file to fall back to the package default.

#Anatomy of a stub

Stubs are compiled with Blade::render(), so the full Blade syntax is available — {{ $title }} for echoes, @if/@foreach for control flow, {!! ... !!} for raw output. Here is the make:doc default trimmed for clarity:

---

title: {{ $title }}
{!! $group !== null ? "group: {$group}" : '# group: Guides' !!}
{!! $order !== null ? "order: {$order}" : '# order: 1' !!}
# description: A short summary used for <meta> tags and SEO
# slug: custom-url
# hidden: true
# ... every other metadata field, commented out

---

# {{ $title }}

Start writing your documentation here.

The inline ternary keeps the rendered front-matter free of blank lines when --group or --order aren't supplied.

#Recipes

#Force every page into a group

---

title: {{ $title }}
group: {{ $group ?? 'Uncategorised' }}
order: {{ $order ?? 999 }}

---

# {{ $title }}

#Stamp every new page with the date

---

title: {{ $title }}
updated_at: {{ now()->toDateString() }}
author: {{ config('app.author', 'Docs Team') }}

---

# {{ $title }}

<!-- created via `php artisan make:doc {{ $name }}` -->

#Pre-populate body content

---

title: {{ $title }}

---

# {{ $title }}

## Overview

Describe what this page covers.

## Example

```php
// code goes here
```

## See also

- [Related page](/docs/related)

#Available metadata

Every key on the Metadata page is valid in a stub. The default stub keeps each one commented out so new authors can uncomment the fields they need without consulting the docs.