<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Damian Gibbs on Medium]]></title>
        <description><![CDATA[Stories by Damian Gibbs on Medium]]></description>
        <link>https://medium.com/@damiangct?source=rss-ba77097094f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WO-fP0CtBf3RzmCuGBDe4g.jpeg</url>
            <title>Stories by Damian Gibbs on Medium</title>
            <link>https://medium.com/@damiangct?source=rss-ba77097094f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:59:19 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damiangct/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Writing ~ less is more]]></title>
            <link>https://medium.com/@damiangct/writing-less-is-more-fa7fcdbeb16e?source=rss-ba77097094f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa7fcdbeb16e</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[markdown]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[editing]]></category>
            <dc:creator><![CDATA[Damian Gibbs]]></dc:creator>
            <pubDate>Sat, 19 Nov 2016 19:19:21 GMT</pubDate>
            <atom:updated>2016-11-19T19:19:55.067Z</atom:updated>
            <content:encoded><![CDATA[<h3>Writing tools ~ learning from techies</h3><p>The relationship between creators and their tools is an integral part of the creative process, and influences the outcome and creator equally. For the author and artist, learning to use the tools to a point where they become an extension of themselves is magical.</p><p>My son is into visual media and we regularly watch the <a href="https://www.youtube.com/user/caseyneistat">YouTube vlogger</a> <a href="https://medium.com/u/cb3bf029673b">Casey Neistat</a> together. The entertainment factor and educational learning experience is top notch, and the style of cinematography is, for me, something unique. One of Casey’s mantras on film making is you use the equipment that will get you the best shot at the time. If you watch his episodes, the camera (whether it is a mobile phone, DSLR, GoPro, or one of his drones) is an extension of himself. He is so closely integrated with his film-making tools that they no longer appear to come between him and the shot.</p><p>For me, this is the Holy Grail for publishing: transparency of tools. All too often the tools of publishing come in the way of the publishing process. The popular tool chain used by many publishers is convoluted leaving the authors, copy editors, designers, and marketing department in virtual silos, all using different tools and multiple file formats.</p><p>I get that editors and authors have used Word for decades, maybe some remember WordPerfect, and the familiarity of the interface and settings allows them to be more productive and creative. The same goes for designers and typesetters.</p><p>At one time Casey was frustrated with his creative process. The conventional wisdom is to take a break, recuperate, reassess, and then come back rejuvenated. But, in true Casey style, he upped his game and challenged himself to do a vlog every day!</p><p><em>And that’s when things changed.</em></p><p><em>When you become mission critical, your assessment of your tools changes, and you experience your work through new eyes.</em></p><p>I needed to up my productivity when creating and converting ebooks. Dreamweaver was slow, cumbersome, with far too many distracting palettes and thingy-ma-bobs. After trialling and testing other tools, I chose brevity in the form of <a href="http://www.barebones.com/products/bbedit/index.html">BBEdit</a>, and once I had only partially mastered the software my productivity skyrocketed. Granted, I also learn’t gazillions about HTML and CSS, but that was also largely due to BBEdit helping me focus on the code.</p><p>Same happened with writing every day. I just couldn’t imagine writing in Word or Pages, saving, exporting (or copying and pasting), checking the formatting, etc. So much better to put it straight into Medium — simple, clear, right tools in the right place, publish, share. Done.</p><p>Unsurprisingly, the art and science of focused writing is no more entrenched than in software development. Good <strong>documentation</strong> of the software is vital for the users as well as the development<strong> team</strong>. When you need to document everything (write user guides, help pages, FAQ pages, and continually update all of these), <strong>every single day</strong>, you can be sure the techies will find a more efficient way to do it!</p><p>I bolded the “documentation”, “team”, and “every single day” because, in essence, this is the core of book production.</p><h4>So what do techies do and use?</h4><p>First up, less is more. A coder spends an inordinate amount of time with fingers on the keyboard. Every stroke counts. Taking your fingers off the keyboard to use a mouse to click on something is time not spent typing or editing, and breaks the flow of coding and writing.</p><p>Secondly, their content is in open, plain-old-vanilla ascii text format. Ok, I already hear groans about no wysiwig, layout, etc, but bear with me.</p><p>Thirdly, they use mature and open systems to work collaboratively. These systems keep track of versions of documents, so you are able to see differences (like track changes).</p><p>Fourthly, they automate to minimise mundane and repetitive tasks (e.g. building table of contents, and inserting definitions for glossary items), auto complete common words and phrases, and expand predefined acronyms for long words and phrases.</p><p>Lastly, they publish content to various output file formats from the same source document. This includes conditional publishing (you wouldn’t want to include a video in a printed book, but maybe a poster image instead with a caption).</p><p>As an example for the first point, look at the Pages interface (Word just takes ages to load) below is point and click to make text bold, change heading levels, etc. You can apply keyboard short cuts for many things but have to go and set them up and options are limited.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1009/1*Cd2COAbfo0JyEONHgRgn2g.png" /></figure><p>What if you could write and format without having to worry about the mouse, or point-and-click, and just could focus on the writing? Enter <a href="http://daringfireball.net/projects/markdown/syntax">John Gruber</a>, founder of the open <a href="https://en.wikipedia.org/wiki/Markdown">markdown format</a>:</p><blockquote>Markdown is intended to be as easy-to-read and easy-to-write as is feasible.</blockquote><blockquote>Readability, however, is emphasized above all else. A Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions. …</blockquote><blockquote>To this end, Markdown’s syntax is comprised entirely of punctuation characters, which punctuation characters have been carefully chosen so as to look like what they mean. E.g., asterisks around a word actually look like *emphasis*. Markdown lists look like, well, lists. Even blockquotes look like quoted passages of text, assuming you’ve ever used email.</blockquote><p>An example of a simple markdown document would be:</p><pre># Top level heading / Head A / Chap head</pre><pre>A paragraph of text with a **bold** word and an *italic* word. Paragraphs of text are separated by a double line just to keep it clean and easy to read.</pre><pre>## Sub heading</pre><pre>Lists are dead easy to do and follow a similar logic to paragraphs in that the start and end of a list must be separated by an double line space.</pre><pre>1. list item <br>2. list item</pre><pre>* bulleted list item<br>* bulleted list item</pre><p>There are a number of online markdown editors that you can experiment with. Here is an example in <a href="http://stackedit.io/">stackedit.io</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GzzLH8sBhWc5AjN-0UQDCA.png" /><figcaption>Stackedit.io</figcaption></figure><p>Remember the philosophy of markdown above: <em>“Readability, however, is emphasized above all else.”</em> Although the above editor has a preview pane, the raw text is still perfectly readable. As you become more proficient the preview pane will fall way and you will focus entirely on the writing.</p><p>Just as an aside, a fundamental concept in markdown is that<em> content is separate from how the content looks on screen. The on-screen display of the markdown can be customised.</em></p><p>Over and above online editors there are many standalone apps for your computer and mobile devices which support markdown.</p><p>Electric Bookworks have an excellent guide to markdown specifically aimed at book publishing. Check out the “how markdown works” section: <a href="http://electricbook.works/guide/text/03-markdown.html#how-markdown-works">http://electricbook.works/guide/text/03-markdown.html#how-markdown-works</a>.</p><p>If, or when, at some stage you have to get your content into InDesign (which uses doc, docx or rtf to import text), converting is simple. Here is an example of the very same markdown document run through the amazing open Pandoc software (<a href="http://pandoc.org/">http://pandoc.org/</a>), all it took was:</p><pre>$ pandoc sample.md -o sample.docx</pre><p>and voila:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1007/1*rlr7k0MVcys8q002MD8QlA.png" /><figcaption>The sample.md doc converted using Pandoc and then opened in Word.</figcaption></figure><p>I am very well aware of the mind shift around the above versus just doing it all in Word. I’ve been there, but being able to fire up a text editor and keep writing is just too good event to think of going back back.</p><p>The markdown demonstrated here is one of a few “flavours” or variations of markdown. It is a format that has expanded over the years and has adapted to more and more sophisticated types of content. Markdown is more pervasive than you might imagine. Try typing a message in Whatsapp and put an “*” either side of a word, e.g. *hello*.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/738/1*s6yOvrA80wHid0Q5kbAP3A.png" /><figcaption><a href="https://techcrunch.com/2016/03/29/now-you-can-impress-your-friends-with-bold-italics-and-strikethrough-in-whatsapp/">Techcrunch</a></figcaption></figure><p>Web based publishing tools have adopted markdown in many flavours as the entry authoring format and web tech (HTML and CSS) has become the underlying language for publishing.</p><p>Markdown makes the interaction between you and the content. It is beautifully simple and powerful.</p><p>Authoring is only one link in the publishing chain and I will explore the rest of the process in future articles. But for now, if you are going to be authoring and editing, the markdown format provides a huge amount of leverage for a very elegant and simple open file format.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa7fcdbeb16e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why use a typesetter?]]></title>
            <link>https://medium.com/@damiangct/why-use-a-typesetter-664d5ba63b3f?source=rss-ba77097094f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/664d5ba63b3f</guid>
            <category><![CDATA[ebooks]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[ebook]]></category>
            <category><![CDATA[typesetting]]></category>
            <dc:creator><![CDATA[Damian Gibbs]]></dc:creator>
            <pubDate>Sat, 19 Nov 2016 08:40:40 GMT</pubDate>
            <atom:updated>2016-11-19T08:40:40.297Z</atom:updated>
            <content:encoded><![CDATA[<p>Technology has brought many improvements to publishing — speed, opportunity for great design, accuracy, and multiple output formats (epub, mobi, print pdf). However, the book will only be as good as the people behind it, and how well they can use the tools provided. A word-processor doesn’t make a great writer, like wise, InDesign doesn’t make a good looking and easy reading book. Sure, InDesign provides the tools, but a skilled typesetter will make your book shine.</p><p>There is certainly a place for off-shore vendors providing scalable typesetting services for large volumes, and sometimes payoffs as different operators work on the same jobs in shifts. However, whether you invest in “boutique” typesetter offering bespoke, personalised service, or off-shore vendor for scalable services, there are some guidelines that will help ensure a great relationship with your typesetter and efficient book production.</p><h3>Style guides</h3><p>This is not to be confused with a spec design. While the spec design covers the design elements of the book, the style guide covers editorial and typographical conventions to be used. It may seem under the domain of the copy editor, but often things are picked up during typesetting which are seen through fresh eyes.</p><p>Content developers and editors can avoid quality and design issues by setting up a style guides either for the publication, and/or as a publishers style guide. This provides the typesetter a reference for any queries or inconsistencies within the manuscript while typesetting, and the typesetter can make an informed decision without having to refer back to the client before carrying on.</p><p>Some examples will be spelling (ize vs ise, color vs colour), which words are consistently italicised (foreign language words, <em>et al</em>, <em>viz, etc</em>), how lists are handled (capitalize with full stop, or not), and numbering style for lists and levels. Lists are easy to setup in InDesign and therefore not have to be manually typed in by author or content editor. Also, bringing in lists using Word’s list feature often gets mangled.</p><h3>Typography and layout</h3><p>The essence of a good book is readability. Of course, great content, but what’s the point if it is difficult to read? It is important to consider your target market’s reading environment. Style of fonts, font size, leading, and margins all play a part in defining the content to their respective readers.</p><p>Mix this into your books overall costing. Say the budget for the book 256 pages but the first draft comes to 263 pages, and there is no way to cut content? By adjusting the font size and leading marginally, you could bring back one line per page and return the book to budgeted extent. In addition, or alternatively, space above and below headings, adjusting letter and word spacing, or the body area (page margins), are all possibilities to bring back a line or two per page and book into extent without having to rework content.</p><p>Every book needs hyphenation and justification settings adjusted to minimise loose lines (rivers running through the text), multiple hyphens, and widows and orphans. Typesetters work with this all the time and should be adjusted for every book.</p><p>In digital (epub, mobi, html) books page extents are not an issue, other than possibly conversion costs which page based, typography is still as important for the legibility by the reader. However, it is far more complex and challenging as the final reading devices vary considerable and the user often has the ability to override the publishers settings. In some cases this is good as many books are run through meat grinder processes using one size fits all templates and the outcomes can be very poor. But, with some effort and foresight, ebooks can be designed and setup with good results.</p><p>Typesetters that have worked in both print and digital will ask you before outputting which reading devices your are targeting and then adjust the epub styles accordingly. You can ask for a one size fits all epub, but sacrifices will have to be made.</p><h3>Structure</h3><p>The mysterious and often hidden underbelly of content. Books have inherit structure which is transparent to the reader, but is the very thing that makes some books exceptional to pick up and hold.</p><p>Visual book design and designing structure go hand in hand. Understanding structure of the content is the key starting point of designing the look and feel. Well nested content providing a logical and natural flow helps the reader to enjoy the content without struggling to maintain concentration.</p><p>When designing for print using InDesign, design elements are all visual objects placed on a page using various tools and objects in InDesign. Each repeated object or text element is given a style name, e.g. “HeadA”, “HeadB”, “sidebar-box”, “bold”, “italic”, “chap-head”, etc. All these style names represent an object in the book and when adding or reformatting an object, the style name provide a shortcut to quickly format the object without reapplying the individual style elements. The styles are grouped according to paragraph, character, object, table and table cells.</p><p>The challenge comes when transferring the content from print to digital formats.</p><p>Unlike the InDesign, digital formats separate content from the visual display. InDesign is a single file with everything inside it, and you need InDesign to open the file and edit. Digital books use web technology as a starting point — HTML and CSS files — and are plain text files which are editable using any number of open-source, free, or proprietary text editors.</p><p>The HTML file use open and closing tags to block content according to it structure. So for example, a top level heading would be <strong>&lt;h1&gt;</strong>This is the heading<strong>&lt;/h1&gt;</strong>. A level two heading, or “head B” would use <strong><em>&lt;h2&gt;</em></strong>, a paragraph of body text the <strong><em>&lt;p&gt;</em></strong> tag, etc. Yup, pretty much the same as the Ventura or Quark Xpress in the 1990s!</p><p>The CSS file fulfils the same function as the style sheets in Word or InDesign. They apply formatting to the content contained within the tags of the HTML file. This is done by using syntax where the tag name is used as a “selector”, and then the tag given attributes. For example <strong>p {font-size: 16px;}</strong>, this would apply 16px font size to all content enclosed in the <strong>&lt;p&gt;&lt;/p&gt;</strong> tags.</p><p>This is a super simple example and as with web technologies, things can get very complex very quickly. There are other elements such as classes and ids which can be added to the HTML tags that give greater control over the content, also adding more efficient ways to format and recycle or reused content.</p><p><em>So, how does this affect the publisher or content creators?</em></p><p>The key is consistency in styling InDesign documents so that as much of your content uses the same style names for the same types of elements. There are two parts to styling in InDesign: the <em>style name</em>, and the <em>html tag</em> applied within the style sheet. Even if the tag is not applied to the style name, just having consistent styles will make conversion more efficient. With consistent style naming it is possible to use them to apply the correct structure.</p><p><em>But why such an emphasis on structure?</em></p><p>Well, there is a strong swing in the direction of single source publishing workflows that use HTML as the source document and able to deliver to multiple formats (epub, mobi, screen and print pdf) without ongoing conversion processes. These systems bypass InDesign and open up the publishing process to a truly collaborative (parallel) workflow which has been the holy grail of publishing.</p><p><strong>But, for publishers to have efficient content conversion and to take advantage of single source publishing systems, content will have to be structured consistently and that starts with your existing content in InDesign.</strong></p><p>Style naming conventions are not difficult to setup and there are many CSS models (BEM, ATOM, OOP, etc) which have already addressed many issues that book publishers might face. One size will not fit all, but starting sooner than later will help to start creating more efficiency even within InDesign.</p><p>Many typesetters now understand this as they are also involved in converting books to digital version on behalf of clients.</p><h3>Confidentiality</h3><p>The accumulated experience across many different genres by a typesetter is passed through onto your titles, however, the details of your title should never be revealed other than those collaborating on the project. Work should not be sub-contracted out by the typesetter unless under explicit approval by the client.</p><h3>Backup and archiving</h3><p>Backup systems can be fully automated and any loss of data should not be more than a day. In addition, each round of proofs or changes should be saved with a different version number, e.g suffix with “prf_1”, “prf_2”, etc. This helps if reference for a change or update in a previous version is required.</p><p>On completion of a project a final archive is should be delivered to the client. The archive should include all the makeup files (InDesign, Idml, images, press pdf) and if required exported docx or html.</p><p>Many typesetters keep an archive of all the jobs and I have had clients come back many times looking for another copy, or to do reprint changes. Before embarking on reprint changes, make absolutely sure that the typesetter is working on the correct or latest version.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=664d5ba63b3f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reviewing the old, can serve as the teacher*]]></title>
            <link>https://medium.com/@damiangct/reviewing-the-old-can-serve-as-the-teacher-b770508bbf74?source=rss-ba77097094f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/b770508bbf74</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[publishing]]></category>
            <category><![CDATA[offshore]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[production]]></category>
            <dc:creator><![CDATA[Damian Gibbs]]></dc:creator>
            <pubDate>Fri, 18 Nov 2016 10:11:54 GMT</pubDate>
            <atom:updated>2016-11-18T11:50:40.677Z</atom:updated>
            <content:encoded><![CDATA[<p>I started out in book design and typesetting quite by accident. My first “real” job was an admin clerk at an international insurance corporate with a conservative ethos. All dark suites and ties. I was the typical square peg in a round hole, bright shirts and pants and a big hairy beard. The work was pretty mundane, all numbers and bookkeeping and balancing to the cent. The saving grace for me was that they had computers and every spare opportunity I had was building macros in Lotus 123 to make my work easier and less error prone. Even wrote some prank “viruses” and changed around the keys on the keyboards, great fun. After hours I was knocking out a monthly newsletter for my mom on her 386 beige pc box (even had a “turbo” button) with Windows 3.1. Also tried to teach myself Pascal, but gave up after an exhaustive session determined to get something working and found myself on the floor!</p><p>After a couple of years I transitioned from accounting clerk to apprentice typesetter. Early days of digital publishing was fascinating as I experienced first hand the effects of a disruptive technology. Some employees and repro houses just couldn’t face the challenge, and others transitioned. The adopters fell into two broad camps, those that adopted the technology but fiercely guarded the historical design “standards”, and those that adopted the new tech and pushed the boundaries.</p><p>It was round this time that South Africa entered the new democracy and a new educational system was implemented. For educational publishers it was a clean slate: new publishing tools (the DTP department had moved onto Apple with Quark), new curriculum to engage with, and a production workflow that needed to cope with the high demands of the submission process.</p><p>And so it went for the next 15 years. Government revised the curriculum another few times, more crazy submission deadlines, and publishers and suppliers burning the candle from both ends. The extreme pressure of churning out school books and teacher guides led to a rapidly expanded supplier base which include many inexperienced typesetters, editors, and project managers who never had the luxury of a comprehensive training and mentorship. To compound the skills deficit, many experienced and knowledgeable colleagues have scaled back, burnt out, moved on, or retired.</p><p>Government have now put a moratorium on new school books for the next few years and suddenly the local educational book publishing industry has slowed down almost to a halt. Publishers have to look everywhere to reduce costs and off-shoring typesetting as an immediate option.</p><p>The irony, for me, is during the last decade and a bit, even with all the new shiny software tools and tech, the local book production process (author -&gt; editor -&gt; typesetter -&gt;print -&gt; ebook) now goes through more sets of proofs than ever before. After a quite a few discussions with colleagues and production staff it is clear that some essential publishing processes have not been continued, or were lost.</p><p><em>So will off-shoring bring down costs of book production?</em></p><p>Immediately yes, rates are lower and the workforce is scalable. However, there are some “hidden” costs and payoffs: communication difficulties (time-zone differences, language and accent), service providers who engage with the content especially when dealing with indigenous languages, and future proofing content by ensuring it is <a href="https://www.linkedin.com/pulse/why-use-typesetter-damian-gibbs?trk=hp-feed-article-title-publish">structured consistently and correctly</a>.</p><p>Of course this is not a blanket rule, I have worked with some awesome vendors who have done great work. But it takes time to build up the relationship, clearly set out the requirements, check, feedback, check, etc.</p><p>The inherent issues discussed above still persist and will follow through to wherever the work is sent, local or off-shore. We (the royal “we”, publishers, editors, typesetters, indexers, illustrators, designers, etc) need to ask:</p><p><em>“Why could we do books in 3 or 4 sets of proofs in the 1990s with relatively primitive digital tools, and now 6 or more sets with all the shiny tech and access to internet?”</em></p><p>By addressing this question, I feel it is more than plausible that the cost of book production could be substantially reduced by collaborating with local suppliers and return to insourcing. There are many issues around the cost benefit of off-shoring and <a href="http://www.theatlantic.com/magazine/archive/2012/12/the-insourcing-boom/309166/">this article from 2012 raises some pertinent points</a>. This excerpt illustrates the crux of off-shore vs inshore benefits, but strongly recommend reading the full article.</p><blockquote>The GeoSpring suffered from an advanced-technology version of “IKEA Syndrome.” It was so hard to assemble that no one in the big room wanted to make it … By considering the workers who would have to put the water heater together — in fact, by having those workers right at the table, looking at the design as it was drawn — the team cut the work hours necessary to assemble the water heater from 10 hours in China to two hours in Louisville. …</blockquote><blockquote>For years, too many American companies have treated the actual manufacturing of their products as incidental…</blockquote><blockquote>Harry Moser, an MIT-trained engineer, … started an organization called the Reshoring Initiative in 2010, to help companies assess where to make their products. “The way we see it,” says Moser, “about 60 percent of the companies that offshored manufacturing didn’t really do the math. They looked only at the labor rate — they didn’t look at the hidden costs.” Moser believes that about a quarter of what’s made outside the U.S. could be more profitably made at home.</blockquote><blockquote>… but many of those hidden costs come later. In the first blush of cheap manufacturing, it’s easy to overlook the slow loss of your own skills, the gradual homogenization of your products, the corrosion of quality and decline of innovation.</blockquote><p>While publishing tools are rapidly evolving, <a href="http://electricbook.works/">with some very interesting and innovative local projects</a>, they will all be for naught until the local publishing community (companies and suppliers) invest in themselves and further develop local publishing skills, talent, and innovation.</p><p>The South African book publishing industry was born out of colonial traditions and systems, and the impacts on our society is a debate I would rather leave to more astute colleagues. However, there is an opportunity to innovate and create a publishing environment that better serves our readers, schools and tertiary educational requirements, and grow local industry.</p><p>A prime example of what is possible locally is <a href="https://medium.com/u/5a3f59d027">Arthur Attwell</a>, a unique blend of tech, teaching, innovation, and deep industry knowledge. <a href="http://bookdash.org/">Who said you can’t make a book in a day</a>, or make books from <a href="https://github.com/electricbookworks/electric-book">web tech</a>.</p><p>Drop me a line or request to join <a href="https://www.linkedin.com/groups/1187507"><strong>amaBukaBuka</strong></a> group to connect, network, and to start some conversations around improving and innovating publishing in (South and Southern) Africa. The group was originally setup to help promote local suppliers at the 2012 Cape Town International Book Fair.</p><ul><li><em>Quote originally seen on pythoni app for iOS, haven’t been able to find a source.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b770508bbf74" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>