On the opportunities, challenges, and best practices related to improving publishing workflows.
Tech Forum 2020 recap: Workflows
How we work defines how we compete
BookNet Canada's product ecosystem: A flowchart
How tagging can streamline your print + digital workflow
The transition from producing strictly print books to producing content for a multitude of digital formats means it’s time to rejig some tried-and-true workflows.
Colleen Cunningham, Senior Ebook Developer at F+W, A Content + eCommerce Company, has some thoughts about using a content management system to produce content in the digital age.
PressBooks: Web-First Workflow Just Got Even Easier
Anthologize: Making Web-First Workflow Even Easier for Publishers
Anthologize grew out of One Week | One Tool—yes, one week—a project of the Center for History and New Media, George Mason University.
So, what’s all the fuss about? This is the extra step that’s been needed to make it extremely easy for any publisher to implement web-first workflow : all you need is WordPress and a plugin.
Web-First Workflow: Confluence Proof-of-Concept
Back in May, Noah blogged about the potential for Confluence by Atlassian to work as a web-first xml workflow solution. His post put Confluence up alongside WordPress from SFU’s Book of MPub (full disclosure: I worked with John Maxwell in 2009 on Start With the Web and still do some related work today) as a contender. Really, any CMS/wiki can work, it’s just a matter of how well it works and whether it works for you.
Evernote to the Fore
“Build products people lust after”
This is the advice given by the founders of Atlassian during the Atlassian Starter Day conference and it spurred me to write about Evernote (with a dash of Safari 5).
I have had Evernote on my laptop for a while but since I have been using my iphone more recently I’ve really become enamoured with Evernote.
Confluence As a Web-Based Publishing System
In conferences and sessions we often discuss XML based publishing workflows…a concept I love, but I term I hate. Concept — content that is single sourced, marked up and is used to drive a plethora of end uses (i.e. pbook, ebook, web content, app, etc…). Why do I hate it? It is scary, maybe not to everyone, but to enough people in the “content business” that the term itself can often kill any hope of implementation.
Here’s why we need solutions that take the scary out of XML publishing workflows.
