Editoria 0.1 introduced a basic ‘Table of Contents’ interface for organizing components of a book project (e.g. chapters), monitoring the status of those components, and launching the web-based authoring tool to make edits to the contents of those components. Books, however, are made up of many components that may not appear in the final Table of Contents, and there are additional complexities in status, workflow and attributes that an effective interface for managing book components needs to handle elegantly.
In collaboration with members of the editorial team at UC Press, the developers of Editoria have now completed mock-ups for a revised Table of Contents interface that, going forward, we’ll be referring to as the Book Builder. In Editoria 0.2, this interface will include the following enhancements:
- Customizable default set of book components, including standard, Chicago style divisions (e.g. Front Matter, Body, Back Matter)
- Ability to upload a Microsoft Word *.docx file to each component — and, as an alternative, the ability to launch the web-based authoring tool to compose the material from scratch
- Toggles to record and indicate the current state of manuscript preparation (e.g. To Edit, Editing, Edited)
- Pagination indicator (right, left, flow, run-in)
- Automatic chapter numbering in the Body division, with the ability to indicate when a component should not be numbered
Features not included in the 0.2 development sprint, but under consideration for future releases include:
- Support for component sub-titles
- Support for components that may not include any accompanying text (e.g. Part I, Part II)
- Support for media components, with additional tools to track rights clearance status, format and resolution validation, and alternate ‘static’ media when movies or audio files are embedded.
Editoria 0.2 development begins June 27th, with a target release planned for late July / early August.
We welcome your feedback!
If you have questions, suggestions or ideas, please add them in the ‘Leave a Reply’ section below, or write to us directly: firstname.lastname@example.org