public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: mb21 <mauro.bieg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Adding minimal CSS to pandoc's default HTML template
Date: Sat, 22 Aug 2020 04:23:34 -0700 (PDT)	[thread overview]
Message-ID: <41422a08-cc8d-4480-8bfc-03d907cb2794n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]

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

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/41422a08-cc8d-4480-8bfc-03d907cb2794n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2070 bytes --]

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 11:23 mb21 [this message]
     [not found] ` <41422a08-cc8d-4480-8bfc-03d907cb2794n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-08-23 11:54   ` Albert Krewinkel
     [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=41422a08-cc8d-4480-8bfc-03d907cb2794n@googlegroups.com \
    --to=mauro.bieg-re5jqeeqqe8avxtiumwx3w@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).