This repo contains the source code of Kmesh Website and all of the docs for Kmesh.
Welcome to join us and you are more than appreciated to contribute!
Here's a quick guide to updating the docs. It assumes you're familiar with the GitHub workflow and you're happy to use the automated preview of your doc updates:
- Fork the Kmesh/website repo on GitHub.
- Make your changes and send a pull request (PR).
- If you're not yet ready for a review, add a comment to the PR saying it's a
work in progress or add
[WIP]
in your PRs title. You can also add/hold
in a comment to mark the PR as not ready for merge. - Wait for the automated PR workflow to do some checks. When it's ready, you should see a comment like this: Deploy Preview for kmesh-net ready!
- Click Details to the right of "Deploy preview ready" to see a preview of your updates.
- Continue updating your doc until you're happy with it.
- When you're ready for a review, add a comment to the PR and assign a reviewer/approver. See the Kmesh contributor guide.
In the Kmesh documentation, a note is required at the beginning of each document as follows:
---
draft: false
linktitle: XXX
menu:
docs:
parent: XXX
weight: 1
title: XXX
toc: true
type: docs
---
There are four points to note:
linktitle
is the title displayed in the menu.title
is the title displayed on the document page.parent
indicates which directory this document is contained in. For example, if you want to write a document under theuser guide
, you need to set theparent: user guide
. For the correspondence of each menu, please refer to menus. A simpler way is to directly copy the configuration of the existing documents in the directory.weight
is used to order the documents. Should avoid duplication and conflicts prevented. It is also best not to use adjacent numbers to facilitate the insertion of new documents. A spacing of 5 is recommended. If you want your document to always be at the end of the current directory, you can just use 99.