public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Adding minimal CSS to pandoc's default HTML template
Date: Sun, 23 Aug 2020 13:54:00 +0200	[thread overview]
Message-ID: <87r1rxa887.fsf@zeitkraut.de> (raw)
In-Reply-To: <41422a08-cc8d-4480-8bfc-03d907cb2794n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Looks great, IMHO! The produced layout is beautiful, and
supporting more variables is nice, too.

The only concern I have is that this could open pandora's box when
is comes to requests for CSS tweaks. But this seems like a minor
problem.


mb21 writes:

> We're looking for feedback on a pull request I made: it adds some minimal
> CSS to pandoc's default HTML template.
>
> Two things that inspired this:
>
> - questions like this one on StackOverflow:
> https://stackoverflow.com/questions/63293929/pandoc-change-font-family-to-sans-while-converting-from-markdown-to-html
> - I've recently updated and streamlined the CSS I use to generate simple
> HTML files (or publish to my blog), and was surprised how minimal it can
> be, while still looking pretty good (IMHO). The idea is to rely on browser
> defaults as much as possible (which are fairly consistent nowadays), so you
> don't have to override/normalize a lot.
>
> The new CSS is added by default when using the `--standalone` option,
> unless you also use the `--css` option or convert to slideshows. Inclusion
> can be disabled e.g. with `pandoc -M document-css=false`. Or customized
> (like all templates and template partials) by adding your own file to
> ~/.pandoc/templates/styles.html.
>
> There are a few variables like `mainfont`, `fontsize` etc. that you can
> set, similar to what we already have in the LaTeX template. Have a look at
> the proposed changes to the MANUAL (and to styles.html):
>
> https://github.com/jgm/pandoc/pull/6601/files


--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124


  parent reply	other threads:[~2020-08-23 11:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 11:23 mb21
     [not found] ` <41422a08-cc8d-4480-8bfc-03d907cb2794n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-23 11:54   ` Albert Krewinkel [this message]
     [not found]     ` <87r1rxa887.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-08-23 17:24       ` mb21
2020-08-24 17:51       ` Daniel Staal
     [not found]         ` <c26ebc5e-35e3-0e84-037e-d8fa1f119438-Jdbf3xiKgS8@public.gmane.org>
2020-08-24 18:42           ` mb21
2020-08-24 20:03           ` John MacFarlane
     [not found]             ` <m2v9h7x13x.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-08-29 10:06               ` Ganriel Nützi
     [not found]                 ` <6497A421-E81B-45BA-8148-47B9CFC94C78-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-08-29 12:52                   ` BPJ

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=87r1rxa887.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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).