Sourcefabric Manuals

 English |  Español |  Français |  Italiano |  Português |  Русский |  Shqip

Booktype 2.3 for Authors and Publishers

Formless Content

The page is changing in so many ways – time-based media is making its way into book pages, reactive content, scrollable space, and a multitude of differing display devices make designing pages pretty hard work these days. How to design for so many possibilities? How to understand so many possibilities?

Craig Mod of Flipboard makes a very compelling argument for two forms of page: formless and definite content, in an article he wrote for Book: A Futurists Manifesto - the first book to be produced by PressBooks. Craig's argument in a nutshell, and in his own words, is:

the key difference between Formless and Definite Content is the interaction between the content and the page. Formless Content doesn’t see the page or its boundaries; Definite Content is not only aware of the page, but embraces it. It edits, shifts, and resizes itself to fit the page [...] Put very simply, Formless Content is unaware of the container. Definite Content embraces the container as a canvas.

Craig argues that most book content we know is formless – the text can reflow into other containers without affecting the meaning.  It's a really well-argued position and one that is in tension to the current design methodologies of book designers today. Book designers are taught to design contained space – books are a very definite context in which they work. Desktop Publishing applications are built to meet this methodology. Pixel perfect manipulation within a strictly contained space. If the designed digital article does not exactly match the printed artefact then something went wrong. A lot of energy has gone into this process.

Formless design principles are uneasy to consider for traditional book designers – how can you design for a page that does not yet know its container? It is literally like asking a book designer to design a book without telling them the page dimensions.

As it happens, web designers have been thinking about page design too. For a long time now, web designers have made pages that embrace differing containers – they have been working, at least in part, with formless content.

Tools like Booktype take the web designer's aptitude for working with formless content and enable them to produce books. A good tool set for designing formless books should not work with a constrained page dimensions. It is tempting, for example, to think of working with a design environment with constrained page-like artefacts - think of Google Docs as an example. Could something like Google Docs with its digital, scrollable, yet fixed page size be a good starting point for some kind of design tool? Place layout and typographical controls on top of Google Docs and do we have the next book design environment?

I don’t think so, because it is exactly the kind of idea that is blinded by the media of the past and cannot accept that things have changed. We must design tools that enable book design for formless content. What those tools look like is a very interesting question and one which Aleksandar Erkalović (Booktype lead developer) and Adam Hyde have been working on with students (Hannes Bernard and Aiwen Yin) from the Sandberg Institute in Amsterdam.

Our argument is that the design of formless content is really a partially constrained environment since elements within the page have some kind of relationship to each other. This is an argument web designers are familiar with when using design tools like position:relative – a rule which sets a relative position relationships between objects. Relationships can be constrained or shaped by rules which will be at least partially preserved when displayed in different contexts. The meaning is preserved by the relationship between the elements more than by their relationship to the constraints of a page.

This is the reasoning behind Cascading Style Sheets – the design language of the web. It is rule based design and even partly conditional. It is possible to express conditions in CSS, even though it is not done that often. A CSS rule such as :

h2+p {page-break-inside:avoid;}

is a conditional CSS rule which will apply the style only when a paragraph follows a <h2> heading element.

Web designers know this kind of thinking, but book designers are going to have to let go of old ideas and enjoy thinking and designing this way. The legacy is so strong that some designers are pretending the issue does not exist. There are tools now sold as design environments for iPad books. They give a near 1:1 page relationship between design environment and the final result. However, we all know what happens to digital hardware – it changes.

What is true now will not be true five years from now, so the idea that an ebook is a contained space is very appealing to traditional book designers, but it will be a short lived myth. iPads might keep the same form for five years, they might not, but they certainly will not keep it over the next five to ten years. Better to learn how to design in the new way than be fooled into thinking you can bring all the old methods to a new medium and get away with it for long.

Booktype works with formless content and design using CSS. A visual design environment assists this process but CSS styles can also be modified manually. Almost any CSS that you make yourself or find on the Internet can be applied to these books.

To understand the relationship between CSS and the final result there is no substitute for trial and error. Designers must first understand how a ‘web native’ technology — CSS — applies to page based media. This paradigm appears simple, but it requires a re-alignment of how book designers think about designing books, and to do this designers must try the process and persevere until they succeed. After the initial success with Booktype, things become easier!

There has been error in communication with Booktype server. Not sure right now where is the problem.

You should refresh this page.