Skip to content

docs: propose Markdown conventions in CONTRIBUTING - #10108

Open
ump45nose wants to merge 1 commit into
npm:latestfrom
ump45nose:contrib-fix-5522
Open

ump45nose wants to merge 1 commit into
npm:latestfrom
ump45nose:contrib-fix-5522

Conversation

@ump45nose

Copy link
Copy Markdown

Adds a "Markdown Conventions" section to CONTRIBUTING.md (no hard wrapping of prose, one space after a period, leave tool-generated files as generated).

Status / please decide: #5522 asks whether these conventions should exist, and @lukekarrys commented that the team should reach consensus first. This PR proposes one answer (dropping the 80-column hard wrap for prose, as suggested in the issue) so there is something concrete to discuss; I have not changed any existing docs to match. Feel free to close if the team prefers a different convention. Refs #5522.

No tests run (docs only).

AI assistance disclosure: this change was prepared with the help of an AI coding agent (Grok Bot). The account owner has not reviewed every line in detail; please treat it accordingly.

Contributors editing Markdown had no discoverable statement of what
the house style actually is, so the same edits produced different
results depending on who ran them.

Prose in this repository is written one paragraph per line and is not
hard wrapped, and one space follows a sentence period. Document both
norms in CONTRIBUTING.md, the file contributors already read before
opening a pull request.

Also record that the 80-column wrapping in tool-generated files such
as CODE_OF_CONDUCT.md comes from the generator, so it is left alone
rather than "fixed".

Closes: npm#5522
@ump45nose
ump45nose requested a review from a team as a code owner October 10, 2026 09:19
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