Development record
abcd's README parts cannot form a centred header. Each part is written as its own paragraph, so the three badges stack on three lines and cannot join a centred badge row written in HTML, and links and contents are always bulleted lists. With no Markdown level-one heading, the first absent part goes to the very top of the file. In abcd's own README, choosing all six parts put six blocks above the centred logo and title, with a second release badge, so the README was rewritten by hand and the parts turned off.
issueresolvedminoriss-2610311544004033
abcd's README parts cannot form a centred header. Each part is written as its own paragraph, so the three badges stack on three lines and cannot join a centred badge row written in HTML, and links and contents are always bulleted lists. With no Markdown level-one heading, the first absent part goes to the very top of the file. In abcd's own README, choosing all six parts put six blocks above the centred logo and title, with a second release badge, so the README was rewritten by hand and the parts turned off.
Grounds
- pursued: a part placed inside a centred HTML header renders as a badge or link there, and setup fills abcd's layout-C header with the same rows in the same order; shown wrong if a part inside a <p> or <div> block is written as Markdown, an absent part lands above an HTML <h1>, a removal or insertion adds a blank line inside the block, or a second setup run rewrites the README.
Frontmatter
| id | iss-2610311544004033 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610311544004033-readme-parts-cannot-join-a-centred.md
open on GitHub ↗ · commit history ↗
mentions4
- dcn-26103120050216682026-10-31 — iss-2610311544004033, facilitator on delegation: the inline form is chosen by where the owner puts a part, not by a new setting or flag. A part whose opening mark is a continuation line of an open block-level HTML block (CommonMark types 6 and 7, such as a `<p>` or `<div>` block, which run to the next blank line) is written as HTML, because Markdown inside an HTML block is never rendered; a part anywhere else is written as today. Grounds: CommonMark 0.31 HTML block rules; a body that cannot render where it stands is a defect, not a preference.
- dcn-26103120050378462026-10-31 — iss-2610311544004033, facilitator on delegation: placement. An absent part whose nearest present part is inline goes on the line beside it, with no blank line between, in the inline form, so it joins the same HTML block. With no part present, an absent part goes after a leading frontmatter block, else after the first live level-one heading, a Markdown # line or an HTML `<h1>` line outside every code fence, else at the top; there it is written in block form, set off by blank lines. Removing an inline part leaves no blank line in the block it sat in.
- dcn-26103120050381172026-10-31 — iss-2610311544004033, facilitator on delegation: inline bodies. A badge is one line, an `<a href>` around an `<img src alt>`, with every attribute value HTML-escaped. Links, licence and contents are each one line of `<a>` links joined by a spaced middle dot. Inline links use short labels (Changelog, Contributing, Security, Code of conduct); the inline licence links the identifier and the word licence (MIT licence), or Licence when abcd cannot name it; inline contents lists level-two headings only so it stays one line, a heading with an unsure anchor shown as plain escaped text.
- dcn-26103120050404872026-10-31 — iss-2610311544004033, facilitator on delegation: abcd's own README keeps the layout-C header the person chose. Its badge rows are wrapped in one `<p>` block, and readme.parts is release-badge, build-badge, abcd-badge, licence and links, each placed where layout C shows it, so the result renders as the hand-written header does. contents is left out: layout C's link line replaces the contents list, and its Install and First run links stay hand-written.