Markdown blockquotes render as literal > text without semantic blockquote styling #57

Website baseline: ac81655f4ac3aa1250023a3a9a5e3a93c00ac059 (website branch), checked locally on 2026-10-28.

Observed behavior

Documentation pages containing Markdown blockquote syntax (lines prefixed with >) render as raw literal text prepended with > inside a standard <p> tag rather than an HTML <blockquote> element.

Specifically, on /docs/installation/, the note:

> The upstream OWASP repository is the canonical source. The fork may contain additional content or experimental changes not yet merged upstream.

renders in the DOM as:

<p><br>&gt; The upstream OWASP repository is the canonical source. The fork may contain additional content or experimental changes not yet merged upstream.</p>

While globals.css (lines 139–146) provides dedicated styles for .prose blockquote (left amber accent border, background tint, padding, and subtle rounded corners), this styling is never applied because renderMarkdown() in src/app/docs/[slug]/page.tsx only escapes > to > without converting blockquote syntax into <blockquote>.

Reproduction

1. Open /docs/installation/.
2. Inspect the paragraph immediately following the fork clone code snippet.
3. Observe that the text begins with a literal > character and is rendered as a normal paragraph without the intended blockquote callout styling.

Expected behavior

Parse Markdown lines beginning with > into semantic <blockquote> tags (or wrapped within .prose blockquote), rendering them with the styled callout box defined in globals.css and removing the literal > / leading <br> characters.

Marked screenshot

Red boxes, numbered callouts and AUDIT ANNOTATION panels were added temporarily in the browser to identify the observation/request. They are not implemented website features. Capture notes.

Source

• src/lib/docs-data.ts:93
• src/app/docs/[slug]/page.tsx:177
• src/app/globals.css:139

Scope and disclosure

Issue report only; no PR or website code changes. AI assistance: Google Antigravity (Gemini); browser investigation via Playwright, evidence annotations and report drafting. Checks were executed locally; payload examples remained inert text; no target testing was performed.