Customizing document styles with FSharp.Markdown.Pdf

Yan Cui

I help clients go faster for less using serverless technologies.

Following on from my last post on formatting a Markdown document into PDF using FSharp.Markdown.Pdf, if you don’t like the default styling (which I tried to mimic style Github formats Markdown documents with) you can set your own styling for the different types of Markdown elements by going down a level of abstraction.

The FSharp.Markdown.Pdf.MarkdownStyleNames module defines all the names of styles used to format the different Markdown elements (e.g. heading 1-6, code block, listing 1-3, etc.) into PDF. To override the default styles, you need to:

  1. Instantiate an instance of the Document type from the MigraDoc.DocumentObjectModel namespace.
  2. Add the predefined style names from the aforementioned MarkdownStyleNames module to the document’s collection of styles.
  3. Tweak the style to your liking.
  4. Call the FSharp.Markdown.Pdf.PdfFormatting.formatMarkdown function with the Document value.
  5. Voila! You now have an instance of PdfDocument which has been formatted with your custom styling.

to see these simple steps in action:

You can compare the original and customized PDF outputs here and here.

Whenever you’re ready, here are 3 ways I can help you:

  1. Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop to level up your serverless skills quickly.
  2. Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
  3. I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.

1 thought on “Customizing document styles with FSharp.Markdown.Pdf”

  1. Pingback: F# Weekly #26 2013 | Sergey Tihon's Blog

Leave a Comment

Your email address will not be published. Required fields are marked *