Tianocore-docs Gitbook offline document status (PDF, EPUB, MOBI)
Michael D Kinney
I have been working on addressing the gaps in the transition to
the new GitBook services for the TianoCore documents in the GitBook
markdown format. The major gap is the loss of the offline PDF,
EPUB, and MOBI formats.
I have found a GitHub action that performs the equivalent work
of the legacy GitBook server and it supports publishing the HTML,
PDF, EPUB, and MOBI formats in a gh-pages branch of a GitBook
document repository. The gh-pages branch supports the HTML
web view of the documents and is stored as part of the same
GitHub repository that hosts the document source files.
I have tried this out on the edk2-TemplateSpecification document
in the Tianocore-Docs GitHub organization.
The following is the link to the GitHub actions YML file that
publishes a draft version of the document from the master branch
and the release versions of the document from and release/* branch.
* Source: https://github.com/ZanderZhao/gitbook-action
* Docs: https://zlogs.net/gitbook-action/
I found a few issues with the support of embedded PlantUml
diagrams. A fork of the GitBook puml plugin is available
that addresses these issues. The book.json file is updated
to use this newer plugin.
Links to the GitBook puml pluigis:
The following are the links to the EDK II Template Specification
documents published by this Gitbook Action. Notice that all the
links are to files in either GitHub repos or the web pages published
by GitHub when a gh-pages branch is present and updated.
Draft versions from master branch:
Release versions from release/0.2 branch:
In order to enable this on all the documents in Tianocore-docs, the
following tasks need to be performed on each document repo:
* Update book.json in master and release/* branches to use the
newer PlantUML plugin.
* Add the file .github/workflows/gitbook-action.yml to the
master and release/* branches.
* Force a document build on the master and release/* branches to
publish all draft and release versions of the documents.
Please review the content here and the published documents and let
me know if there are any concerns with switching to a GitHub
Action to publish all Tianocore Gitbook markdown based documents.