Would you like to add #metadata via the command line, but feel limited because arguments to `--metadata`/`-M` are not treated as #Markdown? Here's a #LuaFilter to solve this:

function Meta (meta)
for key, value in pairs(meta) do
if type(value) == 'string' then
meta[key] = pandoc.utils.blocks_to_inlines(
pandoc.read(value).blocks)
end
end
return meta
end

Example:

pandoc -L parse-md-in-metadata.lua \
-M title='Defend democracy *now*!' …

Blog post by @benjamingeer describing a method to generate #Arabic PDFs from Markdown via #TeXLaTeX:
https://benjamingeer.name/en/post/pandoc-arabic-howto/
#pandoc #markdown #pdf #blog

#Markdown tip: the most commonly used syntax for horizontal rules seems to be three hyphens

---

However, this can sometimes lead to confusion with YAML block delimiters and overlaps with setext headings syntax. It can thus be clearer to use three or more asterisks instead

* * *

The interposed spaces are optional.

Lecture Template by Carten Gips: “This project defines a skeleton repo for creating lecture slides and handouts including lecture notes out of Pandoc Markdown using a single source approach.”
The project has extensive documentation and offers multiple installation and usage options.
https://github.com/cagix/pandoc-lecture
#pandoc #markdown #singlesource #template #lecture

#Markdown syntax tip for code block attributes, yielding the best rendering results with both pandoc and on platforms such as #GitLab #GitHub, #Codeberg, etc:

``` lua {#my-id .another-class}
io.stdout:write('hi!')
```

The curly-braces syntax for attributes is ignored when read as #CommonMark, the Markdown variant used by most platforms. The above ensures that syntax highlighting still works with CommonMark, and that the other attributes get respected when converting with #pandoc.

New library: panluna — write customized #Markdown parsers and use them with #pandoc.
Some Markdown syntax extensions cannot be realized via filters but require custom readers. The #panluna library provides a new method to build such readers, based on the lunamark parser. The latter was written by John MacFarlane, who also authored pandoc.
https://github.com/tarleb/panluna

#Misskey で新しいことを学んだよ。
$[ruby 漢字 ふりがな] → 漢字(ふりがな)
#ruby #markdown ​​ ​​

RE: https://makai.chaotic.ninja/notes/9rnnao9gvb

Here it is, the newest of the newest re-recording of my introduction video to #SilverBullet

19 minutes of #PKM #Markdown awesomeness. If you're into that type of thing.

https://www.youtube.com/watch?v=8btx9HeuZ4s

＞脱Word、脱Markdown、asciidocでドキュメント作成する際のアレコレ #Markdown - Qiita https://qiita.com/tamikura@github/items/5d3f62dae55617ee42bb

markdown は『表でセルの結合ができない』などの理由でイマイチと言われている。Excel ではセルの結合が忌むべきものとされていたりするので、このあたり面白いところである。

まぁ、これはExcel がワードプロセッサのように使われているのがそもそも悪いためなのであるが（初期の Word があまりにも酷かったのが一因）、日本人はなんでも表で表現しようという癖がある（悪癖とまでは言わないが）

#Markdown has two kinds of #links:

[inline links](https://pandoc.org/MANUAL#inline-links)

and

[reference links][1]

[1]: https://pandoc.org/MANUAL#reference-links

The former is the default when producing Markdown, but the latter can be generated by calling pandoc with the `--reference-links` option. Control the placement of reference lists with `--reference-location`: either after each block, after each section, or all together at the very end of the document.

There are four ways to add #metadata to a document: in ascending order of precedence, with latter options overriding earlier options, these are:

• dedicated metadata YAML file passed via `--metadata-file`,
• metadata in the input document (e.g., #YAML blocks in #Markdown),
• entries below the `metadata` field in a defaults file, and
• values given via the command line (`--metadata` or `-M`).

Also, if a value is defined more than once in an input doc, then the last one wins.

Hi @pandoc!

I am writing my thesis in #Markdown, obviously using #Pandoc, but without using any template because I want to keep things as simple as possible.

I simply run the command pandoc -s thesis.md -C -o thesis.pdf (details in this page).

I have one problem, though: all #HTML tags used inside Markdown (such as <u>, <q>, and <cite>) are not rendered, and they disappear in the final PDF (therefore, if I underlined something with <u>, in the PDF it is not underlined).

Do you have any suggestions about how I can fix this?

Thank you so much!

Writing a #thesis? Thinking about doing it in #Markdown? No problem, Tom Pollard has you covered.
https://github.com/tompollard/phd_thesis_markdown

Create speaker notes for slides by adding a "notes" div. #Markdown example:

# Abbey Road
Here comes the sun

::: notes
And I say it's all right.
:::

Works as expected with pptx (#PowerPoint).
#revealjs: use the speaker view by pressing `s`.
#beamer: compile with `-V classoption=notes` or `-V classoption=notes=only`.

Make sure to enable the `gfm_auto_identifier` extension on a reader when converting to GitHub Flavored Markdown, especially when adding a Table of Contents with `--toc -s`. E.g.:
pandoc -f markdown+gfm_auto_identifiers -t gfm --toc -s

This is a bit awkward, but ensures that all links and header IDs are in the format expected by GitHub.
#Markdown #gfm #toc

Wide #Markdown pipe tables sometimes overflow the page when converted to #PDF. This is due to pipe tables not containing table column widths. Multiline tables and grid tables do encode this info; using them can prevent overflow issues.
#tables