I.4 Who this book is for and how to read it
Who this book is for
You have probably used the Documentize website once or twice. Maybe you merged two files with Merger and went away happy. This book is for the moment after that, when you want to master it: know what every app does, what makes it unique, how apps connect, and how to chain them to finish a real job. By the end of your first path you should be able to send a heavy report by email, turn photos into a searchable PDF, or understand a long document in minutes, without hunting for tools.
It is written for office workers, students, researchers, editors, lawyers' assistants, small-business owners and developers. You do not need technical knowledge. Where a technical word is unavoidable (OCR, text layer, PDF/A), it is explained the first time it appears and again in the glossary.
Three reading paths
flowchart TD
S[You are here] --> A{What do you need?}
A -->|I have a task| PA[Path A: recipes]
A -->|I want to know every tool| PB[Path B: the app chapters]
A -->|I want to automate| PC[Path C: beyond the browser]
PA --> M[Part III map]
PB --> M
PC --> M
Path A: "I have a task"
Start with the goal, not the tool.
- Open the goal finder and find your sentence ("I want to send a big report by email"). For that one the recipe is Send a big report by email, a chain of Delete Page, Optimize and Compressor.
- Open the matching recipe in Part XII. Each one lists the starting state, the chain of apps, the options and a check at the end.
- When a step confuses you, follow its link to the app chapter.
Path B: "I want to know every tool"
Read by family. Every family has a landing page, one chapter per app, a practical lab, and a page on how the family works together.
| Family | Start here |
|---|---|
| Organize | 04-organize |
| Add & Structure | 05-add-structure |
| Protect & Prove | 06-protect |
| Shrink, Clean & Repair | 07-shrink-repair |
| Extract, Read & Search | 08-extract |
| Convert & Create | 09-convert-create |
| AI: understand documents | 10-ai-understand |
| AI for developers and teams | 11-ai-dev |
Read Part II before any of them. It takes half an hour and saves you hours.
Path C: "I want to automate"
Go to Beyond the browser. Start with Which channel when, then pick command-line plugins, the MCP server for AI assistants, the web API or self-hosting. Do at least one recipe by hand first, so you know what you are automating.
How every app page is built
All app chapters in Parts IV to XI use the same twelve headings, so you learn the pattern once:
- In one sentence
- What makes it unique
- When to use it / when not to
- Before you start (what state the document must be in)
- Step by step
- Options explained
- What you get
- Quality & limits (lossless, lossy, recognised or generated)
- Works well with (use before, use after)
- Common mistakes & fixes
- Same thing elsewhere (CLI, MCP, API)
- Try it
Two further elements recur. Each family ends with a lab: a hands-on project that chains the apps. And each family has a combos page about how its apps work together.
Conventions you will meet
| You see | It means |
|---|---|
| "the site states..." | A claim taken from the app's own page or FAQ. The book reports it; it does not guarantee it. |
| "(verify on the live app)" | The book found a mismatch or an unclear point in the product. Check it with your own file. |
| Not available / retired | The tool is described in the plan but does not work today, or has been withdrawn. The chapter says what to do instead. |
| Screenshot placeholder | A picture is planned at that spot. |
Numbers and promises
Limits, prices and allowances change and differ between environments. This book gives a number only where the product's page or FAQ states it, and then says so. For anything else it points you to the pricing page and tells you where the number comes from.
Next
Time to see what is actually on the shelf. Every app on one page: the portfolio →, and then Part II if you want the shared ideas first.