blob: d2382aa525fa38670bfa6c0ab693d97c464b096e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
|
# 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, run these commands:
```bash
make all
```
To build docs for one SIG, run these commands:
```bash
make SIG=sig-apps gen-docs
make SIG=sig-testing gen-docs
make WG=resource-management gen-docs
```
where the `SIG` or `WG` 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:
```markdown
<!-- 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:
```markdown
<!-- BEGIN CUSTOM CONTENT -->
## Upcoming SIG goals
- Do this
- Do that
<!-- END CUSTOM CONTENT -->
```
|
