The afternoon this lesson exists to prevent
A designer lays out an 80-page college prospectus. Each page is built by hand: text boxes placed individually, the running head copied onto every page, the page number typed. It looks fine.
Then the client says the body font should be Lato, not Poppins.
If the file was built with styles, that is one dialog and about forty seconds. If it was not, it is six hours of clicking, and three paragraphs somewhere in the middle will be missed and go to press wrong.
The whole reason layout applications exist as a separate category from drawing applications is this problem, and the features that solve it.
What a layout application gives you that a drawing application does not
- Linked text frames. Text flows from one frame to the next and across pages, so adding a paragraph on page 3 reflows everything after it. In a drawing program, every text box is an island.
- Master pages. Running head, folio, margin guides and any repeating furniture live on a master. Change it once, it changes on all 80 pages.
- Automatic page numbers, which renumber when you insert a page.
- Styles, which is the rest of this lesson, and tables that behave like tables.
- Preflight, a live check for missing images, overset text, RGB pictures and missing fonts.
- Package / Collect for Output, which gathers the document, every linked image and every font into one folder to send.
The tools:
- Adobe InDesign — the industry reference. Subscription.
- Affinity Publisher — very capable, was a one-off purchase, terms changed after the Canva acquisition in 2025; check.
- Scribus — free, open source, mature, and its PDF/X export is excellent. The interface is dated and some things are clumsy. It has laid out a great many real books.
- CorelDRAW does multi-page and has paragraph styles, and is perfectly reasonable up to about twenty pages. Its text flow model is weaker, so a long document is harder work than it needs to be.
- LibreOffice Writer with proper styles will produce a decent 200-page interior for a novel, and it is free and runs on anything.
A style is a name for a set of decisions
That is the whole idea. "Body" means 10/14 pt Lato, ragged right, 0 space before, 3 mm space after, hyphenation on. Once it has a name, you can change the decisions behind the name and every paragraph carrying it updates.
The value is not that applying a style is fast. It is that the change is centralised. Design work is mostly revision, and revision is where unstyled documents fail.
Three kinds:
- Paragraph styles for whole paragraphs: body, heading, caption, list item.
- Character styles for spans inside a paragraph: bold run-in lead, a different font for a botanical name, a colour on a cross-reference.
- Object styles for frames: fill, stroke, text inset, corner radius.
And based-on inheritance is what makes it worth doing properly. Define "Body". Then define "Body Indent" as *based on Body*, changing only the first-line indent. Then "Body Small" as *based on Body*, changing only the size. Change Body's typeface and all three follow. Build your styles as a family, not as a list.
Colour works the same way: define a swatch, name it, use it everywhere, and a brand-colour change becomes one edit.
The mistake that makes people distrust styles
You change the style. Thirty paragraphs do not update.
Almost always the cause is a local override. Someone selected that text and set the font directly, on top of the style. The direct formatting wins, and the style change never reaches it.
InDesign shows a + next to the style name in the Paragraph Styles panel when the selection has overrides. Alt-click the style name to apply it and clear overrides at the same time. Scribus and Affinity Publisher have equivalent behaviour with different names.
The discipline: format by applying a style, never by reaching for the font dropdown. If you need a variation, make a style for it. This feels slow for the first ten minutes of a document and saves the whole afternoon described at the top.
Two more things worth setting up on day one
A baseline grid. Set it to your body leading — if the body is 10/14, the grid is 14 pt — and align the body style to it. Text in adjacent columns then sits on exactly the same lines, and a spread looks composed rather than approximately aligned.
Linked, not embedded, images. A linked image stays on disk and the layout holds a reference, so the document stays small and updating the photograph updates the layout. Embedding makes the file self-contained but bloated and stale. Use links, then Package before sending.
The one that pays
Data merge. Five hundred visiting cards with different names, or 300 certificates, or price labels for a whole shop, from a CSV file. InDesign has Data Merge, CorelDRAW has Print Merge, Scribus does it with the Generator script. Set up the template once, point it at the spreadsheet, produce 500 personalised pages in a minute.
This is well-paid, unglamorous, repeatable work that almost no one advertises being able to do. If you learn one thing from this lesson beyond styles, learn this.
Leave imposition alone
Do not build your own printer's spreads or gang up pages unless you have been asked to. Supply single pages at trim size in reading order, with bleed. The press imposes for its own machine, paper and folding, and a helpfully pre-imposed file usually has to be taken apart again.
Today
Open any multi-page document you have made. If there are no named paragraph styles in it, rebuild the first three pages with them. You will finish the remaining pages faster than the ones you already did.
Before you move on