--input-format md (Markdown input)

OurBigBook has some level of support for markdown input.

Single newlines preserve paragraph grouping, including around fenced code and native block macros; blank lines separate paragraphs. This allows block content inside paragraphs without explicit \P wrappers. Unlike standard Markdown's lazy continuation, unindented prose ends a list, and unquoted prose ends a block quote. Indent every continuation line of a list item and prefix every line of a block quote with >. This keeps following prose outside those containers without forcing a paragraph break. OurBigBook macro arguments can themselves contain Markdown. The github-md output format is for GitHub deployment, not lossless conversion to editable Markdown source.

Markdown wikilinks use native OurBigBook cross-reference resolution: [[fundamental theorem of calculus]] is equivalent to <fundamental theorem of calculus>, and [[my id|my text]] is equivalent to <my id>[my text]. Custom display text can contain Markdown. Wikilinks remain literal inside code; escape the first bracket as \[[my id]] to display the syntax in normal text.

Topic links use [[#personal knowledge bases]], equivalent to \x[personal knowledge bases]{topic}. Use [[#personal knowledge bases|my text]] for a custom label. Unlike ordinary wikilinks, topic links do not require a matching local header.

You can transparently include standard markdown files such as markdown-example.md with:and OurBigBook will integrate it into the current project seamlessly. Live demo: