Download
Each family member comes as a pair: a full proposal document you can edit in Word, and a small reference document carrying only the design, for generating from Markdown. The PDFs are visual previews.
Prefer everything at once — templates, Markdown skeleton, OOXML source, fonts and the builder? Download the full kit (.zip), or browse it as files.
«…». Replace all of them before sending. Commercial figures and agreement wording are deliberately left unfilled, and Holosun ApS is named in the footer — change the entity details if a different party is issuing the proposal.Two ways to use them
1. Edit in Word
Save a copy and replace its prompts. Use the existing Heading 1/2/3 and SunholoTable styles; the header and footer stay editable. These are ordinary reusable .docx files — not macro-enabled documents, and not Word .dotx templates.
2. Generate the document from Markdown
This is what the reference files exist for, and it is the interesting half. A reference document is a near-empty .docx carrying only the design: page setup, running header and footer, theme, fonts, styles. Point --reference-doc at one and your Markdown becomes the body.
Generate from Markdown
docparse draft.md \
--convert proposal.docx \
--reference-doc sunholo-reference.docx \
--table-style SunholoTableSwap sunholo for holosun or ailang. proposal.md in the kit is a ready-made skeleton with the same structure as the Word files — copy it and fill it in. Nothing here needs Word or LibreOffice installed: the generator writes the OOXML container directly.
Three authoring notes worth knowing before your first run:
| In your Markdown | What happens |
|---|---|
# heading | Starts a new page — use it for major sections only |
## / ### heading | Subheadings, kept with the text that follows |
| Hard line break | Collapsed — use separate paragraphs where separation matters |
[placeholder] | Can be swallowed by link parsing — use «placeholder» |
For exactly which parts of the document the merge lifts from the template and which it regenerates, see Styling from a reference doc.
Design
A4 portrait; 23 mm side margins; white page; Montserrat headings over 11 pt Arial body. Colours are taken from sunholo.com: vermilion #E73C17, blue-grey #314352, pale grey #F6F8FA, with a darker vermilion #B52D10 for small link text.
First-page branding is larger; continuation pages use a compact header. Table headers repeat across page breaks. The three-page outline covers the opportunity, the delivery and the commercial next steps — real content usually runs longer, so render and look at it after editing.
Montserrat Regular and Bold ship in the kit under the SIL Open Font License. Install them for the closest Word layout, or send the PDF. The fonts are not embedded in the DOCX.
Rebuild from source
The design is not baked into a binary you have to reverse-engineer. source/parts/ is the editable OOXML; source/build.ail packages those parts and the logos into the reference documents using AILANG’s std/zip; and build.sh then runs the reference documents back through docparse to regenerate the proposals themselves.
bash build.shNo Python and no python-docx anywhere in that pipeline. Requirements: AILANG, AILANG Parse, and — only for rendered previews — LibreOffice and Poppler.
After changing the design, check it:
docparse-audit output/sunholo-proposal.docx --strict
docparse-render output/sunholo-proposal.docx --output-dir .build/renderThen look at every rendered page. An audit pass says the file is well-formed. It says nothing about whether the layout, or the wording, is right.
Licence
The templates and their OOXML source are published by Holosun ApS for reuse, including commercially. The bundled Montserrat fonts keep their own SIL Open Font License, included as OFL.txt. The Sunholo and AILANG logos are Holosun ApS marks — replace them with your own if you are issuing proposals as a different party.
This is a document adaptation of the sunholo.com visual language rather than a formal brand guide.
Frequently Asked Questions
Are these Word proposal templates free to use?
Yes — adapt them freely, including commercially. Keep OFL.txt with the Montserrat fonts if you redistribute those, and swap the logos if you are issuing proposals as a different party.
What is the difference between the proposal file and the reference file?
The proposal .docx is a full document you edit in Word. The reference .docx is a near-empty companion carrying only the design — page setup, headers, footers, theme, styles — for use with --reference-doc, where its body is discarded and your Markdown supplies the content.
Do I need Word or LibreOffice to generate a branded document?
No. docparse writes the OOXML container directly, so there is no Office install and no headless subprocess. LibreOffice and Poppler are only needed if you want rendered PDF or PNG previews.
Are these .dotx Word templates?
No — ordinary reusable .docx files, not macro-enabled and not .dotx. Save a copy and edit it, or point --reference-doc at the matching reference file.
Can I use my own company letterhead instead?
Yes, and that is the more common case. Any existing .docx works as a reference doc — its logo, embedded fonts and running headers come through byte-for-byte. These templates are a worked example, not a requirement.