The main issue is that Markdown remains a pretty primitive language to write documents in, with dozens of incompatible extensions all over the place.

I don't know if it's the best format to focus on.

▲

OlaProis 12 hours ago | parent | next [-]

Fair point about fragmentation! Ferrite uses Comrak which implements CommonMark + GitHub Flavored Markdown (GFM) — arguably the closest thing to a "standard" we have.

We chose Markdown because: - It's what most developers already use (README files, documentation, wikis) - Plain text files are portable, grep-able, git-friendly, and won't lock you in - GFM covers tables, task lists, strikethrough, and autolinks which handles 90% of use cases

We also support JSON, YAML, and TOML with native tree viewers. Wikilinks ([[links]]) and backlinks are planned for v0.3.0 for folks wanting Obsidian-style knowledge bases.

That said, I'd love to hear what format you'd prefer — always interested in expanding support!

▲

mgaunard 10 hours ago | parent [-]

asciidoc or rst/sphinx, are tools which are much better suited to build software documentation with cross-references etc.

	▲	OlaProis 9 hours ago \| parent [-]
		AsciiDoc and RST/Sphinx are definitely more powerful for structured documentation with cross-references, includes, and admonitions. For now Ferrite is focused on Markdown since that's the most common format for notes and quick docs. But the architecture could support other formats — the parser layer is modular. If there's demand, AsciiDoc would be the easier addition (cleaner syntax than RST). Would be curious how many folks would use it as their primary format vs. Markdown.

▲

tapirl 7 hours ago | parent | prev [-]

This is one reason why I created TapirMD, which offers better specificity.