The System Behind Trail Walker

(Newspaper Edition)

At a glance

• 35 paragraph styles
• Object styles for 2 caption types and 2 sidebar styles
• Single parent page set; page layouts saved as library items
• Actual .indt template file (vs. IDML workflow used for Curl)
• 5-column grid designed from scratch for the redesign
• Collaborative Dropbox workflow with shared InDesign files
• PDF/X-1a export with crop marks and bleeds
• InSite digital proofing pipeline
• Full issue production typically completed within 2 weeks

TLDR: Building and maintaining the InDesign production system behind 27 issues of Trail Walker — a 5-column grid redesign, template development, and a collaborative editorial workflow modeled on daily newspaper production.

The production system behind Trail Walker’s newspaper format was built on a foundation I understood well: the collaborative editorial workflow I’d had working at Metro US. When my former Metro colleague brought me in to redesign Trail Walker, we carried the same production rhythm into the project that we’d used in newsrooms — pre-edited copy, shared files, designer and editor working in the same InDesign documents. At Metro that had meant a CMS; for Trail Walker, we replicated it with a shared Dropbox folder. Clean, efficient, and built on mutual trust developed over years of working together under daily newspaper deadlines.

The redesign itself started with the grid. The original Trail Walker suffered from cramped, unbalanced pages with no clear visual hierarchy and not enough breathing room. Informed by years of newspaper production experience, I decided on a 5-column grid for the 11×17 publication, giving the layout more flexibility and significantly more white space. That grid stayed consistent across all 27 issues I produced of the newspaper format.

The template system was a proper .indt file rather than the IDML-based workflow I used for Curl Magazine. (Trail Walker involved another person working in the same InDesign files, which made a clean, stable template the right choice.) Page layouts for recurring sections were saved as library items, so starting a new issue meant pulling the right page structure from the library rather than rebuilding from scratch each time.

The document architecture was built around 35 paragraph styles, with object styles handling the two caption types and two sidebar styles that recurred throughout every issue. Some elements stayed fixed by client preference — a standing spread with a light topographic line background, for example — while the rest of the layout adapted to each issue’s content.

Content arrived as Word docs via the shared Dropbox folder, avoiding email attachments entirely. Preflight followed standard checks, with saved printer job options including crop marks and bleeds for the commercial print run. Digital proofs came back through InSite, the industry-standard proofing platform, before final approval and file delivery.

Full production of each issue — from receiving content to sending print-ready PDFs — typically ran about two weeks.

This production system supported the layout of Trail Walker →