際際滷

際際滷Share a Scribd company logo

MagNet 2013 - PR1 2013

Kim Latreille
Kim Latreille

PR1 - Efficient Magazine Workflow for Production and Editorial These slides are from my presentation this morning at MagNet, Canada's Magazine Conference.

1 of 34
Download to read offline
PR1 Efficient Workflow for Production and Editorial Kim Latreille, Digital Media Consultant @kim_elle
Here is todays topic: Learn how you can integrate and streamline the process to make the whole magazine produc:on cycle easier and more e鍖cient, preven:ng nail-足bi:ng stress for everyone as deadlines begin to loom.
My best advice: The only way to prevent nail-足bi:ng is to get a good manicure.
Why listen to me? ≒ 20 years experience in a rapidly changing environment ≒ Magazine hoarder ≒ Closet geek/technology lover ≒ Prefers to do things once ≒ Pet peeve backtracking ≒ Capable of the odd joke
Some publica:ons Ive worked on:
Screen size varia,ons Delivery 鍖le format varia,ons No 鍖le standards What makes work鍖ow di鍖cult? Its the stu鍖 nightmares are made of.
Another problem is language. ≒ Print side versus Web side ≒ CMYK versus RGB ≒ 300 dpi versus 72 ppi ≒ Inches versus pixels ≒ PDF versus PNG ≒ Which route is be^er? ≒ Where do tablet edi:ons 鍖t then? They are a digital product
Whats common to both? HTML (or HyperText Markup Language) De鍖ni,on: a set of standards, used to tag the elements of a hypertext document. It is a text descrip:on language that is used for electronic publishing, especially on the web. So what about publishing in any format isnt electronic?
Who has heard these terms to describe magazine work鍖ow? ≒ Print-足Centric ≒ Web-足Centric ≒ Mobile-足Centric ≒ Content-足Centric ≒ Any thoughts on which of these might make the most sense?
It depends on who you ask. ≒ A print produc:on person Print-足Centric ≒ A interac:ve webby guy Web-足Centric ≒ A few industry analysts Mobile-足Centric ≒ An idealist Content-足Centric
In fact, this slide claims to represent a prac:cal HTML5 magazine work鍖ow: Source: h^p://www.slideshare.net/ mkowalski1/developing-足a-足 prac:cal-足html5-足magazine-足 work鍖ow Uh, wheres the printed magazine?
Where then, do we go from here? ≒ Unfortunately, the idealists Content-足Centric work鍖ow does not exist ≒ Print-足Centric work鍖ow is the one being used by most publishers ≒ Publishers are either: Too heavily invested in exis:ng technology Unwilling to shid to a new way of thinking ≒ Or both
Lets dig into Print-足Centric. ≒ Most publishers are knee-足deep in legacy systems and technology CMS such as K4, Woodwing Adobe InDesign QuarkXpress ≒ Publishers s:ll rely on print for almost 90% of their revenue ≒ Not surprising they think print 鍖rst
Cond辿 Nast and Adobe h^p://www.youtube.com/watch?v=34f13csGLIs ≒ Cond辿 Nast uses Adobe Digital Publishing Suite to produce enhanced digital edi:ons of their printed magazine ≒ Their approach is typical of many publishers who think print 鍖rst
The typical digital edi:on is sta:c. ≒ Most publishers have edi:ons on digital newsstands ≒ Many publishers choose print circula:on distributor rela:onships to get onto digital newsstands ≒ CDS Global ≒ Dis:cor ≒ More oden than not, these edi:ons are replicas of print edi:ons created from single page PDFs
Alterna:ve solu:ons: ≒ Solu:ons exist that allow publishers to use print PDF 鍖les to create digital edi:ons Issuu 3Dissue Uni鍖ip Zinio VirtualPaper Turnit Adobe Publishing Suite Texterity ≒ DIY advantage maintains control of your product ≒ Pricing and tools vary
Great digital DIY examples: ≒ The Kit h^p://www.thekit.ca/ Started as a digital-足only publica:on Originally built in partnership with Texterity ≒ Covet Garden h^p://covetgarden.com/ A digital magazine accessed on their website Uses an embedded viewer or open on iPad Created using Issuu
Delivering 鍖les for digital edi:ons: ≒ The majority use print PDF 鍖les to create the digital edi:on ≒ Re-足rip the PDF to tablet viewer speci鍖ca:ons Resolu:on, RGB colour-足space Create a jpeg 鍖le Two 鍖les delivered for each page ≒ PDF for zooming in ≒ jpeg for fast view
To 鍖nd e鍖ciency, I start here. ≒ Build a smart work鍖ow Address requirements for all edi:ons/plalorms ≒ Automate pain points Sodware and script within applica:ons ≒ Share resources across plalorms Mul:purpose content as much as possible Finding e鍖ciency across plaYorms requires a bit more crea,vity.
Crea:ng PDF 鍖les is the easy part. ≒ Using any design applica:on: PDFX-足1a is a standard senng Customized job op:on senngs can be imported to accommodate digital edi:on vendors PDF 鍖le speci鍖ca:ons ≒ If your premedia process is automated, both print and digital edi:on 鍖les can be created simultaneously ≒ PDF 鍖les can be created, named and delivered to each vendor/supplier
Now the job is done, so what? ≒ We have two iden:cal sta:c edi:ons of the magazine, one print and one digital ≒ Enhancing the sta:c digital edi:on pages happens once the PDF 鍖les are uploaded to the vendor ≒ Typically, you can enhance by adding: URL links Sound clips Embedded video Some might call that boring or a waste of the plaYorms biggest asset digital capability.
Evidence of the boring factor. Source: h^p://deadtreeedi:on.blogspot.ca/
Some applica:ons are more 鍖exible. ≒ Adobe Digital Publishing Suite, Woodwing and Virtual Publisher are all print/digital edi:on Content Management Systems ≒ Each works with InDesign within the CMS and allows the designer to: create versions for mul:ple plalorms view on mul:ple device templates ≒ CMS can manage internal work鍖ow and integrate editorial with ad material
Be^er controlled expecta:ons. Allows designer to view the layout on various screen sizes and tweak if necessary.
Some magazine content is published on websites. ≒ There are a few ways to make that happen: You can cut and paste Someone else can cut and paste ≒ Unfortunately, with all this terri鍖c technology, and the whole publishing process being digital, in a Print-足Centric work鍖ow this is the best cross-足plalorm solu:on weve got.
To bridge the gap. ≒ Some website developers have created sodware to help you manage content: Agility CMS Wordpress Squarespace There are several more, but Agility is very ac,ve with publishers, will customize their solu,on and help clients get rolling.
S:ll, its cut and paste. ≒ To avoid cut and paste, there are ways to take copy from InDesign and plop it into Wordpress. PageZepher from Markzware indexes content and exports to Wordpress Export from InDesign as XML and import into Wordpress (this ac:on can be automated) But it aint pre]y. A lot of work needs to be done by the web editor.
Images are another thing. ≒ Automa:on can be used share resources between print and web ≒ Scrip:ng sodware such as Enfocus Powerswitch can be set up to convert image 鍖les, then deliver them to web editors CMYK to RGB 300dpi to 72ppi (or whatever is required) Determine 鍖ow based on 鍖le type ≒ .ai goes through Illustrator ≒ anything else through Photoshop
Could it be easier? ≒ Yes ≒ A content-足centric approach could bene鍖t all plalorms, but applica:ons to support that work鍖ow for print edi:ons do not exist ≒ Not to men:on dyed-足in-足the-足wool print tradi:onalists convincing them to change is like pulling teeth
Is it possible to work another way? ≒ Who knows what responsive design is? ≒ Consider responsive design templates and how that works ≒ HTML5, CSS and tagging content HyperText Markup Language Cascading Style Sheets ≒ Di鍖erent styles can be applied depending on the output device being used ≒ Digital versions can be di鍖erent from printed versions, designers can tailor the presenta:on of elements for each plalorm
Responsive youve been served. Elements are served depending on screen dimensions, pixels per inch.
Torontoist website is responsive. ≒ Elements are recon鍖gured depending on what device you are viewing the website on ≒ Try it on your desktop, mobile device, tablet ≒ Try Chatelaine.com too
And why not a page of a magazine? ≒ Depends on who you ask ≒ Allows for content focus, i.e. Content-足Centric ≒ Some edi:ng would be required Audience considera:ons ≒ Yet, for moving content around in a work鍖ow for mul:ple devices, tagging would be an ideal solu:on ≒ Thoughts?
Ques:ons? ≒ Fire away ≒ Who is seeing Wes Bos this adernoon? ≒ Thank you for listening ≒ Keep in touch: kimlatreille@gmail.com Twi^er: @kim_elle h^p://kimlatreille.tumblr.com

