@slide(layout=chapter-slide) @number 4 @title Project structure @slide(layout=content-and-preview) @title Goal @content Create a bigger LaTeX project and … * prevent LaTeX documents from growing monstrously 👹 * keep the overview over the project structure @preview {style="padding: .2em; height: 100vh"} @slide(layout=content-and-preview) @title Main file 👑 @content * contains basic structure and front matter * includes separate sections with \ `\input{path/to/file}` ``` {.lang-tex .hljs data-sourcefile=main.tex} \documentclass{article} \usepackage{babel} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \title{A Title} \begin{document} \maketitle \tableofcontents \input{section1.tex} \input{section2.tex} \end{document} ``` @preview  @slide(layout=content-and-preview) @title File with a section @content * contains **no preamble** * contains **no** `\begin{document}` or `\end{document}` ``` {.hljs .lang-tex data-sourcefile=part1.tex} \section{This is section 1} A paragraph about the content of section 1. % … ``` ``` {.hljs .lang-tex data-sourcefile=part2.tex} \section{This is section 2} A paragraph about the content of section 2. % … ``` @preview {.thin-padding} @slide(layout=content-and-preview-with-category) @category Excursion @title Specifying file paths 👣 @content * important for `\input{}`, but later also for other media types * file and folder structure = tree structure 🌳 @preview  @slide(layout=content-and-preview-with-category) @category Excursion @title Specifying file paths 👣 @content ### Absolute paths * path from the root directory to a file * the direcories are separated by special characters: * under UNIX: `/` * under Windows: `\`
absolute path for `main.tex`
* UNIX: `/home/knut/docs/latex/main.tex` * Windows: `C:\knut\docs\latex\main.tex`In **LaTeX,** you have to use UNIX-style paths. Therefore, we will use those from here on.
Relative path \ from `main.tex` to `part1.tex`
`./part1.tex` A **single dot ‘`.`’** in a relative path represents the current folder (in this case: `latex`). It is optional, you could also write `part1.tex` here.Relative path from `main.tex` to `part1.tex` in subfolder
`./sections/part1.tex` @preview  @slide(layout=content-and-preview-with-category) @category Excursion @title Specifying paths 👣 @content ### Relative pathsRelative path from `main.tex` in its own subfolder to `part1.tex` in another subfolder
`../sections/part1.tex` **Two dots ‘`..`’** represent the parent folder of the current folder (in this case: `latex`, parent of `main`). @preview  @slide(layout=content-only) @title Compiling the project @content * **Only the main file** has to be compiled to get the complete PDF document. * Error messages include a reference to the corresponding subfile. * Subfiles cannot be compiled on their own as they don’t have a preamble. @slide(layout=content-and-preview) @title Outsourcing the preamble @content What do you think happens when we outsource the preamble into its own subfile? Will the document compile? ++ **Yes, it will!** \ A simple way of keeping the main file even more organised. @preview {.thin-padding} @slide(layout=task) @task-number 4 @title A structured project @content You will find a file named `main.tex` in the folder `exercises/project-structure`. * Extract the sections into their own files (`section1.tex`, `section2.tex`, and `section3.tex`) and insert them using the `\input` command. * Have a look at the project archive, starting from `main.tex`. @slide(layout=content-only-with-category) @category Demo @title Compiling larger projects @content * From now on, we will compile the file `main.tex` in the project root. * To do so, right click on the file in TeXstudio and choose “Select as explicit root document” from the dropdown. * Next, compile as usual.