ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: juh+ntg-context--- via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: juh+ntg-context@mailbox.org
Subject: Re: Improving pandoc's ConTeXt output
Date: Sun, 5 Jun 2022 18:38:56 +0200	[thread overview]
Message-ID: <aa920c8b-19d2-0111-cbe2-290caa8f4392@mailbox.org> (raw)
In-Reply-To: <87czfnp55x.fsf@zeitkraut.de>

Dear Albert!

Am 05.06.22 um 16:15 schrieb Albert Krewinkel via ntg-context:
> Dear juh,
> 
> juh via ntg-context <ntg-context@ntg.nl> writes:
> 
>> great to hear that, as my cooperative uses pandoc to produce print stuff
>> with ConTeXt, we are always happy, when there are improvements.
> 
> I'd love to learn more about your workflow, if you have time to share at
> some point!
> 

I would like to blog about it, but we are still tweaking the process.

In short.

Our authors use Markdown:

- to produce websites via Hugo
- to produce print stuff via pandoc-context

Our main concern was the question: How to roll out the context system to 
all contributors?

We maintain our system in a repo with a bootstrap script.

The bootstrap script determines the architecture of the computer, 
installs lmtx in the right architecture (linux,mac,windows) and 
generates a post-merge script for git that calls "context --generate" 
after every update of the repo.

The repo contains context stuff and pandoc stuff in two directories.
In ../context-project we have our style files and global images such as 
logos, icons etc.

In the pandoc directory we store our pandoc templates, filters, 
csl-styles and global bibliografies.

Last but not least the repo contains a build script that essentially 
calls pandoc and context on the given markdown file.

For each print project we have a different repository, eg. for reports, 
brochures, slides or offers.

We make use of the yaml preface in the markdown files especially for 
offers. The sales consultant only has to fill out the yaml part and 
build the file. The result is nice looking and standardized so that 
everyone in the coop could write an offer.

One dependency is that everyone must install the newest pandooc and 
Inkscape to convert SVGs to PDF. With the MP-way of doing this we had 
some problems. We need the SVG conversion for our documentation. It is 
special as we would like to build the html version also with pandoc from 
one single markdown source. In theory this is possible but there are yet 
some smaller problems to solve.

I am happy to answer questions for details.

juh
-- 
Hostsharing Presseteam | https://www.hostsharing.net
Telefon: +49 40 2093313-51 | Telefax: +49 40 2093313-52
Hostsharing eG | Flughafenstraße 52a | 22335 Hamburg | Germany
Registergericht Hamburg, GnR 1007 | UID: DE218602793
Vorstand: Michael Hierweck, Dr. Martin Weigele

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2022-06-05 16:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05  7:07 Albert Krewinkel via ntg-context
2022-06-05  8:20 ` juh via ntg-context
2022-06-05  9:39   ` Denis Maier via ntg-context
2022-06-05 14:15   ` Albert Krewinkel via ntg-context
2022-06-05 16:38     ` juh+ntg-context--- via ntg-context [this message]
2022-06-05 23:52       ` Thangalin via ntg-context
2022-06-06  5:21         ` Problem with SVG an conversion mp (was: Improving pandoc's ConTeXt output) Jan U. Hasecke via ntg-context
2022-06-06  5:51         ` Improving pandoc's ConTeXt output juh+ntg-context--- via ntg-context
2022-06-05  9:46 ` Denis Maier via ntg-context
2022-06-05 10:01 ` Hans Hagen via ntg-context
2022-06-05 11:08   ` Wolfgang Schuster via ntg-context
2022-06-05 14:30     ` Albert Krewinkel via ntg-context
2022-06-06 20:47       ` Henning Hraban Ramm via ntg-context
2022-06-08 13:43 ` Albert Krewinkel via ntg-context

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aa920c8b-19d2-0111-cbe2-290caa8f4392@mailbox.org \
    --to=ntg-context@ntg.nl \
    --cc=juh+ntg-context@mailbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).