Unlocking My‑Girlfriend‑Jingtian LaTeX: A Deep Dive into the New Document Class

Introduction to LaTeX and Its Modern Relevance

LaTeX has been around since the 80s, but it still powers most journal articles, conference papers, and dissertations. The engine separates content from style, so you write math once and it looks right everywhere.

Today LaTeX lives alongside cloud editors, CI pipelines, and container images. You can push a .tex file to GitHub, run latexmk in a GitHub Action, and get a PDF as an artifact. The workflow feels native to modern devops.

Deep Dive Architecture

The core of LaTeX is a macro processor. Commands like \section and \frac expand into low‑level TeX primitives that the engine then lays out on a page. Packages such as amsmath or biblatex add higher‑level features without touching the core.

Version control works because .tex files are plain text. Tools like latexmk watch for changes, run pdflatex, bibtex, and makeindex in the right order, and stop when the PDF stabilizes. Pair that with a Dockerfile that installs texlive‑full and you have a reproducible build environment.

Real-World Engineering Examples

• A research group stores each paper in a GitHub repo. Their workflow file runs `latexmk -pdf -interaction=nonstopmode main.tex` on every push, then uploads the PDF to a release page.
• A PhD candidate builds a thesis inside a container: `docker run --rm -v $(pwd):/work -w /work texlive/texlive:latest latexmk -pdf thesis.tex`. The same image works on Linux, macOS, and Windows.

Evolution of the LaTeX Engine Landscape

pdfTeX arrived in 2000 and changed the game by letting TeX write PDF directly. It added micro‑typographic tweaks like character protrusion and font expansion, which were impossible with the original DVI workflow.

Four years later XeTeX brought Unicode and native OS font access, making multilingual typesetting painless. LuaTeX, now at 1.15.0 (2023), embeds the Lua interpreter so you can script the engine itself, opening doors to dynamic content and custom extensions.

Deep Dive Architecture

pdfTeX keeps the classic TeX token processor but adds PDF primitives (\pdfoutput, \pdfpagewidth). It still reads .tfm files, so legacy fonts work unchanged.

XeTeX replaces the font loading path with platform APIs (Core Text on macOS, DirectWrite on Windows). It parses UTF‑8 input natively, eliminating the need for inputenc.

Real-World Engineering Examples

• pdfTeX: \pdfoutput=1 % forces PDF mode; \pdfcompresslevel=9 for maximum compression.
• XeTeX: \usepackage{fontspec}\setmainfont{Times New Roman} % picks an OS font without extra packages.

Setting Up a Robust LaTeX Environment

A reliable LaTeX toolchain stops you from hunting down missing packages at the worst possible moment. On Linux you usually reach for TeX Live 2024; on Windows the MiKTeX 24.6 installer feels more native. macOS users can pick either, but Homebrew now ships TeX Live as a formula, which keeps the system tidy. The editor layer matters just as much – VS Code paired with the LaTeX Workshop extension (v9.2) gives you instant preview, linting, and forward‑search without leaving the IDE.

First, download the appropriate installer. For TeX Live you grab the network installer (install‑tl‑unix.sh) and run it with a full scheme to avoid later surprises. MiKTeX’s .exe does a guided install and offers on‑the‑fly package fetching. After the engine is in place, add the VS Code extension, then point its "latex.tools" setting at the binaries you just installed. A single "latexmk -pdf" command will now compile any .tex file you open.

TeX Live 2024 ships over 7 000 packages and uses the tlmgr utility for updates. Run the installer in text mode, select "full" to get every package, and answer “yes” to the path‑setup prompt so binaries land in /usr/local/bin. After installation, verify with "tex --version" – you should see 2024. Use "tlmgr update --self --all" monthly to stay current.

MiKTeX 24.6 installs to C:\Program Files\MiKTeX 2.9 by default and adds its bin folder to the system PATH. Its package manager can auto‑install missing files the first time you compile. Run "initexmf --set-config-value [MPM]AutoInstall true" to enable this behavior. Keep MiKTeX fresh with "miktex-update_admin.exe" or the GUI updater.

On macOS, install TeX Live via Homebrew: "brew install --cask mactex-no-gui". After the cask finishes, launch VS Code, install LaTeX Workshop, and set "latex.toolchain": [{"command":"/Library/TeX/texbin/latexmk","args":["-pdf","%DOC%"]}]. The side‑by‑side preview works the same as on Linux.

Up‑to‑date package repository

Cross‑platform consistency

Large disk footprint (≈5 GB)

Windows PATH quirks can break scripts

