Recommended source format
Markdown is the source of truth for a PostRout post. A well-structured source gives the generator reliable content boundaries and makes the resulting channel versions easier to review.
---
title: "A practical guide to content routing"
description: "How to adapt one source for several publishing channels."
tags:
- publishing
- markdown
canonical_url: "https://example.com/content-routing"
---
# A practical guide to content routing
Start with a short introduction that states the reader's problem.
## Build one reliable source
Use descriptive headings, complete links, and fenced code blocks.
```ts
const destination = "dev-community";
```Formatting guidance
- Use one H1 title and organize the body with H2 and H3 headings.
- Use fenced code blocks and include a language when known.
- Use descriptive link text instead of raw URLs when possible.
- Give images useful alt text and verify that their URLs are publicly accessible.
- Keep the canonical URL pointed at the preferred original source.
- Treat tags as destination suggestions; each platform may enforce its own limits.
Before generation
- Remove private notes, credentials, placeholders, and unpublished customer information.
- Check that product names, facts, dates, and links are current.
- Make the main takeaway explicit rather than expecting the generator to infer it.
- Preserve important qualifications and citations in the source.