Skip to content

docs: capture list-spacing best practice and surface solutions/#19

Open
mairas wants to merge 1 commit into
mainfrom
docs/compound-list-spacing-best-practice
Open

docs: capture list-spacing best practice and surface solutions/#19
mairas wants to merge 1 commit into
mainfrom
docs/compound-list-spacing-best-practice

Conversation

@mairas
Copy link
Copy Markdown
Contributor

@mairas mairas commented May 16, 2026

Summary

Follow-up to #18. Captures the Python-Markdown blank-line-before-lists requirement as a reusable knowledge doc so the rule and the underlying mechanism don't have to be rediscovered next time.

Changes

  • New solutions/best-practices/markdown-lists-need-blank-line-2026-05-16.md — knowledge-track doc explaining why MkDocs/Python-Markdown folds lists into the preceding paragraph without a blank line, with before/after examples and a note on the sane_lists alternative we chose not to enable.
  • solutions/ lives outside docs/ so it doesn't ship to the published site. mkdocs build --strict is unaffected.
  • CLAUDE.md — added the list-spacing rule to Content Guidelines (catches it at authoring time) and a short "Engineering Notes" section pointing at solutions/ so future agents can discover the knowledge store.

Test plan

  • uv run mkdocs build --strict passes (solutions/ is not in docs_dir)
  • CLAUDE.md additions render correctly

🤖 Generated with Claude Code

Document the Python-Markdown blank-line-before-lists requirement
that caused #18, and add a pointer from CLAUDE.md so future agents
discover the solutions/ knowledge store and the rule itself before
authoring new content.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant