If you are typesetting a research paper or writing a technical book for print publication typst is a great solution, but for a lot folks not having web support is an absolute dealbreaker.
Why? because Asciidoc/tor gives you a lot more:
- a syntax with callouts, tables, indexes, comments, notes and everything you may need in a book
- macro expansion
- a ton of complex diagrams via PlantUML (veeery useful!) that you can keep inline
- a ton of output formats, including "real" paper books via Docbook.
I use my Markdown editor[1] to produce my blog[2].
keenwrite.bin -q -i "${FILE_MD}" -o "${FILE_HTML}" \
--curl-quotes=true
Offers external variable sources, too; see [3] and [4].[2]: https://dave.autonoma.ca/blog/
[3]: https://gitlab.com/DaveJarvis/KeenWrite/-/blob/main/docs/cmd...
MkDocs or Docusaurus for documentation. MdBook is not in the running, IMO, unless it’s radically improved since the last time I checked.
And here’s my hot take—most generators have a lot of the same design flaws. Routing is generally a mistake—you should instead design a system where every page has a URL that directly corresponds to the source file path, if feasible. Shortcodes are a mistake—you should use custom HTML tags. SSGs should have e.g. S3+Cloudfront as a core part of their design rather than just thinking of S3 as a place you put files when you’re done.
[3] https://gurudas.dev/blog/2023/06/07/how-i-generate-gurudas-d...
https://awesome.haunt.page/
A few hand-picked examples: https://jakob.space/blog/decompilation-by-hand.html
https://guix.gnu.org/en/download/latest/
https://www.gnu.org/software/guile/learn/Jekyll - written in Ruby
Hugo - written in Go
Zola - written in Rust
GitHub Gist: "Document Conversion":
https://gist.github.com/datacustodian/4483fff487a0ef70c7b760...
https://en.wikipedia.org/wiki/List_of_document_markup_langua...
Issue is that the file system layout is more like this:
/Product A/images/
/Product A/revision.tex
/Product A/instalwin7.tex
/Product A/instalwin10.tex
/Product A/layout.tex
/Product B/layout.tex
/Commmon/images/
/Common/companyinfo.tex
/Common/header.tex
/Win7/images
/Win7/access-cmd.tex
/Win10/images
/Win10/access-cmd.tex
Where Product A and Product B layout.tex links all LaTex files needed to build a complete document.
I chose `mdbook` over `pandoc` mainly because of themes and search provided by default.
If I could wave a wand and extend it in any way I chose, I'd want the ability to implement macros (or the equivalent) a la TeX, so as to automate doing fancier formatting in HTML.