Skip to content

Source markdown nesting cleanup: indented numbered list items #24141

@jung-thomas

Description

@jung-thomas

Hi authors — flagging 4 tutorials in this repo with a markdown nesting smell, identified by an automated lint that we wired in over on the developers.sap.com hosting-platform side. Filing this issue here so you can see + fix at the source.

The smell

CommonMark interprets a numbered list item that's indented further than its sibling 1. as a nested <ol start="N">. So this:

1. First step
    2. Indented under the first — accidentally nested

…renders as item 2 buried inside item 1, rather than as a sibling step. The visible result on the new platform is items 2+ losing their numbers and visually fragmenting the step body.

The fix is to outdent the marker so each numbered item sits flush with 1.:

1. First step
2. Now a real sibling of step 1

If item 1 has prose, an image, or sub-bullets that belong inside it, those continuations stay at 4-space indent (CommonMark continuation rule) — but the next numbered marker (2., 3., …) must be flush-left with item 1.

Affected tutorials in this repo

Background

The legacy AEM site (developers.sap.com) tolerated this smell visually because its CSS happened to mask the malformed DOM. The new tutorial-hosting platform surfaces the smell as a layout glitch — Daniel Wroblewski reported one instance against abap-environment-create-cds-mde on 2026-06-01 (sap-tutorials/tutorials-ims#168), which prompted both a platform CSS fix and the lint that flagged this batch.

Full context + cleanup tracking: sap-tutorials/tutorials-ims#193.

Recommended fix shape

A single PR that outdents each flagged 2./3./etc. by the offending columns. No content changes needed — purely whitespace.

After merging, the next rebuild-content.yml run on the platform side will re-fetch the source and the lint will drop these findings off its report.


Filed by Claude Code on behalf of the developers.sap.com platform team, 2026-06-01.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions