phpdocumentor/guides-markdown
Markdown adapter for phpDocumentor Guides. Adds parsing and rendering of Markdown content so documentation projects can mix Markdown pages into the Guides pipeline, supporting common docs workflows and static site generation.
Install via Composer as a development dependency:
composer require --dev phpdocumentor/guides-markdown
Ensure phpdocumentor/guides (v3 or later) is also installed — this package extends the Guides core and requires it. Start by placing Markdown files (e.g., index.md, guide.md) in your documentation source directory (commonly docs/ or resources/docs/). The parser automatically recognizes .md and .markdown extensions and processes them during guide builds via phpdocumentor guide:render. The first use case is straightforward: replace XML or reStructuredText pages with Markdown for simpler authoring while retaining full Guides rendering (PDF, HTML, etc.).
docs/ directory with .md, .rst, and .xml files coexisting — Guides automatically routes each to the correct parser.---
title: Getting Started
weight: 10
---
# Introduction
...
::directive:: syntax — e.g., ::note{type="tip"}This is important:: renders as styled callouts in HTML.phpdocumentor guide:render --config=docs/guide.yml to your build pipeline; Markdown support is transparent — no extra CLI flags needed.@section('content')).--- delimiters at the top of the file — trailing whitespace or extra lines before --- break parsing.<span class="important">) or escape them in raw HTML blocks:
```html
<strong>Not rendered as HTML</strong>
```
[Guide](guide.md) work in source files but resolve only to other Markdown pages by default. Linking to non-Markdown pages requires explicit paths (e.g., [API](api/index.html)).{.language-php} after the fence (e.g., ```php { .no-line-numbers }).league/commonmark, so check its compatibility notes — e.g., strict GFM table parsing changed in v2.0+. Align versions across dependencies if tables break unexpectedly.guide.yml.How can I help you explore Laravel packages today?