woocommerce-markdown

Lint after edits; use ATX headings, 4-space lists, and language-specified code blocks.

• Guidelines for creating and modifying markdown files in WooCommerce
• Enforces strict formatting rules via markdownlint
• Applies to all markdown content including READMEs and changelogs

• Always lint after changes with `markdownlint --fix` then `markdownlint`
• Run from repository root to load configuration
• Use UTF-8 encoding for directory trees and special chars
• Follow ATX heading style (no underline)
• Lists must be 4-space indented with blank lines before/after
• Code blocks must specify language and have blank lines around them
• Emphasis cannot be used as headings
• No hard tabs or trailing whitespace rules

1. 1.Edit markdown file
2. 2.Run `markdownlint --fix` then `markdownlint` to verify
3. 3.Fix remaining issues manually
4. 4.Commit changes only after clean lint output
5. 5.Use correct heading hierarchy and language in code blocks
6. 6.Ensure files end with single newline