More Related Content

MagNet 2013 - PR1 2013

  • 1. PR1 Efficient Workflow for Production and Editorial Kim Latreille, Digital Media Consultant @kim_elle
  • 2. Here is todays topic: Learn how you can integrate and streamline the process to make the whole magazine produc:on cycle easier and more e鍖cient, preven:ng nail-足bi:ng stress for everyone as deadlines begin to loom.
  • 3. My best advice: The only way to prevent nail-足bi:ng is to get a good manicure.
  • 4. Why listen to me? ≒ 20 years experience in a rapidly changing environment ≒ Magazine hoarder ≒ Closet geek/technology lover ≒ Prefers to do things once ≒ Pet peeve backtracking ≒ Capable of the odd joke
  • 5. Some publica:ons Ive worked on:
  • 6. Screen size varia,ons Delivery 鍖le format varia,ons No 鍖le standards What makes work鍖ow di鍖cult? Its the stu鍖 nightmares are made of.
  • 7. Another problem is language. ≒ Print side versus Web side ≒ CMYK versus RGB ≒ 300 dpi versus 72 ppi ≒ Inches versus pixels ≒ PDF versus PNG ≒ Which route is be^er? ≒ Where do tablet edi:ons 鍖t then? They are a digital product
  • 8. Whats common to both? HTML (or HyperText Markup Language) De鍖ni,on: a set of standards, used to tag the elements of a hypertext document. It is a text descrip:on language that is used for electronic publishing, especially on the web. So what about publishing in any format isnt electronic?
  • 9. Who has heard these terms to describe magazine work鍖ow? ≒ Print-足Centric ≒ Web-足Centric ≒ Mobile-足Centric ≒ Content-足Centric ≒ Any thoughts on which of these might make the most sense?
  • 10. It depends on who you ask. ≒ A print produc:on person Print-足Centric ≒ A interac:ve webby guy Web-足Centric ≒ A few industry analysts Mobile-足Centric ≒ An idealist Content-足Centric
  • 11. In fact, this slide claims to represent a prac:cal HTML5 magazine work鍖ow: Source: h^p://www.slideshare.net/ mkowalski1/developing-足a-足 prac:cal-足html5-足magazine-足 work鍖ow Uh, wheres the printed magazine?
  • 12. Where then, do we go from here? ≒ Unfortunately, the idealists Content-足Centric work鍖ow does not exist ≒ Print-足Centric work鍖ow is the one being used by most publishers ≒ Publishers are either: Too heavily invested in exis:ng technology Unwilling to shid to a new way of thinking ≒ Or both
  • 13. Lets dig into Print-足Centric. ≒ Most publishers are knee-足deep in legacy systems and technology CMS such as K4, Woodwing Adobe InDesign QuarkXpress ≒ Publishers s:ll rely on print for almost 90% of their revenue ≒ Not surprising they think print 鍖rst
  • 14. Cond辿 Nast and Adobe h^p://www.youtube.com/watch?v=34f13csGLIs ≒ Cond辿 Nast uses Adobe Digital Publishing Suite to produce enhanced digital edi:ons of their printed magazine ≒ Their approach is typical of many publishers who think print 鍖rst
  • 15. The typical digital edi:on is sta:c. ≒ Most publishers have edi:ons on digital newsstands ≒ Many publishers choose print circula:on distributor rela:onships to get onto digital newsstands ≒ CDS Global ≒ Dis:cor ≒ More oden than not, these edi:ons are replicas of print edi:ons created from single page PDFs
  • 16. Alterna:ve solu:ons: ≒ Solu:ons exist that allow publishers to use print PDF 鍖les to create digital edi:ons Issuu 3Dissue Uni鍖ip Zinio VirtualPaper Turnit Adobe Publishing Suite Texterity ≒ DIY advantage maintains control of your product ≒ Pricing and tools vary
  • 17. Great digital DIY examples: ≒ The Kit h^p://www.thekit.ca/ Started as a digital-足only publica:on Originally built in partnership with Texterity ≒ Covet Garden h^p://covetgarden.com/ A digital magazine accessed on their website Uses an embedded viewer or open on iPad Created using Issuu
  • 18. Delivering 鍖les for digital edi:ons: ≒ The majority use print PDF 鍖les to create the digital edi:on ≒ Re-足rip the PDF to tablet viewer speci鍖ca:ons Resolu:on, RGB colour-足space Create a jpeg 鍖le Two 鍖les delivered for each page ≒ PDF for zooming in ≒ jpeg for fast view
  • 19. To 鍖nd e鍖ciency, I start here. ≒ Build a smart work鍖ow Address requirements for all edi:ons/plalorms ≒ Automate pain points Sodware and script within applica:ons ≒ Share resources across plalorms Mul:purpose content as much as possible Finding e鍖ciency across plaYorms requires a bit more crea,vity.
  • 20. Crea:ng PDF 鍖les is the easy part. ≒ Using any design applica:on: PDFX-足1a is a standard senng Customized job op:on senngs can be imported to accommodate digital edi:on vendors PDF 鍖le speci鍖ca:ons ≒ If your premedia process is automated, both print and digital edi:on 鍖les can be created simultaneously ≒ PDF 鍖les can be created, named and delivered to each vendor/supplier
  • 21. Now the job is done, so what? ≒ We have two iden:cal sta:c edi:ons of the magazine, one print and one digital ≒ Enhancing the sta:c digital edi:on pages happens once the PDF 鍖les are uploaded to the vendor ≒ Typically, you can enhance by adding: URL links Sound clips Embedded video Some might call that boring or a waste of the plaYorms biggest asset digital capability.
  • 22. Evidence of the boring factor. Source: h^p://deadtreeedi:on.blogspot.ca/
  • 23. Some applica:ons are more 鍖exible. ≒ Adobe Digital Publishing Suite, Woodwing and Virtual Publisher are all print/digital edi:on Content Management Systems ≒ Each works with InDesign within the CMS and allows the designer to: create versions for mul:ple plalorms view on mul:ple device templates ≒ CMS can manage internal work鍖ow and integrate editorial with ad material
  • 24. Be^er controlled expecta:ons. Allows designer to view the layout on various screen sizes and tweak if necessary.
  • 25. Some magazine content is published on websites. ≒ There are a few ways to make that happen: You can cut and paste Someone else can cut and paste ≒ Unfortunately, with all this terri鍖c technology, and the whole publishing process being digital, in a Print-足Centric work鍖ow this is the best cross-足plalorm solu:on weve got.
  • 26. To bridge the gap. ≒ Some website developers have created sodware to help you manage content: Agility CMS Wordpress Squarespace There are several more, but Agility is very ac,ve with publishers, will customize their solu,on and help clients get rolling.
  • 27. S:ll, its cut and paste. ≒ To avoid cut and paste, there are ways to take copy from InDesign and plop it into Wordpress. PageZepher from Markzware indexes content and exports to Wordpress Export from InDesign as XML and import into Wordpress (this ac:on can be automated) But it aint pre]y. A lot of work needs to be done by the web editor.
  • 28. Images are another thing. ≒ Automa:on can be used share resources between print and web ≒ Scrip:ng sodware such as Enfocus Powerswitch can be set up to convert image 鍖les, then deliver them to web editors CMYK to RGB 300dpi to 72ppi (or whatever is required) Determine 鍖ow based on 鍖le type ≒ .ai goes through Illustrator ≒ anything else through Photoshop
  • 29. Could it be easier? ≒ Yes ≒ A content-足centric approach could bene鍖t all plalorms, but applica:ons to support that work鍖ow for print edi:ons do not exist ≒ Not to men:on dyed-足in-足the-足wool print tradi:onalists convincing them to change is like pulling teeth
  • 30. Is it possible to work another way? ≒ Who knows what responsive design is? ≒ Consider responsive design templates and how that works ≒ HTML5, CSS and tagging content HyperText Markup Language Cascading Style Sheets ≒ Di鍖erent styles can be applied depending on the output device being used ≒ Digital versions can be di鍖erent from printed versions, designers can tailor the presenta:on of elements for each plalorm
  • 31. Responsive youve been served. Elements are served depending on screen dimensions, pixels per inch.
  • 32. Torontoist website is responsive. ≒ Elements are recon鍖gured depending on what device you are viewing the website on ≒ Try it on your desktop, mobile device, tablet ≒ Try Chatelaine.com too
  • 33. And why not a page of a magazine? ≒ Depends on who you ask ≒ Allows for content focus, i.e. Content-足Centric ≒ Some edi:ng would be required Audience considera:ons ≒ Yet, for moving content around in a work鍖ow for mul:ple devices, tagging would be an ideal solu:on ≒ Thoughts?
  • 34. Ques:ons? ≒ Fire away ≒ Who is seeing Wes Bos this adernoon? ≒ Thank you for listening ≒ Keep in touch: kimlatreille@gmail.com Twi^er: @kim_elle h^p://kimlatreille.tumblr.com