# MartinThoma/LaTeX-examples: A Practical Collection of LaTeX and TikZ Examples

> MartinThoma/LaTeX-examples is a large TeX repository for people who need working examples of LaTeX documents, mathematics, TikZ drawings, presentations, source-code layouts, and related typesetting techniques. Its per-example Makefiles make individual PDFs easy to build, but the collection is an example library rather than a complete LaTeX package or document class.

**MartinThoma/LaTeX-examples** — Examples for the usage of LaTeX

- Repository: https://github.com/MartinThoma/LaTeX-examples
- Stars: 1,692 · Forks: 413
- Language: TeX
- License: MIT
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/martinthoma-latex-examples

## What LaTeX-examples Contains and Who It Serves

MartinThoma/LaTeX-examples addresses a practical problem in LaTeX development: finding small, inspectable examples instead of starting from an empty document. The README describes the repository as containing more than 570 examples for LaTeX usage, and the top-level directories show the scope: `math/`, `tikz/`, `pstricks/`, `circuits/`, `documents/`, `presentations/`, `publications/`, `source-code/`, `uml/`, `images/`, `asymptote/`, `cheat-sheets/`, and `misc/`.

That structure makes the repository useful for researchers who need mathematical notation, students learning document preparation, and developers preparing diagrams or technical documents. It is also relevant to people who already know the basic LaTeX workflow but need a reference for a particular layout. The collection is not a single application with a command-line interface or a shared public API. It is a set of source examples organized by subject.

The repository's primary language is TeX, and its topics include LaTeX, mathematics, research, science, TikZ, and related diagram packages. The directory names are more informative than the README's short description. They show that the repository covers several kinds of output, from ordinary documents and presentations to mathematical diagrams and circuit illustrations.

This is an example library with a breadth-first catalog. It offers examples to copy, modify and inspect, but it does not provide a documented opinionated workflow for managing every dependency needed by every folder.

## The Per-Example Build Model

The documented build model is decentralized. The README states that every LaTeX file is in a separate folder and has its own Makefile. To generate a PDF, the reader can enter that example's directory and run `make`. This is a useful design for a repository containing unrelated typesetting experiments. A failed or incomplete example does not have to define the build process for every other example.

The top-level `.gitmodules` file also indicates that the project uses Git submodules, which is consistent with the README's instruction to clone recursively when all examples are needed offline. The repository layout contains `.gitattributes`, `.gitignore`, `CONTRIBUTING.md`, and `LICENSE`, in addition to the example directories. Based on that layout, the collection is meant to be read and built from the repository rather than installed through a package manager.

The README gives no single build target, dependency manifest, container image, or command that builds every example into one output directory. It also does not document a centralized test matrix. The `make` workflow therefore assumes that the reader selects an individual example, enters its folder and handles any requirements described there.

## Installing the Collection and Generating One PDF

The README points to a separate LaTeX installation guide and lists the practical requirements: a recent LaTeX version and, for the Makefiles, `make`. The repository itself does not document a package-manager installation such as `tlmgr` or `apt`, so those commands should not be inferred from the project documentation.

For a local checkout that includes the repository's submodules, the documented command is:

```bash
$ git clone --recursive https://github.com/MartinThoma/LaTeX-examples.git
```

After the checkout is complete, select one example directory rather than assuming that the repository root has a build target. The documented first use is to run the Makefile in the chosen directory:

```bash
$ make
```

The README states that this generates the PDF. The repository does not specify a universal output filename because each example has its own folder and Makefile. The reader should therefore inspect the chosen directory before building it and then look for the PDF produced there. If `make` is not installed, the Makefile route cannot be used without providing that external tool.

The README does not give a complete per-example dependency checklist for every directory. Folder-level README files are specifically called out for checking reuse conditions, so the target folder's documentation is part of the installation process rather than an optional extra.

## What the Directory Layout Tells You About Coverage

The directory names provide the clearest map of the collection. `math/` indicates mathematical examples, while `tikz/` and `pstricks/` cover two different diagram-oriented approaches in the repository. `circuits/` indicates circuit-related content, and `uml/` points to UML examples. `presentations/` separates presentation output from ordinary documents, while `documents/` and `publications/` represent different document contexts.

The presence of `source-code/` indicates attention to typesetting code within documents, and `images/` suggests examples involving graphics. `asymptote/` gives the repository a home for examples associated with that tool, while `cheat-sheets/` points to reference-oriented content. `misc/` acts as a catch-all category.

This organization is useful when you know the output you need. It also exposes a limitation: there is no unified index in the README that maps a particular task to a specific example file. The repository's breadth can therefore become a search problem. A reader looking for a particular table style, mathematical construction, diagram or publication layout must browse the relevant directory and inspect its files.

The repository description calls these examples for LaTeX usage, but the topic list and directory layout show that the scope is broader than plain document syntax. The collection is most valuable for visual and technical references, not as a substitute for documentation on LaTeX language semantics.

## Reuse Rules and Licensing Boundaries

