Open-source Kyma and Kyma module user documentation is displayed at https://kyma-project.io
. The website uses docsify as a documentation site generator.
The overarching Kyma content is pulled from the /docs
folder in the /kyma
repository. Module documentation is pulled from the /docs/user
folder in respective module repositories.
After initialization, to run, docsify uses the following files located in the /docs
folder in the /kyma
repository:
index.html
for configurationREADME.md
as the home page.nojekyll
preventing GitHub Pages from ignoring files that begin with an underscore_sidebar.md
listing all Markdown documents to be displayed and ruling navigation between those documents on the website
To publish a document located in the /kyma
repository, follow these steps:
- Create a pull request adding your content to a Markdown file located in the
/docs
folder. - Add a new
_sidebar.md
file including a link to your document, or update an existing_sidebar.md
to include it.
To publish a document located in an existing module repository, follow these steps.
- Create a pull request adding your content to a Markdown file located in the
/docs/user
folder in your module repository. - In the
docs/user
folder, add a new_sidebar.md
file including a link to your document, or update the existing_sidebar.md
to include it.
To publish a document located in a new module repository, follow the steps from Publish a document from an existing module. Once completed, do the following:
- In the
/kyma
repository, open the/kyma/docs/_sidebar.md
file and under Modules, add a link to your module documentation main page. - Update
index.html
by adding a new alias entry in the part. Use the following pattern:
```html
alias: {
'/{MODULE_REPOSITORY_NAME}/(.*)': 'https://raw.githubusercontent.com/{GITHUB_PROJECT_NAME}/{MODULE_REPOSITORY_NAME}/main/docs/$1',
},
```
For example:
```html
alias: {
'/serverless-manager/(.*)': 'https://raw.githubusercontent.com/kyma-project/serverless-manager/main/docs/$1',
},
```
CAUTION: When you update navigation paths in documentation, make sure you check all
_sidebar.md
files that may be affected.