Feature proposal: Add Designer roles and Scripting in previewer and external API
Note: this is the global proposal. It will be followed up in the respective issues already created and 2 more probably another one to be created concerning the API: #308 #208
Context
Geneva University of Art and Design publishes or co-publishes between 10 and 15 publications per year. As a solution to centralize de editing of content and design of these publications the editorial committee ( Dimitri Broquard - head of Visual Communication department, Julie Enckell - Head of cultural development & Anthony Masure - Head of research) has initiated the idea of an inhouse publishing house, HEAD Publishing. The publishing house will be supported by a dedicated website for distributing the publications which will allow for the content to be read in "Long read" format (HTML), PDF, and ePub download, as well as the possibility to order through Print on Demand services(ex.LULU).
Goals
- Be able to use all Paged.JS features for generating experimental design layouts
- Establish a clear role for designers in book production and a design phase.
- Be able to get the book content via an API so that it could be displayed in the dedicated website and also sent to Print-on-demand services ( ex. /api/book/:bookId?format=pdf )
- Have its own visual identity for the interface based on the one identity manual done by Dimitri Broquard.
Specifications
Based on our speculations there will be two scenarios for the design of a book:
- The whole design is done in Paged.JS previewer and saved the PDF, EPUB is exported locally for API consumption
- The Layout design of the book is done in InDesign as some of the designers are not yet acquainted with coding layouts, in this case, a exported IDML file will be used ONLY if it has already achieved a "finished" state by the Editors, authors, etc. Once the pdf is finished , it can be uploaded to the platform where it can then be approved by the team.
Technical Specification
( in the red dots of the UX mockups)
- Be able to edit multiple Stylesheets, they are all added through template manager.
- A JavaScript window for registering handlers, there will only be one per template.
- A download package button that will include all the CSS, HTML and JS file
- A Full screen button
- Different views ( grid and flip book)
- in Dashboard: A "validated" or "finished" state of the book which will disallow further changes and enable API calls.
Note: In the case # 2 of design with IDML and pdf being uploaded the Dashboard seems the best for us.