Where to go next
You made it through the whole track. You installed the engine, styled text, built tables, added headers, and rendered Hypertext Markup Language (HTML). This page is the map for everything after: where to go, and when.
What you will build
Section titled “What you will build”There is no script this time. You leave with two things: a map of the documentation, and your first three recipes to build.
The map
Section titled “The map”Find the row that matches your next need. Each destination explains itself once you arrive, so this table stays short on purpose.
| Destination | When to go there | Link |
|---|---|---|
| PHP cookbook | You know the task — a watermark, a merge, a barcode — and want one complete recipe for it | PHP cookbook |
| Integration cookbook | You run NextPDF inside a framework, a queue, a container, or behind a server | Integration cookbook |
| Choose your path | You are deciding which distribution and edition fit your project before you commit | Choose your path |
| Reference | You need an exact Application Programming Interface (API) signature, or a support matrix for fonts and styles | Reference |
| Migration | You are moving an existing codebase from TCPDF, FPDF, mPDF, or Dompdf | Migrate to NextPDF |
| Frequently asked questions (FAQ) | You have a quick question that other newcomers have probably asked before | NextPDF FAQ |
| Insider_ | You want the engineering essays on why the engine behaves the way it does | Insider_ |
| Troubleshooting | Something failed, and the error message alone did not tell you enough | Troubleshooting |
One more bookmark: the glossary defines every piece of Portable Document Format (PDF) jargon used across these pages.
Your first three recipes
Section titled “Your first three recipes”A recipe is a short, task-shaped page: one goal, one complete script, one result. These three build directly on what you made in this track.
- Embed and subset a TrueType font (TrueType is the most common font file format; subsetting keeps only the characters you used, so the file stays small) — in Text, fonts, and pages you used the built-in fonts; this recipe brings in your own font files.
- Set document metadata (title, author, language) — every document you built deserves a real title, author, and language, so viewers can identify it.
- Style HTML with CSS — take the styled page from HTML to PDF further, and learn which Cascading Style Sheets (CSS) properties are safe to rely on.
There is no next tutorial — you graduated. Pick one of the three recipes above and build it while everything is still fresh. From here on, the PHP cookbook is your home base: one task at a time.