Repository structure and workflow
Lisk uses Antora as a documentation generator.
Structure
The internal structure of development
and main
branch.
docs/
folder
The The source content for the general Lisk documentation is located in the docs/
folder.
The file structure follows the expected structure for Antora documentation, see: docs.antora.org/antora/latest/standard-directories/.
All content is written in AsciiDoc.
ui/
folder
The The presentation of the documentation is stored completely separate from the actual content.
The UI is based on the Antora default UI (see also docs.antora.org/antora-ui-default/).
It is customized as listed in the following points below:
-
Updated the CSS to improve the UX and follow the Lisk brand styleguide.
-
Added additional features, such as:
-
Algolia site search
-
Dark theme
-
Zoom for images
-
Additional layout for swagger UI
-
Tab-blocks
-
β¦β
-
build/
folder
The The build
folder contains the following:
-
β¦βthe
site.yml
file, which is used to generate the Lisk documentation using Antora. -
β¦βthe
searchdocs-scraper
folder, for creating the search index. -
β¦βthe
lib
folder which stores the Asciidoc extensions that are used in the Lisk documentation.
. βββ lib/ (1) βββ searchdocs-scraper/ (2) βββ live-site.yml (3) βββ site.yml (4)
-
The
lib/
folder contains extensions for Antora. The extensions are specified in the playbook file of Antora. -
The
searchdocs-scraper/
folder contains the file required to update the Algolia search index of the documentation. -
The playbook used to compile the live documentation on lisk.com/documentation with Antora. Results are pushed to the
live
branch. -
The playbook used to compile the documentation at liskhq.github.io/lisk-docs with Antora. Results are pushed to the
git-page
branch.
Product-specific docs
There are additional content sources, which each store the documentation for a specific software product of Lisk.
Content sources
Note
|
These branches store either the latest or the WIP versions of each component. |
-
docs-sdk
-
docs-core
-
docs-service
Previous versions
-
docs-COMPONENT-v1
where
-
COMPONENT
can be eithersdk
,core
, orservice
. -
v1
represents the respective version number of the corresponding product.
-