Making a book should be no harder than making a website. What is a book, after all, but a special class of website that happens to have a history of being displayed in purpose-built, paper-based browsers?
Why do we expect frameworks for building websites to output websites that are compatible with multiple browsers, whereas building books … is still a giant shambles as soon as you need to satisfy interoperability with multiple paper and non-paper browsers.
It shouldn’t be any harder to make a standards compliant book that will work in paper and non paper browsers, and some solutions to this problem should be found in the success of web-based web building frameworks, and CMSs.
I build new ways of doing book stuff on the web: PressBooks, LibriVox, iambik, and a few other bits & bobs. bio from Twitter
Sign in to add slides, notes or videos to this session