public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc to PDF -- How to add cover before title and toc
Date: Tue, 29 Dec 2020 11:18:26 -0800 (PST)	[thread overview]
Message-ID: <b4b21bca-bc6d-454d-940a-6dc254b50c37n@googlegroups.com> (raw)
In-Reply-To: <7d9c7d1b-4198-44f0-85b1-2f79b77e3dc6o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

You can modify the default LaTeX template.  Look specifically for the bit 
starting with "$if(title)$".  You'd want your content to come before the 
\titlepage content, so before the $if(title)$.

(Disclaimer: Not an expert.)
On Tuesday, 29 December, 2020 at 12:50:04 am UTC+5:30 LRP wrote:

> I'm developing a series of operations manuals. I'd like to place cover 
> markdown content before title page and toc. I've tried:
>
> Directory
>
> 1-WGCover.md
> 2-Writersglen.md
>
> YAML:
>
> ---
> title: |
>        | ![](WGLogo.png){ width=2.5in }
>        | _____________
>        |
>        | Business Plan
>        | Development
>        | Deployment
>        | Marketing
>        | Operations
>        | _____________
>
> author: Lloyd R. Prentice
> date: May 7, 2019
>
> ...
>
> Pandoc call:
>
> pandoc \
>     -s \
>     1-WGCover.md \
>     2-Writersglen.md \
>     --top-level-division=chapter \
>     --toc \
>     -o \
>     Writersglen.pdf
>
> ...and
>
> pandoc \
>     -s \
>     *.md \
>     --top-level-division=chapter \
>     --toc \
>     -o \
>     Writersglen.pdf
>
> But in both cases the cover content comes after the toc.
>
> Can anyone suggest a solution?
>
> Thanks,
>
> LRP
>
>
>
>

-- 
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/b4b21bca-bc6d-454d-940a-6dc254b50c37n%40googlegroups.com.

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

  parent reply	other threads:[~2020-12-29 19:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 19:20 LRP
     [not found] ` <7d9c7d1b-4198-44f0-85b1-2f79b77e3dc6o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-29 19:18   ` Pranesh Prakash [this message]
     [not found]     ` <b4b21bca-bc6d-454d-940a-6dc254b50c37n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-12-30 19:46       ` Lloyd R. prentice
     [not found]         ` <476c4e27-6c1a-4275-be42-a6cc6febff78-jFIJ+Wc5/Vo7lZ9V/NTDHw@public.gmane.org>
2020-12-30 20:19           ` T. Kurt Bond
     [not found]             ` <CAN1EhV9cEVoaznUXXY9CGAxpY3DnVD4cw4WKFB3BgxTb2eUGnw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-01-04 22:38               ` Lloyd R. prentice

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=b4b21bca-bc6d-454d-940a-6dc254b50c37n@googlegroups.com \
    --to=the.solipsist-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).