The more I write in #CommonMark #Markdown or even #GithubFlavoredMarkdown, the more I want to switch to some other format with more extensive features, or roll my own...

I want something with easy footnotes, definition titles, semantic sections, section CWs, etc, without having to resort to inserting HTML, and keeping it human-readable.

#coding #writing

@FiXato LaTeX? Not familiar with it personally, but it must have at least footnotes and semantic sections since it's for academic text.

@lj_writes yeah, #LaTeX is something I am considering, but I have a feeling that that will end up not being as intuitive to write for me, and not as human-friendly to read as-is.

@FiXato Yeah the trade-off between features and ease of use is tricky :/

@lj_writes yeah, especially it's an older format that tries to please everyone. I guess why I'm currently mostly considering rolling my own.

Unfortunately that would mean losing out on #GithubPages support and the likes, so for now I'm trying to work around it with little backward-compatible hacks.

Relevant #xkcd I guess: xkcd.com/927/ ('Standards')

Follow

@FiXato @lj_writes please don't roll your own format, there are already too many of them. you can use with , see kodymirus.cz/overleaf-html-sam for example.

@michal_h21 using #GithubActions to deploy to #GithubPages (or I guess any other CI tool to convert and deploy to an alternative platform) is an interesting solution I hadn't actually considered yet, thanks. :)

#LaTeX does still look quite human-readable, apart from some of the complexer structures (the \verb part in the example for instance).
I'd have to experiment a bit with that to see if that would work out well enough for my usecase. :)

@lj_writes

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.