poocommerce-markdown

Run `markdownlint --fix` from the repository root to automatically correct formatting issues, then run `markdownlint` to verify compliance. This enforces ATX heading style, 4-space list indentation, language-specified code blocks, blank lines around blocks, UTF-8 encoding, and trailing newlines across all markdown files.

PooCommerce markdown requires ATX heading style, 4-space indentation for lists, language-specified code blocks with blank lines before and after, UTF-8 encoding, and a trailing newline at the end of files. These standards apply to all documentation, README files, and in-code markdown content.

Wrap code blocks with triple backticks and specify the language (e.g., ```javascript), add blank lines before and after the block, and ensure proper indentation. Language specification helps both readability and AI parsing of documentation.

Yes. The `markdownlint --fix` command automatically corrects common markdown formatting issues like indentation, missing blank lines, and heading style. Run it from your repository root to apply fixes across all markdown files before manual review.

Use UTF-8 encoding for all markdown files in PooCommerce documentation. This ensures consistent character handling across the repository and proper rendering in all environments and tools.

Run `markdownlint --fix` after writing or updating any markdown content, then run `markdownlint` to verify compliance before committing. This catches formatting inconsistencies early and maintains documentation quality standards across the project.