Coming at this from the AsciiDoc side (we ship a Mac/iPad authoring app there): Quarkdown's syntax design looks clean, especially the user-defined functions. The harder problem in this category, in my experience, isn't necessarily the source language though. I'd say the output pipeline is the tough one.
Markdown extensions for cross-refs, admonitions, conditional content, function-based reuse — design-wise, those are tractable. The gap most projects in this space hit is downstream: tagged PDF that conforms to PDF/UA, deterministic builds across environments, hreflang and cross-document linking for multi-language docs sites, incremental rebuilds that don't choke on a 500-page book. PDF/UA matters more in the EU since the European Accessibility Act took effect on 28 June 2025.
Curious what the plan looks like there for the four doctypes — paged in particular.
Markdown extensions for cross-refs, admonitions, conditional content, function-based reuse — design-wise, those are tractable. The gap most projects in this space hit is downstream: tagged PDF that conforms to PDF/UA, deterministic builds across environments, hreflang and cross-document linking for multi-language docs sites, incremental rebuilds that don't choke on a 500-page book. PDF/UA matters more in the EU since the European Accessibility Act took effect on 28 June 2025.
Curious what the plan looks like there for the four doctypes — paged in particular.