b-ber is both a method and an application for producing publications in a variety of formats—EPUB 3, Mobi/KF8, static website, PDF, and XML file, which can be imported into InDesign for print layouts—from a single source that consists of plain-text files and other assets. b-ber also functions as a browser-based EPUB reader, which explains the name.
To begin using b-ber, please visit the Getting started page. For more on the rationale behind b-ber, read “Working on Our Thoughts,” by Triple Canopy’s creative director, Caleb Waldorf. To see example projects produced with b-ber, please visit our b-ber demo repository or view projects online at Triple Canopy.
b-ber facilitates control of the design of publications on the level of individual formats by accounting for the specific characteristics of EPUBs, websites, PDFs, etc. b-ber’s architecture allows for the styles included in each theme to be “scoped” to different build types. In other words, the text and media treatments for an EPUB can differ from those for a browser-based version of the same publication. Existing themes, developed by Triple Canopy, include combinations of styles, typefaces, and media layouts. Alternatively, publishers can design and develop their own themes for b-ber. They can also override any of these styles at the level of the individual publication in order to craft a layout that conforms to the needs of the work. By offering high-level design flexibility and format-specific customization, b-ber enables authors, editors, designers, and technologists to simultaneously consider the ideal manifestation of a publication and the multiplicity of scenarios in which it will be encountered.
Find out more in the b-ber wiki.
Summary of Features
- Builds EPUBs, Mobi/KF8s, PDFs, static websites in both horizontal and vertical orientation, and XML files that can be imported into desktop publishing software;
- Generated output follows the EPUB 3.0 specification;
- Creates and links metadata that conforms to the webpub specification for web-based publications;
- Can be styled through overrides or custom themes.
The project roadmap will be coming soon.
Issues should be reported in the b-ber project repository. Please use the template when creating a new issue. Issues should be tagged with the appropriately scoped label (
b-ber/theme, etc.) if it's clear where the issue originates. Other labels (
enhancement, etc.) should also be used when applicable.
Pull requests are welcome. If you plan to contribute to b-ber's development, please send an email to email@example.com, so that we are aware of any contributions you plan on making. There is no explicit style-guide, but a style of coding that's consistent with the existing codebase should be maintained.
Code of Conduct
We ask people to respect the code of conduct which can be read here.