Gated content

A whitepaper that is handed out after a registration needs two editions. One build run produces both.

In the backend module

Under Build a new edition three settings come with this package:

Setting	What it does
Build a preview edition as well	writes <slug>-vorschau beside the edition
Pages in the preview	how many pages it holds
Unguessable slug	appends a random key to the full edition
Split double pages into single pages	cuts sheets that carry two book pages

On the command line

vendor/bin/typo3 flippdf:build whitepaper.pdf whitepaper-2026 \
    --vorschau-ausgabe 5 \
    --zufallskennung \
    --doppelseiten

Out of it come:

• whitepaper-2026-vorschau — the first five pages, no download. This is the one that goes on the landing page.
• whitepaper-2026-a7f3c9d2 — all pages with the download. This link belongs in the confirmation mail, and nowhere else.

--vorschau-kennung names the preview if <slug>-vorschau does not fit.

Why a second edition and not the preview mode

The viewer of the base package can show only the first pages of an edition. That is enough for a taste, but it is not a protection:

• The preview loads a shortened description file, teaser.json.
• The complete book.json stays next to it in the same directory.
• It lists every page image by name.

Whoever knows the address of the edition — and it stands in the source of the landing page — has the whole document. With a separate edition there is nothing to find: the public directory holds five page images and no PDF.

Check it yourself

Open the preview edition, add book.json to its address and count the pages listed. That is what a visitor can do too.

Rebuilding

The extent and the name of the preview are kept in the full edition. A rebuild therefore renews the preview along with it, and the preview has no rebuild button of its own — clicking it would fill the public directory with the whole document.