Everything above begin{document}

Everything between \documentclass{...} and \begin{document} is the preamble. It produces no visible text; it configures the run. Fonts, margins, packages, custom commands, and document metadata all live here, which is why the preamble of a mature paper is often longer than its introduction. Understanding what each line does turns a copied template from an incantation into a checklist.

Anatomy

\documentclass[11pt,a4paper]{article}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage[margin=1in]{geometry}
\usepackage{amsmath,amssymb}
\usepackage{graphicx,booktabs}
\usepackage{hyperref} % load late

\title{Title}
\author{You}
\date{\today}

The options on \documentclass set global defaults: 11pt is the base font size everything else scales from, and a4paper declares the paper size. The two encoding lines are historical companions: inputenc tells the engine your source file is UTF-8, and fontenc selects font encoding so accented characters are real glyphs rather than composites. Current LaTeX assumes UTF-8 input already, so you will see these lines omitted in new documents, but they are harmless and templates keep them for compatibility.

The middle block loads capability packages. geometry sets the margins in one option, amsmath and amssymb provide the math environments and symbols nearly every technical document needs, graphicx enables \includegraphics for figures, and booktabs provides the rules that make tables look professional. Finally, hyperref makes references and citations clickable and is deliberately loaded last, because it redefines internals of many other packages.

The \title, \author, and \date lines only store metadata. Nothing prints until \maketitle runs in the body, which is why these can sit in the preamble at all.

Rules of thumb

A few habits keep preambles healthy. Load one package per job and resist stacking packages that fight over the same territory, such as two ways of setting margins. Keep hyperref at the end, with the handful of documented exceptions like cleveref that must come after it. Put document-wide choices in the class options rather than scattering them, so 11pt or twocolumn is declared once where anyone can see it. And once your custom macros outgrow a few lines, move them to a .sty file so multiple documents can share one set of definitions.

The most useful discipline is negative: if you do not know why a preamble line is there, find out before your document depends on it. Copied preambles accumulate dead lines, and dead lines are where package conflicts hide. See also the document skeleton and engines compared.