Publishing multilingual articles into Payload 3 from Markdown (Lexical converter + agent skill)

[apoi15]

I run a Payload 3 + Next.js site that publishes every article in English, Spanish
and French. Writing them through the admin was slow, and letting an AI agent fill
forms or call the REST API gave different results every run. So I moved the whole
thing to Markdown files plus one script that is the only thing allowed to write
articles, and open-sourced it:

https://github.com/apoi15/payload-blog-publish-skill

What might be useful even if you don't use an AI agent:

• Strict Markdown ⇄ Lexical converter. ##/###, lists, links, tables,
  images and :::callout / :::cta / :::video map 1:1 onto Lexical nodes and
  custom blocks. Anything it can't represent (H1, code fences, HTML, nested lists…)
  is rejected with a line number instead of approximated.
• blog:publish: dry run by default, --apply writes all locales, then reads
  the article back and compares it with the source.
• blog:export: lossless export of a live article back to Markdown, so edits
  made in the admin aren't lost.
• Production database guard. Checks the DATABASE_URL host, and refuses to
  write production unless that one command carries ALLOW_PRODUCTION_DB=true.
• Revalidation for CLI writes via a small app/api/revalidate route.

The SKILL.md lets Claude Code, Codex or any agent run the full pipeline: research,
drafts per locale, dry run, dev DB, then production.

A live example, published in three languages with this workflow:
https://www.hlnapparel.com/blog/ai-tech-pack

examples/ includes a matching Articles collection and the Lexical blocks.
Feedback on the converter's mapping is very welcome.