community/generator
Christoph Blecker 15c20e236d
Add link to open community issues/PRs
2017-10-31 14:16:43 -07:00
..
testdata Remove duplication 2017-07-14 10:20:04 +02:00
vendor/gopkg.in/yaml.v2 vendor gopkg.in/yaml.v2 2017-10-24 23:17:03 -07:00
.gitignore Remove duplication 2017-07-14 10:20:04 +02:00
Gopkg.lock vendor gopkg.in/yaml.v2 2017-10-24 23:17:03 -07:00
Gopkg.toml vendor gopkg.in/yaml.v2 2017-10-24 23:17:03 -07:00
OWNERS Make tabs in OWNERS files into 2 spaces. 2017-08-15 16:33:18 -07:00
README.md Don't use docker by default for sig docs generator 2017-10-24 23:12:43 -07:00
app.go Don't use docker by default for sig docs generator 2017-10-24 23:12:43 -07:00
app_test.go Don't use docker by default for sig docs generator 2017-10-24 23:12:43 -07:00
header.tmpl Don't use docker by default for sig docs generator 2017-10-24 23:12:43 -07:00
list.tmpl correct the link of meeting 2017-10-21 13:38:03 +08:00
sig_readme.tmpl Add link to open community issues/PRs 2017-10-31 14:16:43 -07:00
wg_readme.tmpl Add link to open community issues/PRs 2017-10-31 14:16:43 -07:00

README.md

SIG Doc builder

This folder contains scripts to automatically generate documentation about the different Special Interest Groups (SIGs) of Kubernetes. The authoritative source for SIG information is the sigs.yaml file in the project root. All updates must be done there.

When an update happens to the this file, the next step is generate the accompanying documentation. This takes the format of two types of doc file:

sig-<sig-name>/README.md
wg-<working-group-name>/README.md
sig-list.md

For example, if a contributor has updated sig-cluster-lifecycle, the following files will be generated:

sig-cluster-lifecycle/README.md
sig-list.md

How to use

To (re)build documentation for all the SIGs in a go environment, run:

make generate

or to run this inside a docker container:

make generate-dockerized

To build docs for one SIG, run one of these commands:

make WHAT=sig-apps
make WHAT=cluster-lifecycle
make WHAT=wg-resource-management
make WHAT=container-identity

where the WHAT var refers to the directory being built.

Adding custom content to your README

If your SIG or WG wishes to add custom content, you can do so by placing it within the following code comments:

<!-- BEGIN CUSTOM CONTENT -->

<!-- END CUSTOM CONTENT -->

Anything inside these code comments are saved by the generator and appended to newly generated content. Updating any content outside this block, however, will be overwritten the next time the generator runs.

An example might be:

<!-- BEGIN CUSTOM CONTENT -->
## Upcoming SIG goals
- Do this
- Do that
<!-- END CUSTOM CONTENT -->