We updated the release blog draft flow and the admin blog editor to make generated drafts easier to review and to improve how posts appear to readers. Generated drafts now follow a clearer completeness contract so model-authored prose and deterministic CMS fields are assigned predictable responsibilities. That helps editors know what to check and what to fill in before publishing.
Admins now edit post body and structured blocks with a richer Markdown editor (Tiptap-based) that supports headings, lists, emphasis, links, inline code, and inline image insertion from the CMS media library or uploads. Public blog rendering was updated to preserve that rich Markdown so headings, lists, emphasis, links, code, and images display correctly instead of being flattened to plain text.
Inline images in Markdown are rendered as figures with alt text and optional captions, and the editor preserves explicit image and before/after media blocks. A publish-readiness panel with gap labels and an explicit Publish confirmation helps editors resolve missing SEO or media fields before a post goes live.
Visible before/after checks were captured for the admin editor and public blog rendering to validate the changes; these show the editor updates and how posts look after the richer rendering landed. For jobseekers, the result is clearer, better-structured blog posts with readable headings, lists, links, and images — making release notes and product posts easier to scan and understand.
What changed: generated release blog drafts follow a clearer completeness contract; the admin editor now uses a richer Markdown editor with inline image support; public rendering preserves Markdown structure and images.
Why it matters for jobseekers: blog posts are more consistent and easier to read — headings, lists, links, code snippets, and images appear correctly, so you can scan release notes and product guidance more effectively.