The repository identifies its license as MIT. The README separately gives reuse guidance: users may use and modify the examples, but it asks them to add a link to the repository or `martin-thoma.com`. That request is part of the project's stated reuse conditions and should be considered when copying examples into another document or distributing a derivative collection.

The README also says that most content was created by the repository author, while directing users to the README files in individual folders to determine whether they can use a particular example. This distinction matters because a repository-level license does not replace the need to inspect example-specific documentation. The README does not describe the contents of every folder-level file, so it does not support a claim that every example has the same attribution or reuse status.

There is no documented GitHub release history. The repository has no releases according to the repository metadata, so version-to-version upgrade notes are not available. Users should treat the checkout and its submodules as the source of truth for the examples they copy, and should inspect `LICENSE`, the top-level README, and the selected example's README before redistribution.

## Limitations of an Example Collection

The main limitation is that this is not a unified build product. The README documents `make` per example, but it does not provide a documented command that builds all examples into a consistent deliverable. Some folders may also require external TeX packages or related tools that are not listed at the repository level. The README's broad requirement of a recent LaTeX version and optional `make` installation does not remove those per-example dependencies.

The project is also not a replacement for a maintained LaTeX distribution, editor integration, or package reference. It does not claim to explain the full LaTeX syntax, and the README does not document debugging procedures, automated tests, continuous integration, or rollback behavior. A user who wants a complete thesis template, a validated Beamer presentation workflow, or a reproducible academic publishing pipeline should not assume that selecting the relevant directory supplies all of those needs.

The breadth of the repository is another trade-off. More than 570 examples can be valuable for pattern discovery, but the README offers no per-example catalog, compatibility matrix, or maintenance policy for individual files. The directory-level organization helps, yet it still places the burden of finding and validating a suitable example on the reader.

The repository is not archived, and its last push was on 2026-09-28. That is the maintenance fact available from the repository metadata. The absence of GitHub releases means there is no release schedule to compare against the last push.

## LaTeX-examples Compared with a Package or Template

A real alternative is to use a focused LaTeX template or a local example from another project. The difference is in purpose. LaTeX-examples is a broad catalog of standalone demonstrations across mathematics, TikZ, PStricks, presentations, publications, UML, circuits and other areas. A template is usually designed around one document class or output type and may define a specific layout, metadata structure or publishing convention.

Another practical alternative is to keep a small personal collection of files that build in one controlled environment. That approach reduces the number of external dependencies and makes it easier to document exactly which TeX distribution and packages are required. LaTeX-examples offers more examples to inspect, but its breadth does not provide evidence that every example is compatible with one another or that the collection can be built as a single suite.

The choice depends on the task. Use this repository when you need to discover a technique or borrow a small pattern. Choose a focused template when you need a complete document workflow with a defined class and maintained project structure. Choose a controlled local collection when reproducibility matters more than variety.

## Choosing LaTeX-examples for a Real Project

LaTeX-examples is a reasonable reference for a researcher who needs a mathematical layout, a technical diagram, a presentation example or a document structure to adapt. The per-folder Makefile model is particularly useful for inspecting one example without committing to a repository-wide build process. The MIT license and the stated permission to modify examples also make the collection relevant to small adaptations, subject to the attribution request and folder-level guidance.

It is the wrong choice if you need a supported LaTeX class, a complete publishing system, or a guarantee that every example builds with one dependency set. It is also a poor fit for a user who does not want to inspect source files and manage TeX tooling. The README does not document automated compatibility checks or releases, so adoption should be based on the selected example rather than on the size of the collection.

The repository was not archived, and the last push was on 2026-09-28. Verify first that the chosen example's dependencies are available, read its local README, and run its own Makefile. If that example builds and its reuse terms fit the intended document, it is a concrete source to adapt.

## Conclusion

Adopt this repository when you need a concrete LaTeX, mathematics or TikZ example to study or adapt. Do not treat it as a turnkey LaTeX framework or assume that every example has identical dependencies. First inspect the target folder's files and README, verify that a current LaTeX distribution and `make` are available, and build only the example you intend to use.

## FAQ

### How do I install LaTeX-examples?

The README says to clone the repository with submodules if you want all examples offline. It does not document installation through a package manager; it links to a separate guide for installing a recent LaTeX version.

### How do I generate a PDF from LaTeX-examples?

Enter the folder for the selected example and run `make`. The README says that every LaTeX file has its own Makefile and that this command generates the PDF.

### Can I use LaTeX-examples in my own document?

The README says that the examples may be used and modified, with a request to add a link to the repository or `martin-thoma.com`. It also directs users to check the README in the specific folder before reuse.

## Sources

- [Issues](https://github.com/MartinThoma/LaTeX-examples/issues)
- [License: MIT](https://github.com/MartinThoma/LaTeX-examples/blob/master/LICENSE)
- [MartinThoma/LaTeX-examples on GitHub](https://github.com/MartinThoma/LaTeX-examples)
- [README](https://github.com/MartinThoma/LaTeX-examples/blob/master/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/martinthoma-latex-examples