-
Notifications
You must be signed in to change notification settings - Fork 1
Glossary
calebwaldorf edited this page May 8, 2019
·
1 revision
Below are terms used throughout this wiki, which have specific meaning within the b-ber framework.
Term | Definition |
---|---|
b-ber | The overall b-ber framework. |
bber |
The command for running b-ber from the command line interface. |
build | The processes for building different output formats. |
build type | The different types of formats produced from the source files. |
EPUB | An EPUB 3 file built by b-ber. |
Reader | The browser-based reader that displays an EPUB 3 file. |
Mobi | A Mobi/KF8 file built by b-ber. |
Web | A static website built by b-ber. |
A PDF built by b-ber. | |
XML | An XML file optimized to be imported into Adobe InDesign for print production. |
directives | Custom markdown-it extensions for structuring a project’s markdown. |
figures | Images that use built-in styles and interactivity. |
metadata | The metadata generated from the metadata.yml file. Outputted to TK. |
reading order | The sequence of files presented to the reader. In some build types – EPUB, Reader, Mobi, Web – this will be reflected as the the table of contents. |
scoping styles | Styles can be scoped to specific build types. E.g., the body text could be scoped to be blue in an EPUB and red in the Reader. |
theme | A theme is the overall styles for a project and can be set via the CLI. b-ber is packaged with a serif and sans-serif theme. |
- Adding metadata
- Creating content
- Generating new content
- Authoring and editing content
- Reading order (Table of Contents)
- Configuring the build
- Adding a cover image
- All directives
- Text
- Media
- Misc