a41213bc86
* Add constants for the open source and samples repos branch names
Open source branch name - `openSourceBranchName`
Sample repos branch name - `openSourceSamplesBranchName`
* Add base path constants to the open source and samples repos
Fully replace base path to open source codebase - `openSourceBranch`
Fully replace base path to open source samples - `openSourceSamplesBranch`
These can be accessed in the docs using `os_branch` and `os_samples_branch`
Correct usages in the docs to use these constants.
* Correct links
Cherry picked from - commit
|
||
|---|---|---|
| .. | ||
| docs_builder | ||
| ext | ||
| source | ||
| .gitattributes | ||
| .gitignore | ||
| build.gradle | ||
| index.html | ||
| install-docsite-requirements.sh | ||
| make-docsite.sh | ||
| Makefile | ||
| packages.md | ||
| README.md | ||
| requirements.txt | ||
Corda Documentation Build
To run the Corda Documentation build run ./gradlew makeDocs
Note: In order to run the documentation build you will need Docker installed.
Windows users: If this task fails because Docker can't find make-docsite.sh, go to Settings > Shared Drives in the Docker system tray agent, make sure the relevant drive is shared, and click 'Reset credentials'.
rst style guide
It's probably worth reading this to get your head around the rst syntax we're using.
version placeholders
Currently we support five placeholders that get substituted at build time:
"|corda_version|"
"|java_version|"
"|kotlin_version|"
"|gradle_plugins_version|"
"|quasar_version|"
If you put one of these in an rst file anywhere (including in a code tag) then it will be substituted with the value in constants.properties (which is in the root of the project) at build time.
The code for this can be found near the top of the conf.py file in the docs/source directory.