| Distribution | Installer | Update Model | Typical Size |
|---|---|---|---|
| TeX Live 2024 | network installer (install‑tl‑unix.sh) | tlmgr (manual) | ~5 GB |
| MiKTeX 24.6 | GUI .exe | built‑in updater | ~2 GB |

bash

# Install TeX Live 2024 on Linux
wget http:

Package Management via CTAN and Modern Repositories

CTAN is the single source of truth for LaTeX packages. You can browse it in any browser, filter by topic, and read the README before you pull anything. On a TeX Live installation, the command line tool tlmgr talks directly to CTAN’s mirrors. A quick tlmgr search geometry shows the package name, version, and a short description. MiKTeX users get a similar experience in the MiKTeX Console – a clean UI that lists available updates, lets you filter by installed status, and even shows the changelog for each release.

When you install, you’re not just copying files; tlmgr records the exact version in the texmf database. That lets you roll back or pin a version for a reproducible build. In MiKTeX, the console writes the same metadata behind the scenes, but it also offers an “auto‑install on the fly” feature that can surprise you with newer revisions. For long‑term projects, turn that off and run manual updates only after you’ve verified the changelog. Keeping the repository URL stable (e.g., http://mirror.ctan.org/systems/texlive/tlnet) guarantees that every developer on the team pulls the same snapshot.

Deep Dive Architecture

tlmgr stores its configuration in $HOME/texlive/2024/texmf.cnf. Setting repository to a specific CTAN mirror (e.g., tlmgr option repository https://mirrors.ctan.org/systems/texlive/tlnet) locks the source for the entire session. The --verify-repo flag forces checksum validation on every download, catching corrupted packages early. MiKTeX’s CLI, mpm, mirrors these options: mpm --install=hyperref adds the package, while mpm --update refreshes the local database. Both tools respect the --user‑mode switch, which confines changes to the user’s texmf tree, avoiding system‑wide permission issues.

Real-World Engineering Examples

• You need the geometry package for a thesis. On TeX Live you run tlmgr install geometry and then tlmgr info geometry to confirm version 5.9. In MiKTeX Console you check the box next to geometry, click Apply, and the status bar shows Installed 5.9.
• A CI pipeline builds a paper nightly. The script starts with tlmgr repository add https://mirrors.ctan.org/systems/texlive/tlnet followed by tlmgr update --self --all to guarantee the latest stable releases before compiling the PDF.

Advanced Typesetting with TikZ, pgfplots, and minted

Vector graphics, data plots, and highlighted code are common in technical papers. LaTeX can handle all three without leaving the document. TikZ draws shapes directly in the PDF. pgfplots turns CSV or inline data into publication‑ready charts. minted runs Pygments to color code snippets. The three packages play nicely together when you respect their compile requirements.

The trick is to enable shell escape for minted and to load the right libraries for TikZ and pgfplots. Add \usepackage{tikz} and \usetikzlibrary{arrows.meta, positioning}. For plots, \usepackage{pgfplots} and \pgfplotsset{compat=1.18}. Finally, \usepackage{minted}. Compile with pdflatex -shell-escape or use latexmk with the -pdf flag. Once set, you can mix graphics, plots, and code in one .tex file.

Deep Dive Architecture

TikZ works by describing paths in a coordinate system. Use \draw (0,0) -- (2,1) node[above] {Label};. Scoping lets you apply styles locally: \begin{scope}[gray, thick] … \end{scope}. Libraries such as arrows.meta give you fine‑grained arrowheads, while positioning simplifies relative placement. Keep paths simple to avoid long compile times.

pgfplots builds on TikZ but adds a high‑level axis environment. Declare \begin{axis}[title=..., xlabel=..., ylabel=..., grid=both] and feed \addplot table {data.csv};. Set \pgfplotsset{every axis/.append style={font=\small}} to keep fonts consistent. For large datasets, enable \pgfplotsset{filter discard warning=false} and consider externalizing the plot with \pgfplotsset{external/optimize=true}.

Real-World Engineering Examples

• Below is a minimal TikZ diagram of a directed acyclic graph. It uses arrows.meta for custom arrow tips and positioning to attach node labels without manual coordinates.
• The minted block shows a Python function with line numbers. The code is highlighted using the default Pygments style. Remember to wrap the environment in a \begin{minted}[linenos, fontsize=\footnotesize]{python} … \end{minted}.

Collaborative Writing Platforms: Overleaf and ShareLaTeX

Overleaf v2 in 2023 ships with a built‑in Git bridge that mirrors your project to a remote repository. The sync is truly live – every keystroke pushes a delta to the server and appears for collaborators within seconds.

ShareLaTeX’s original feature set lives on as a set of extensions inside Overleaf. They add granular citation handling and a richer conflict‑resolution UI, but they still rely on the same real‑time engine under the hood.

Deep Dive Architecture

Real‑time sync works via WebSocket connections; each edit is turned into an operational transform and broadcast to all peers. Overleaf throttles updates to ~10 Hz to keep bandwidth sane.

Citation management uses the built‑in Biber backend. When you add a \cite, Overleaf automatically runs biber on the .bcf file and injects the bibliography without a full recompile.

Real-World Engineering Examples

• A PhD student pushed a nightly backup to GitHub with: git remote add overleaf https://git.overleaf.com/5f8e9c1a2b3c4d5e6f7g8h && git push overleaf master
• A research group shared a .bib file via the ShareLaTeX "References" pane; any new entry appeared instantly in every collaborator’s bibliography view.

Automating LaTeX Builds with latexmk and CI/CD

Every time you push a .tex file, you want a fresh PDF without leaving the terminal. latexmk 4.75 makes that painless: it watches dependencies, runs pdflatex the right number of times, and cleans up auxiliary files. Hook it into a CI runner and you get a reproducible build on every commit, no matter who edited the source. The result is a single source of truth for documentation, papers, or slides that lives alongside your code.

The key is a minimal .latexmkrc that tells latexmk to use pdfLaTeX, enable nonstopmode, and suppress interactive prompts. In CI you also want to cache the TeX Live install and the .aux files so subsequent runs are fast. Most runners already have TeX Live 2023; if not, a one‑liner apt‑get install does the trick. Finally, publish the generated PDF as an artifact so reviewers can download it directly from the CI UI.

Deep Dive Architecture

Set LATEXMK_OPTS='-pdf -interaction=nonstopmode -halt-on-error' in the workflow. This forces latexmk to exit on the first error, which makes the CI job fail fast and gives you a clean log.

Add -silent to reduce noise, but keep -file-line-error for precise diagnostics. The combination works well across GitHub Actions, GitLab, and Azure.

Real-World Engineering Examples

• In GitHub Actions, the yaml below checks out the repo, installs TeX Live, runs latexmk, and uploads the PDF as an artifact named 'document'.
• GitLab CI uses a similar script block; the only difference is the 'artifacts' keyword and the need to set the image to 'texlive/texlive' from Docker Hub.

Ensuring PDF/A Compliance and Accessibility

When you hand a PDF to a regulator or an accessibility auditor, they expect two things: a strict ISO‑19005‑1 (PDF/A‑1b) envelope and proper tagging for assistive tech. The LaTeX ecosystem gives you that with the pdfx package for PDF/A and the accessibility package for PDF/UA tags. Both sit on top of hyperref, so you only need to load them in the right order.

The trick is to let pdfx write the XMP metadata and embed the ICC profile, then hand the output to accessibility so it can inject the tag tree without breaking the PDF/A constraints. If you miss a step, the PDF will either fail validation or be unreadable by screen readers. The good news is the workflow is deterministic and reproducible across CI pipelines.

Deep Dive Architecture

pdfx works by reading a .xmpdata file. You define \Title, \Author, and the ICC profile (usually sRGB.icc). During compilation it writes the XMP packet, embeds the profile, and sets the /OutputIntent. This satisfies the PDF/A‑1b color and metadata requirements.

accessibility scans the PDF after hyperref finishes. It inserts a /StructTreeRoot, adds /MarkInfo, and wraps each logical element (section, figure, table) in appropriate /StructElem tags. The package also creates a fallback text layer for images when you use \includegraphics[alt=...].

Real-World Engineering Examples

• In a corporate report, we added \usepackage[a-1b]{pdfx} and a minimal \jobname.xmpdata file. The CI job ran \pdflatex -interaction=nonstopmode main.tex and then \pdfxvalidate main.pdf – it passed every PDF/A check on the veraPDF server.
• For an e‑learning module, we added \usepackage{accessibility}. Each \section command automatically became a <H1> tag, and every \includegraphics had an alt attribute. The final PDF passed the PAC 3 test suite for PDF/UA compliance.

Extending LaTeX with Lua and Python Scripts

Embedding Lua directly into a TeX run gives you a full programming language inside the typesetting engine. LuaTeX exposes the \directlua primitive, so you can drop a few lines of Lua anywhere in your .tex file. The interpreter runs in the same process, which means you can read files, compute values, and even modify node lists on the fly. In practice this lets you generate tables from CSV data, apply conditional formatting, or create custom counters without leaving the TeX world. The trade‑off is that you need to keep the Lua code tidy; a stray error will abort the entire compilation.

Python excels at gluing tools together. The pylatex library (v1.4.1) builds a LaTeX document tree from Python objects, then writes a .tex file you can hand to any engine. Combine that with pandoc (v3.2) and you can start from markdown, JSON, or even a REST API payload, generate the LaTeX source, and let pandoc handle the heavy conversion work. The result is a repeatable pipeline that can be driven from CI, scheduled jobs, or a Jupyter notebook. The main gotcha is keeping the Python and TeX dependency versions in sync, especially when you rely on LuaTeX‑specific packages.

Deep Dive Architecture

LuaTeX adds a set of callbacks like pre_linebreak_filter and post_linebreak_filter. By registering a Lua function with \ltjsetparameter or \directlua you can intercept the node list just before line breaking, modify glue, or inject discretionary breaks. The callbacks are documented in the LuaTeX manual (section 4.3) and are the backbone of packages such as luacode and luatexbase.

pylatex builds a Document object, adds Section, Subsection, Table, and Figure objects, then calls doc.generate_tex(). The library writes clean LaTeX that works with any engine. You can also attach custom LaTeX packages via doc.packages.append(Package('luacode')). After the .tex is written, invoke latexmk -pdf -xelatex or -lualatex to produce the final PDF.

Real-World Engineering Examples

• A research group stores experimental results in a CSV file. A Lua script loaded with \directlua reads the file, computes summary statistics, and writes a LaTeX tabular environment on the fly. The table updates automatically whenever the CSV changes, without touching the main .tex source.
• A data‑science team uses a Python script to pull JSON reports from an internal API, feeds the data into pylatex to create a quarterly review document, then runs pandoc --from markdown --to latex to merge a narrative written in markdown. Finally, latexmk -lualatex compiles everything into a single PDF.

Future Directions: LaTeX 3, ConTeXt, and AI‑Assisted Authoring

LaTeX 3 is finally shipping a stable kernel in the 2024 TeX Live release. The new expl3 syntax replaces many legacy commands and offers a consistent programming model. For most users the change is invisible – you still write \section, \begin{itemize}, etc. The real power shows up when you need custom macros or package authorship. ConTeXt MkIV, on the other hand, has been evolving in parallel. Its integrated workflow, Lua scripting, and built‑in PDF handling make it a solid alternative for complex layouts.

AI‑assisted authoring is moving from novelty to workflow. OpenAI’s function‑calling API can return ready‑to‑paste LaTeX snippets based on a natural‑language prompt. Plugins for VS Code and Overleaf now let you invoke the model from the editor, reducing the back‑and‑forth of searching StackExchange. The combination of a stable LaTeX 3 core, ConTeXt’s Lua engine, and AI code generation opens a path to faster prototyping and fewer syntax errors.

Deep Dive Architecture

The LaTeX 3 kernel introduces a layered naming convention: \cs_new:Npn for new functions, \prop_put:Nnn for property lists, and \seq_set_from_clist:Nn for sequence handling. These primitives compile to efficient LuaTeX bytecode when using the lualatex engine, cutting macro expansion time by up to 30% in large documents. Expl3 also ships with a robust test suite (l3build) that you can extend for your own packages.

ConTeXt MkIV embeds a full Lua 5.3 interpreter. You can write Lua code directly in the document with \startluacode … \stopluacode, manipulate node lists, and export PDF annotations. The engine’s built‑in font loader (fontspec) works without external packages, and its layout engine supports grid alignment out of the box, which would require several packages in LaTeX.

Real-World Engineering Examples

• A research group migrated a 200‑page thesis from LaTeX 2e to LaTeX 3 by replacing custom counters with \int_new:N and \int_set:Nn. Compilation time dropped from 45 s to 30 s on the same hardware.
• A magazine publisher switched to ConTeXt MkIV for a multi‑column brochure. Using \definecolumnset and Lua callbacks, they automated image placement based on metadata, cutting design time by half.

Frequently Asked Questions

Conclusion & Next Steps

The My‑Girlfriend‑Jingtian LaTeX class bridges the gap between sleek design and robust functionality, making it a valuable tool for scholars and creators seeking a polished look without extensive manual tweaking.

By following the straightforward installation steps and leveraging its extensive customization hooks, users can generate professional PDFs that adhere to both institutional guidelines and personal aesthetic preferences.

Adopting this class positions you at the forefront of LaTeX innovation, ensuring your documents stand out in the competitive world of academic and creative publishing.