Proposal – Draft 1

Written by the e-Weavers
Kathleen, Daryn, Susmita, Josh, Maggie, Alison

The e-Weavers plan to create an ebook for iBooks, which is an application that works on multiple platforms and is more interactive than a Kobo or Kindle reader. Our group-specific reason is that we each have this kind of device so we can test out the ebook ourselves.

Our aim is to maintain the spirit of the original article. The playfulness of the article is its main selling point, and our primary goal is to maintain the integrity of the original article while considering ways of making it better than the original. We value the importance of the design and artwork and are interested in investigating how it relates to, and enhances, the article itself. This means incorporating colour and graphics into the body of our ebook. We hope this would bring out that original playfulness. The overall presentation of the book is important to us, so we plan to spend a considerable amount of time working on the design and format.

Type is important. It needs to be resizable and readable, but preserve the design of the individual page and the piece as a whole. We realize this might be the role of the ebook reader, not a direct function of the ebook, but we want to be sure that our document can be resized by iBooks. We want to explore whether or not it is beneficial for us to make the book reflowable or not; if we do, is this going to make the format too flexible and changeable, or will it increase interactivity? This shouldn’t be the most time-consuming of our projects, but will tie into our design process and our discovery of iBook’s many capabilities.

We plan to include a table of contents because of the article’s many subheadings and the unwieldy length of the article as a book. This way, readers can jump to whichever section they want to read right from the table of contents. The book will be organized by chapters and subheadings, creating an organized structure important for readability. We are also aware that the purpose the article serves is largely educational, and we feel that including clear chapters and subheadings will lend better to an audience that is looking for a clear answer to the question “what is code?”

It is our goal to include the initial pop-up message in the article as an epigraph. We feel this makes a good translation from website to ebook. We are considering how we will treat pop-up footnotes throughout, and plan to spend considerable time on this aspect of the book to further set it apart from traditional forms and, again, maintain the original spirit of the work. These may become static footnotes, or if we can figure out the functionality of the pop-up, we would like to keep them this way.

 

The background on the webpage “What is Code?” is very colourful. We would like to create a title page for our ebook with similar colours and perhaps the pattern as well. This is both to attract readers to our ebook, as well as forge a stronger connection between ebook and website.

For practicality reasons, we will be removing some of the GIFs that won’t function on iBooks, as well as any other little images – like Twitter icons – that no longer have a place in our version. Our hope is to make the graphs and tables throughout the article readable and that they will contribute to the content in an educational way.

We also plan to investigate additional functions like videos and other interactive elements to determine if they will work for the platform we’ve chosen. Is an epub3 going to be a viable option for us? We plan to determine this in the next week, before solidifying our working timeline and planning the finished product.

We have assigned roles for each group member to research and test on our epub file. Our timeline for this research is to come to the table on Friday with specific information as to whether our initial plans are feasible given our project deadline. Once we further investigate our individual roles and responsibilities, we will be better able to come together and create a project that is cohesive and fully-realized.

 

Our initial work will be broken down as follows:

Susmita: Creating a working table of contents

Kathleen: Investigating graphs & footnotes; will these work with our chosen platform?

Alison: Creating the epigraph

Maggie: Work on interactive elements, including the capabilities of InDesign, and the possibility of making an epub3

Josh: Cleaning up logos, GIFs, things we’re removing

Daryn: Planning and conceptualizing our design (including colour usage and visual graphics)