Branded Course Materials Pipeline: From Markdown Syllabus to Per-Session DOCX

Abstract This paper documents two utilities that compose a complete course-materials pipeline for independent educators: a syllabus PDF compiler that converts markdown course structure into branded A4 PDFs, and a per-session content generator that produces individual .docx files per session from a YAML syllabus specification. Together they handle both the public-facing syllabus document and the per-session teaching materials. What this deposit contains paper.md — the methodology paper (the citable scholarly artifact) supplementary.zip — bundled working source code for 2 component workflows covered by this paper, each with its own README, Python source, configuration, sample input, CITATION.cff, and LICENSE README.md — entry point CITATION.cff — machine-readable citation LICENSE (MIT for code) and LICENSE-DOCS (CC BY 4.0 for documentation) Production Results Courses produced: 5 syllabi to date Sessions per course: 8-12 typically Time saved per session vs. manual formatting: ~30 minutes Limitations The session generator produces a structural skeleton, not full session content. Authors must still write the body. Multi-language courses are not yet handled by the templates. Reproducibility Two MIT-licensed Python modules with sample syllabi. Companion Papers This deposit is one of ten flagship records in the Practitioner Publishing Stack series. Each flagship is a methodology paper plus the relevant working source as supplementary material. The series: I. Markdown to multi-format compile pipeline (.docx, .pdf, .epub) with consistent typography. (slug: f01-pub-compile-stack, domain: PUB) II. Detection and removal of AI writing signatures from manuscripts before publication. (slug: f02-aiq-zero-signature-pipeline, domain: AIQ) III. End-to-end pipeline from literature search to Zenodo-published, DOI-indexed academic artifact. (slug: f03-res-research-to-doi, domain: RES) IV. Six python-docx utilities for format normalization, heading conversion, and AI-signature cleanup. (slug: f04-doc-production-pipeline, domain: DOC) V. Visual design system: color tokens, typography, charts, diagrams, and AI cover composition. (slug: f05-vis-leather-and-steel-design-system, domain: VIS) VI. Markdown-driven template engine producing branded spreadsheets and PDF checklists for direct sale. (slug: f06-tpl-spec-to-sellable, domain: TPL) VII. Per-channel specification workflow for distribution across seven publishing platforms. (slug: f07-dst-multi-platform-distribution, domain: DST) VIII. (this paper) — Course-materials pipeline: markdown syllabus to branded PDF and per-session DOCX. IX. Seven-phase book production methodology with hard quality gates and 18-day average cycle time. (slug: f09-meta-book-lifecycle, domain: META) X. Architectural overview of an independent publishing operation that produced 558+ titles. (slug: f10-meta-practitioner-publishing-stack, domain: META) Author Ibrahim Anwar (Hibranwar) ORCID: 0009-0006-0425-4923 Wikidata: Q138856145 Web: hibranwar.com Affiliation: PT Hibrkraft Kreasi Indonesia (Cileungsi, Bogor, Indonesia) License The methodology paper, configuration, and sample data are released under CC BY 4.0. The Python source code in supplementary.zip is released under the MIT License. Citation If you use this work, please cite via the DOI minted on this Zenodo record. A machine-readable CITATION.cff ships in the deposit. About the Practitioner Publishing Stack The Practitioner Publishing Stack documents an independent publishing operation by Ibrahim Anwar that produced 558+ titles across nonfiction books, public-domain translations, academic papers, and digital templates, distributed across seven platforms, with a single human as the bottleneck. Average end-to-end cycle time per title: 18 days. Operator headcount: 1.