https://alwaldend.com/docs/projects/x_article_uploader/openspec/specs/markdown-to-draftjs/ Recent content in Markdown to draftjs on Alwaldend Hugo en https://alwaldend.com/docs/projects/x_article_uploader/openspec/specs/markdown-to-draftjs/spec/ Mon, 01 Jan 0001 00:00:00 +0000 https://alwaldend.com/docs/projects/x_article_uploader/openspec/specs/markdown-to-draftjs/spec/ <span id="markdown-to-draftjs-specification"></span><h2 id="purpose">Purpose<a class="td-heading-self-link" href="#purpose" aria-label="Heading self-link"></a></h2><p>Compile a Markdown post into the DraftJS <code>content_state</code> document that the X Articles API accepts, so the Markdown that renders the blog also produces the article body without hand-editing.</p> <h2 id="requirements">Requirements<a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"></a></h2><h3 id="requirement-source-post-input-model">Requirement: Source post input model<a class="td-heading-self-link" href="#requirement-source-post-input-model" aria-label="Heading self-link"></a></h3><p>The converter SHALL treat a blog source post as YAML front matter plus a Markdown body, and MUST NOT emit front matter as article text. It SHALL expose the parsed metadata separately from the <code>content_state</code> document, and SHALL report the parsed <code>title</code> as document metadata because draft creation requires a title that <code>content_state</code> does not carry. A source whose front matter has no non-empty <code>title</code> SHALL fail conversion with a diagnostic naming the source, rather than producing a document that cannot be uploaded.</p>