Markdown renders as single line in some cases #75

New issue

Open

opened 2026-01-02 10:41:43 +00:00 by mprihoda · 1 comment

mprihoda commented

2026-01-02 10:41:43 +00:00

(Migrated from github.com)

Some Markdown content gets rendered as a single line because standard Markdown doesn't add line breaks without extra spaces. This doesn't look good in the dashboard. Need to find a solution that doesn't require imposing stricter rules on Markdown creation - perhaps a rendering option or CSS fix.

claude commented

2026-10-16 10:52:51 +00:00

Member

Intake: needs-input
Workflow: diagnostic
Reason: G7 (1 [human] finding)
Analysis: project-management/issues/IW-75/analysis.md on branch IW-75

1. Should IW-75 also fix front matter that renders as one heading, or should that go to a separate issue? (G7)

The issue reports lines that join because Markdown needs extra spaces for a line break. The analysis found a second problem with a different cause. The renderer does not know the --- key block at the top of 160 files (card.md, tracker.md, review packets), so it shows that block as one large heading line. The analysis adds this as Phase 2 only because it looks similar. The final review asks you to decide the scope.

"This is a second shape of the same symptom, so it is in scope."

Links: analysis.md#L209-L211, tasks.md#L10-L11

a) Keep it in IW-75 as Phase 2. Both fixes go into the same renderer file in one pull request. This adds 1.5-2.5 hours to this issue.
b) Move it to a new issue. IW-75 has one phase and fixes only the field lines. Front matter stays broken until someone does the new issue.
c) Do not fix front matter. IW-75 has one phase. The front-matter fault is not recorded anywhere.

Recommended: a) — The fix is already analysed and has a reproduction. It changes the same file, and the dashboard user sees the same fault.

Answer in a comment on this issue, per number, for example "1: a", or in your own words; intake reads it on its next iteration.

Intake: needs-input Workflow: diagnostic Reason: G7 (1 [human] finding) Analysis: project-management/issues/IW-75/analysis.md on branch IW-75 ### 1. Should IW-75 also fix front matter that renders as one heading, or should that go to a separate issue? (G7) The issue reports lines that join because Markdown needs extra spaces for a line break. The analysis found a second problem with a different cause. The renderer does not know the `---` key block at the top of 160 files (`card.md`, `tracker.md`, review packets), so it shows that block as one large heading line. The analysis adds this as Phase 2 only because it looks similar. The final review asks you to decide the scope. > "This is a second shape of the same symptom, so it is in scope." Links: [analysis.md#L209-L211](https://code.iterative.works/iterative-works/iw-cli/src/branch/IW-75/project-management/issues/IW-75/analysis.md#L209-L211), [tasks.md#L10-L11](https://code.iterative.works/iterative-works/iw-cli/src/branch/IW-75/project-management/issues/IW-75/tasks.md#L10-L11) - **a) Keep it in IW-75 as Phase 2.** Both fixes go into the same renderer file in one pull request. This adds 1.5-2.5 hours to this issue. - **b) Move it to a new issue.** IW-75 has one phase and fixes only the field lines. Front matter stays broken until someone does the new issue. - **c) Do not fix front matter.** IW-75 has one phase. The front-matter fault is not recorded anywhere. **Recommended: a)** — The fix is already analysed and has a reproduction. It changes the same file, and the dashboard user sees the same fault. Answer in a comment on this issue, per number, for example "1: a", or in your own words; intake reads it on its next iteration.

claude added the

needs-input

label

2026-10-16 10:52:51 +00:00