markor VS Asciidoctor

Just curious, any reason you're using TMarkor instead of Markor? (https://github.com/gsantner/markor/ , https://play.google.com/store/apps/details?id=net.gsantner.m...)

Only asking since this was also the editor I ended up settling on in Android, but it seems like TMarkor is just a repackaging of Markor without any references to its forked(?) source.

My requirement was that the repo had to be open source so that I could audit the repo and compile the APK from source, as well as potentially fork it for personal modifications if needed.

As other commenters posted, maintaining screenshots is a pain. Especially with software that's regularly changing.

That said, there are more than a few GitHub readmes that contain screens. Sometimes quite a few screens. Here's an example: https://github.com/gsantner/markor

The new Version 2.11 of [email protected] is now available on f-droid

Try Markor

Use Markor as my org-roam Set up my notes directory as my "home" directory, and set up some templates for creating new files, and set some timestamp formats to match org's. Also has a recursive text search that's good enough for my uses.

This is the Markor github repository with links to F-droid: https://github.com/gsantner/markor

There are web based VSCode you can run. Or if you push to Github that with give you a good read and a ok write experience. I treat mobile as a read only so I use Markor.

I already use Markor for some things on Android, so this might work really cleanly, unless I'm misunderstanding Foam's structure.

You can also use Syncthing with any kind of local files only editor to make them sync-able. For example with Markor

I use Markor and like it very much, feature-wise.

You have also AsciiDoctor ( https://asciidoctor.org/ ) which is alive and well. I am using it for technical CS documentation internally, but only for single page documents. I did not try to deploy their whole multi-document setup called Antora ( https://antora.org/ ).

AsciiDoc File support. ( #1876, #808, #2022)

If Maths is important to you, take a look at Asciidoc - https://asciidoctor.org/

I use Asciidoctor, highlightjs, a custom highlight.js language definition and that bash script:

AsciiDoc is so close to being good. It slam dunks Markdown, but they just have a few nagging issues that they refuse to fix, for 9 years now:

https://github.com/asciidoctor/asciidoctor/issues/1087

Asciidoctor is a Ruby-based text processor for parsing AsciiDoc into a document model and converting it to HTML5, PDF, EPUB3, and other formats. Built-in converters for HTML5, DocBook5, and man pages are available in Asciidoctor. Asciidoctor has an out-of-the-box default stylesheet and built-in integrations for MathJax (display beautiful math in your browser), highlight.js, Rouge, and Pygments (syntax highlighting), as well as Font Awesome (for icons). Although Asciidoctor is written in Ruby, that does not mean you need to know Ruby to use it. Asciidoctor can be executed on a JVM using AsciidoctorJ or in any JavaScript environment (including the browser) using Asciidoctor.js. You can choose any one of three Asciidoctor processors (Ruby, JavaScript, Java/JVM) and get the same experience. You can also use the Asciidoctor Maven Plugin to convert your Asciidoc documentation using Asciidoctor from an Apache Maven build.

asciidoctor for writing

If you're looking at AsciiDoc, you'll want to look at Asciidoctor: https://asciidoctor.org/

The third system that I found was AsciiDoc, which started as a Python project, abandoned for a while and eventually resurrected by Dan Allen with Asciidoctor. AsciiDoc has a lot of features and I consider it superior to Markdown, but Asciidoctor is a Ruby program, and this made it difficult for me to use it. In addition, the standard output of Asciidoctor is a nice single HTML page but again customising it is a pain. I eventually created the site of the book using it, but adding my Google Analytics code and a sitemap.xml to the HTML wasn't trivial, not to mention customising the look of elements such as admonitions.