Very nice (automatic) conversion from pandoc markdown to vim helpfiles.

If I ever write a neovim plugin (or extend my current dinky little plug) this could come in very handy,
e.g. for automatic conversion through Github/Forgejo actions.

Allows creating pandoc filters in python instead of lua.

A fully open-source headless CMS that supports Markdown and Visual Editing - tinacms/tinacms

This seems awesome, integrates itself a little more into your website than 'directus' (which does essentially the same thing) and runs directly on a git repo instead of being backed by SQL. Stuff fetched by GraphQL afaik.

The Modern Data Stack 🐰 — Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database. - directus/directus

Built on REST/GraphQL, can interface with any SQL db (though can bring its own afaik?) - could be a really nice little CMS tool for building blogs/content-websites etc.

Portable Text is a JSON based rich text specification for modern content editing platforms. - portabletext/portabletext

Basically, a pandoc-like AST but built on JSON and more usable throughout web ecosystems.

A 'simplified' bibliography reference format like bibtex or biblatex.

Uses yaml under the hood and is super simple to understand:

Doan2020:
    type: Article
    title: Kinetics and luminescence of the excitations of a nonequilibrium polariton condensate
    author: ["Doan, T. D.", "Tran Thoai, D. B.", "Haug, Hartmut"]
    doi: "10.1103/PhysRevB.102.165126"
    page-range: 165126-165139
    date: 2020-10-14
    parent:
        type: Periodical
        title: Physical Review B
        volume: 102
        issue: 16
        publisher: American Physical Society

One interesting fact is that it uses one (or multiple) 'parent' keys to signify where something is from which in turn use the same simple keys (type, title, ...) as the original document to describe themselves.
So, instead of a million individual keys to describe an entry we use a more recursive format with each having the same couple keys.
This could be really interesting for a closer papis integration with its standard yaml format for example.

Format readme here.

I am not sure how 'mature' the format is, however.
It has been created for the typst typesetting language afaik, and that is still pretty new/fluctuating as of now as well.

A new markup-based typesetting system that is powerful and easy to learn.

This is very exciting. It actually allows some fairly advanced constructs and environments but keeps its (basic) syntax at a similarly simple level such as markdown.

It even has a 'code mode' in which you can call arbitrary expressions and pass arguments just doing #myfunc(myargument:true, another: 12). And those are then programmed in typst language (which I have not looked into yet). And even most basic markup is done in those so they are definitely powerful!

Basically wants to be LaTeX 2.0-ish. Does not yet have the same advanced page-orphan algorithms etc however. Can be used in quarto from 1.4 as markup language!

An academic publishing workflow with automatic doi -> citation processing and (I think?) writing in markdown then publishing as pdf/docx/html documents.

Similar to quarto in other words, but taking a bit of a different approach. Also has a sister-repository with an AI assistant for the publishing process which seems like a neat tool to try.

Zotero plugin that links your Markdown database to Zotero. Jump directly from Zotero Items to connected Markdown files. Automatically tags Zotero Items so you can easily see which papers you've made notes for

Enable rendering cricit-markup in your quarto output.
Could be really useful for a ms-word -less authoring pipeline.

A free and open-source reference guide that explains how to use Markdown.

Contains a very nice 'tools' directory with links to multitudes of markdown-compatible tools (especially interesting for people not just wanting to write md on the commandline or in vim but wanting a 'rich-text-like' experience while writing).

Contains live graphs (using jupyter kernels), or can even include full jupyter notebooks and allow you to edit them. Contains what they call 'rabbit-hole' links which allow a reader to drill down into definitions/examples/sources.

Seems pretty neat - though I would need it to be included in Quarto (thus Pandoc) to be of real use.

Amazing pandoc template for letters that will follow the German regulations (DIN 5008). Write it with markdown, compile with pandoc and latex, be happy.

Similar letter template but less German here: https://github.com/aaronwolen/pandoc-letter/tree/master

Write your notes using handwriting but be able to still use the basic features provided by a word processor: insert text (with automatic paragraph reflowing), delete text or lines, move text, undo and redo, insert links, bookmarks and a table of contents.

Seems really inventive and quite nicely designed as a proof-of-concept. I am not sure how well it would work for larger projects or over longer spans of time but definitely interesting!

Icon-font for all kinds of academic needs (pre-published, peer-reviewed, arxiv, etc). Mimics fontawesome setup but contains much fewer icons. Neat!

Command line tool for improving typing skills - can do random sampling from entries you give it, or use machine learning training sets to give you typing tasks (for a variety of programming languages as well!)

Note-taking in tree-like structures (reminds me a tiny bit of things like workflowy).

One neat thing is that it has the concept of 'global' and 'local' trees: you have one global tree on your machine (usually central place for any notes you want to add, that you can call up from wherever, a little like a wiki index or similar).

Then you can have many local trees that just live in cwd under .mind - perfect for e.g. keeping track of a project's todos (i.e. little code projects for example)

Allows you to collaborate on RMarkdown writing through google docs. You will have to use RMarkdown syntax in google docs however, which seems even more cumbersome than plaintext integrations.

As far as I can see on the demonstration, it will also not do anything for better presentation while writing (since it isn't knitting or anything before you download from gdocs again of course). Don't know how well people would adopt this then.

A really interesting open-source (and open data friendly as far as I can see) tool for writing, publishing, sharing, exporting, and interacting on (think peer review) articles and scientific writings. Can probably also be used for other writings but that's the primary intent.

Seems really interesting, as in should delve deeper with this one. Built on W3C standards uses OpenID and other interesting tidbits.

RMarkdown for the python world, built on pandoc. This seems like an amazing alternative to the R world (though it includes support for R) and all the bookdown and blogdown alternatives.