We appreciate any contributions to our documentational resources! This includes improvements and corrections to existing content, as well as translations & entirely new content.
In case you are unfamiliar with the GitHub process and you still want to add your own senseBox documentation, you may send it to as markdown (preferred) or office document via mail. Check out our guide (english, german for templates and more.
Thank you for your contribution!
We use the node.js-based tool GitBook for the rendering of the content.
There is an editor specifically for GitBooks, which may be used to edit the book's content. You can get it here. It should be quite convenient to use, we didn't try it yet though.
To live-preview or render a book, you need the npm package gitbook-cli
.
Install it by running npm i -g gitbook-cli
. If that does not work or you don't have npm
, have a look at the official documentation.
To get a live preview of a books website-output, run
gitbook install # only required once
gitbook serve
GitBook provides the output formats website
, pdf
and ebook
.
To render a book run:
gitbook install # only required once
gitbook build # build the website
gitbook pdf # build the pdf
gitbook epub # build the ebook
Each (multilingual) book resides on its own branch.
Currently these are book_edu
, book_home
and book_osem
, each containing a de
and en
language book.
The german versions have far more content, while the english versions are steadily supplemented from there.
Files that are parsed specially by GitBook have a filename in caps:
LANGS.md
: defines the languages of a multilingual bookREADME.md
: the landingpage of a book, eg an introductionSUMMARY.md
: the table of contents, rendered as the left navbarGLOSSARY.md
: a glossary, whose terms are referenced on all other book pagesFOOTER.md
: the page footer on any page
Stylesheets applied on all books are in ./styles
, and are symlinked into each book (unix only).
Currently, all BLOB files (except for community projects, see below) are hosted at a separate repo, to improve reusability within our workinggroup.
Projects contributed by the community should be included in the book of their respective language, in the following directories:
de/community_projekte/
en/community_projects/
Currently the books are built and hosted by gitbook.com.
A commit on each of the book_<name>
branches automatically triggers a new build of the book there.
The domains <edu.books.sensebox.de>, <home.books.sensebox.de> and <osem.books.sensebox.de> are pointing on the builds of these books.
The pdf builds however are built on travis to support custom cover pages. These builds are autocommited into the gh-pages
branch.