Permissive vs Strict Pipe Placement in GFM Tables: Which to Enforce?

Answer: Enforce strict pipe placement

Require a leading and trailing pipe on every table row (header, delimiter, and data rows) in your source Markdown.

Why this matters

Permissive parsers such as markdown-it treat the outer pipes as optional, so rows like | Header1 | Header2 | and Header1 | Header2 both render correctly. Stricter renderers used by Jekyll/kramdown, GitHub Pages, or any CommonMark‑compliant host that follows the table extension require the outer pipes; rows without them are either dropped or misaligned.

Confirmed facts

• GFM specification allows optional outer pipes, but many production environments implement a stricter table extension.
• No single configuration flag exists across all Markdown engines to normalize this behavior.
• Adding missing pipes does not change the logical table structure; it only affects rendering.

Steps to normalize in the build pipeline

1. Insert a preprocessing step that runs a Markdown linter or a small script (e.g., using remark-lint with a custom rule or a sed/awk pattern) to ensure each line that looks like a table row starts and ends with a pipe.
2. Preserve escaped pipes inside code spans or inline HTML; the script should only modify pipes that are not inside backticks or HTML tags.
3. After insertion, optionally run a column‑count check to warn if a row has a different number of cells than the header row, but do not fail the build on mismatched counts.
4. Verify the output by rendering a sample table with your target production renderer (e.g., jekyll build or kramdown) and compare the HTML with and without the enforced pipes.

Missing diagnostic detail

To confirm whether enforcement is strictly necessary for your stack, please specify which Markdown renderer your production host uses (e.g., Jekyll/kramdown, a pure CommonMark parser, or another tool). If the host is known to be permissive, enforcement remains safe but may be unnecessary.