My org is looking for an asciidoc or markdown toolchain consultant. We need templates and tooling that end up with PDF docs. It all needs to be FOSS, usable by people on Linux/Mac/Windows, and backed by git or svn. We're command line, emacs, vim types, but interested in guis too.
For reference, we have a Latex -> PDF repo: https://github.com/OpenTechStrategies/ots-doctools
If you're interested, hop into https://chat.opentechstrategies.com and say hi!
All leads appreciated. Feel free to circulate this notice. Thanks!
@jamesvasile Asciidoc has a lean mean converter to PDF (asciidoctor), plus the flexibility of XML and XSLT. I feel pandoc is overkill.
Is this a volunteer/contributor request or is this like a contracted consultant realjob? Not asking critically, just wondering about expectations.
@klaatu This is infrastructure for my business. I plan to hand somebody real money to solve this problem. All the resulting work will end up on github under open license.
Volunteer and community input are welcome at any point, of course!
@jamesvasile hi, I don't have too much time to be a consultant, but for the #darktable documentation we are using Hugo, markdown, some custom Hugo themes, and weasyprint to deliver HTML, PDF, and ePub from the markdown sources.
You can substitute Hugo for any static site generator you're comfortable with. Hugo so supports asciidoc I believe.
@jamesvasile Hi there, I used to use a home-made markdown to PDF toolchain based on Pandoc, a custom LaTeX class, and a simple Mafefile that automates the build. I've recently transitioned to a different solution based on Emacs Org Mode, the same custom LaTeX class, and still automated via a Makefile (that launches Emacs in batch mode). I'm so excited by Org Mode and its power and I'd totally recommend it as an option for your task. FWIW, very glad to share my scripts.
@fabionatali I'd love to see a link to your scripts! I use org mode, but not everybody I work with does, and I don't want to make emacs a hard requirement, but anything you have would be great.
@jamesvasile The way I handled variable substitutions in the past is also very rudimentary: via `envsubst` in the Makefile and `$VARIABLES` scattered in the markdown source file. I think I saw you use Jinja instead in your project, which seems a much more sensible approach.
@jamesvasile All in all, the only relevant bit for you might be the use of Pandoc, e.g.
pandoc project.md --pdf-engine=xelatex --output project.tex --template template.tex
That's based on having the markdown in a `project.md` file and the LaTeX scaffolding in a `template.tex`. Of course the template may rely on a custom LaTeX class for further customisation.
@jamesvasile I hear what you say re Emacs and not wanting to add that as a hard requirement, that makes complete sense. In my particular scenario, I could afford the switch and I'm very happy. I'm using the same LaTeX class and I basically get the same result as before (with the markdown toolchain), but with the benefit of being in Emacs. Again, I totally understand that YMMV.
@jamesvasile I'll be following you here, curious to know what you come up with, I find these small automation tricks / toolchains very cool.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.