inv-cmarker:0.1.0

[ck3d]

I am submitting

• a new package
• an update for a package

Description: to-commonmark converts Typst content to CommonMark strings, written entirely in Typst script with no external tooling required. It provides a single to-commonmark(content) -> str function that performs a recursive walk over Typst's content tree, supporting headings, paragraphs, lists (unordered and ordered), block quotes, code blocks (with language info strings), inline code, strong/emphasis, links, images, and line breaks. Unsupported elements (tables, math, figures, footnotes) emit HTML drop comments rather than failing silently.

This is useful for:

• Exporting Typst-generated documentation to Markdown for publishing on GitHub, Wikis, or static site generators
• Building documentation pipelines that originate in Typst but need to be consumed in Markdown-only environments
• Content migration from Typst to Markdown-based systems

The package is written in pure Typst script with zero dependencies, making it portable and easy to integrate.

I have read and followed the submission guidelines and, in particular, I

• selected a name that isn't the most obvious or canonical name for what the package does
  • Explanation: The canonical name would be typst-to-commonmark. We use 2 as a shorthand convention common in package ecosystems (similar to json2yaml, png2svg, csv2json), making it a stylistic neologism rather than the most obvious English phrasing.
• added a typst.toml file with all required keys
• added a README.md with documentation for my package
• have chosen a license and added a LICENSE file or linked one in my README.md
• tested my package locally on my system and it worked
• excluded PDFs or README images, if any, but not the LICENSE

[saecki]

Thanks for this package!

[saecki]

This name and the initially submitted name are not ideal. The original shouldn't really have to contain the word Typst and this one is a little too descriptive. We try to avoid canonical names so multiple packages serving the same purpose can coexist without one having an unfair advantage. Could you change the name to something else, for example by adding a non-descriptive prefix or suffix, or ideally by coming up with something a little more creative? See our naming rules

[ck3d]

Thanks for your feedback. My new proposal is inv-cmarker.

[saecki]

I see you've changed the description, probably because of the warning. But because this is a somewhat of a meta usecase, I would say it's ok to specifically say Typst content, which makes things a bit clearer.
See: https://github.com/typst/packages/blob/main/docs/manifest.md#writing-a-good-description

[ck3d]

The typst-package-check fails, when I add Typst to description.