However, I have some legalese that I need to add before the Table of Contents and I cannot identify where I would place the legal jargon before the ToC.
Here is my MWE for the module.md file I am using. I convert the module.md to a PDF file using pandoc. This preamble generates a ToC immediately after the title page. The legalese you see here then follows the ToC. I would like to have the legal jargon first and then the ToC.
Code: Select all
---
title: "Working Title"
subtitle: "Revision 1"
author: "Guide"
date: "Today's Date"
course_number: EDU-BLAH-BLAH
subject: ""
keywords: [blah, blah, and blah]
lang: "en"
geometry: "left=0.5in,right=0.5in,top=1.0in,bottom=1.0in"
disable-header-and-footer: true
titlepage: true
titlepage-logo: Extras/Graphics/logo.jpeg
toc: true
toc-own-page: true
listings-disable-line-numbers: true
listings-no-page-break: false
colorlinks: true
code-block-font-size: \footnotesize
header-includes:
- |
```{=latex}
\usepackage{awesomebox}
\usepackage{fancyvrb}
\usepackage{float}
\floatplacement{figure}{H}
\usepackage{fvextra}
\usepackage{listings}
\usepackage{marginnote}
\usepackage{setspace}
\setstretch{1.10}
\usepackage{xcolor}
\lstset{basicstyle=\small\ttfamily,columns=flexible,breaklines=true}
\newcommand\userinput[1]{\textbf{#1}}
```
pandoc-latex-environment:
tcolorbox: [box]
norm-box: [norm]
info-box: [info]
warn-box: [warn]
learn-box: [learn]
error-box: [error]
attn-box: [attn]
code-box: [code]
cb-box: [cb]
learn-box: [learn]
scenario-box: [scenario]
outline-box: [outline]
prereqs-box: [prereqs]
labtime-box: [labtime]
tipblock: [tip]
noteblock: [note]
warningblock: [warning]
cautionblock: [caution]
importantblock: [important]
blockquote: [blockquote]
...
<!-- page break from preamble above -->
\begin{scriptsize}
This document is produced by blah.
This document or any part thereof may not be reproduced or transmitted in any form under penalty of law, without the prior written permission of blah.
Copyright legalese blah....
Copyright © 2024 Blah, Inc. All rights reserved.
Printed in USA.
Revision History:
Revision 1---August 2024
The information in this document is current as of the date listed previously.
The information in this document has been carefully verified and is believed to be accurate to reflect the latest release available at publication.
\end{scriptsize}
Any suggestions are appreciated.