Reusing artwork with libraries and snippets in Layout by Zaweba
Keep reusable items in object libraries (.zalib), save a selection as a snippet (.zals) and reach recent colours and fonts in the Assets panel.
Every organisation has pieces it uses again and again. A logo lock up, a standard advert footer, a sidebar design, a set of icons, a contact panel. Rebuilding them each time wastes effort and leads to small differences between versions. Layout by Zaweba has three tools for keeping them to hand: object libraries, snippets and the Assets panel.
Object libraries
An object library is a file, saved as .zalib, that holds a collection of objects you can drag onto any page. Think of it as a drawer of ready made parts. A magazine might have a library of section headers, standfirst boxes and caption styles; a charity might have one with its logo, donation panel and legal text; a designer might keep one per client.
Because the library is its own file, it isn't tied to one document. Open it while working on any job and the same parts are there. Keep libraries in a shared folder and everyone working on a brand can use the same pieces.
Snippets
A snippet, saved as .zals, is one selection exported to a file. Select a group of frames, export them as a snippet, and you have a file that can be brought into another document as that same selection.
Snippets suit one off transfers and handovers. Send a finished advert panel to a colleague as a snippet, or keep a complicated layout element as a file in a project folder. Where a library is a collection you keep adding to, a snippet is a single package.
The Assets panel
The Assets panel shows recently used colours and fonts. When you are building a page and need the colour you used three spreads ago, or the font from the cover, it is there without searching through the swatches or font list. It is a small convenience, but on a long working day it saves a lot of hunting.
How these fit with styles and templates
Libraries and snippets carry objects; styles carry formatting. They work best together. Build library items with object and paragraph styles rather than hand formatting, so they belong to the house style rather than carrying stray formatting from wherever they were made.
Templates are the other side of reuse. A template, saved as .zalt, sets up a whole document with its pages, parents and styles. Libraries then provide the parts that go on those pages.
Building a useful library
Keep it tidy. A library with hundreds of unnamed items is hard to search. Name items clearly by their purpose.
Store finished, approved versions only. If the logo changes, update the library item, not just the copy on one page.
Keep a library per brand or client rather than one huge drawer of everything.
Group the parts of a complex item before adding it, so it arrives as one piece.
Mistakes people make with reuse
Copying and pasting from old documents instead of using a library brings old mistakes along. A library item is the approved version.
Letting libraries drift, with several slightly different versions of the same footer, defeats the point. Remove old versions.
Forgetting linked pictures matters too. A library item with a placed photo refers to that photo's file. Keep library pictures in a stable shared folder so they don't go missing.
None of these tools is dramatic. Together they mean the parts of a job that never change are made once, kept in one place and dropped in when needed, which leaves your time for the parts that do change.
