Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update KubeEnforcer docs to be consistent with others #108

Merged
merged 1 commit into from
Jul 28, 2020

Conversation

agilgur5
Copy link
Contributor

@agilgur5 agilgur5 commented Jul 24, 2020

Description

  • have an Aqua image at the top

  • say "Aqua Security" for heading, not just "Aqua"

  • have a one-line description of the Chart

  • use a "Contents" section

    • not just "Contents:" text
    • and link to it in ToC
  • use a "Configurable Variables" section

    • not a "Customize your configuration section"
    • and add a "KubeEnforcer" subsection
    • and add links to both in ToC
  • all the other charts already do this, KubeEnforcer was the odd one out

Tags

Related to #106 and #105 in adding consistency. The differences in consistency tripped me up when writing #99 as well.

Fixes inconsistencies introduced in #86

- have an Aqua image at the top
- say "Aqua Security" for heading, not just "Aqua"
- have a one-line description of the Chart
- use a "Contents" section
  - not just "Contents:" text
  - and link to it in ToC
- use a "Configurable Variables" section
  - not a "Customize your configuration section"
  - not an H3, but an H2
  - and add a "KubeEnforcer" subsection
  - and add links to both in ToC

- all the other charts already do this, KubeEnforcer was the odd one out
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants