• A New Publishing Tool | Getty Publications
    http://www.getty.edu/publications/digital/platforms-tools.html

    We are developing Quire, a new publishing tool—optimized for publication discoverability and longevity—that uses a static-site generator, Hugo, to create and output titles in multiple formats from plain text files. E-book files are distribution-ready for Amazon, Apple, and other vendors; PDF files are print-on-demand ready. And the online edition can be hosted on any web server, with no special configurations or installations necessary and no backend databases or content management system to update and support over the long term.

    In traditional website publishing, a content management system (CMS) is connected to collections and image databases (1) and set up on a server (2). The CMS is used to create the website, and once the website is published, the CMS rebuilds the site pages each time they are loaded by a user (3). Thus, the CMS must be kept running for the lifetime of the publication.

    In static-site publishing, the CMS is just software and a folder of files on your, the publisher’s, computer (1) that are used to build the site. The site files are then uploaded to the server (2), and users (3) access them directly. You only need to run the site software and upload new files if you want to make updates to the publication.

    And yet, despite the name, static sites can be as dynamic and interactive as you want them to be, thanks to the full support of the complete web platform (HTML5, CSS3, and JavaScript). Zoomable and rotating images, interactive maps, and embedded glossaries are just a few of the features that can be included.

    https://www.youtube.com/watch?v=VVYe0qR5DnM

    https://github.com/gettypubs/quire
    http://blogs.getty.edu/iris/an-editors-view-of-digital-publishing

    #publications_hybrides #prepostprint #web2print #digital-first_publishing #Hugo #static_site_publishing

  • Book production with CSS Paged Media at Fire and Lion
    https://www.pagedmedia.org/book-production-with-css-paged-media-at-fire-and-lion

    I love the many small, technical puzzles that designing books with CSS presents. There are also some much bigger challenges that we’re tackling, and where community effort might go a long way.

    First, multiformat thinking is hard. The whole point of our digital-first approach is to store content only once, and produce multiple formats automatically. This puts tremendous pressure on project managers, developers, authors, editors, designers and proofreaders to think in multiple formats at once.

    For instance, on the web, hyperlinks are cheap: you can add them anywhere, attach them to any text, and the design can keep them out of the reader’s way. In print, hyperlinks vanish or, if presented as page numbers, take up space and attention. Another example I mentioned above is interactivity: the text in the filmstrip figures in The Economy has to be sensitive to the fact that readers might be looking at clickable slides or at a static, printed page. And when controlling the flow of text, editors have to be aware of things like what happens when an element is floated: it appears beside the text it precedes in HTML, which can be counterintuitive for things like sidenotes beside paragraphs.

    Like many publishers, we’ve had to invest a lot in training our team in multi-format thinking.

    Second, manual page refinement is time-consuming. Automated layout with CSS gets us far, taking care of perhaps 90 per cent of a traditional typesetter’s role. But after that a human still has to check every page and refine many of them. On The Economy, I spent three or four hours on each chapter making small tweaks to get figures and sidenotes to fall in just the right place for maximum readability. On most novels, we spend at least three or four hours manually adjusting letter-spacing and soft hyphenation to avoid bad breaks, widows, orphans, and short lines.

    If there is one thing we need better automation for, it’s proper, typographically sensitive widow-and-orphan control.

    Third, technical skills are expensive. Extraordinary demand for developers worldwide means that dedicated technical team members are completely unaffordable for most publishers. If you’re going to create books with HTML and CSS, you need technical skills on the team, either in-house or in partnership with an outsourced team you can really trust.

    In our team, we dedicate a significant piece of everyone’s time to technical skills development – both editors and designers – to reduce dependency on developers. And, as our technical lead, I have to spend at least half my time learning or training others. A commitment to digital-first publishing is a commitment to a serious learning curve.

    https://fireandlion.com
    https://electricbookworks.com
    http://electricbook.works
    https://github.com/electricbookworks/electric-book

    #publications_hybrides #prepostprint #web2print #digital-first_publishing #Jekyll #static_site_publishing