Apply folder/category structure of docs.helm.sh

- moves Docs files from root /docs into subfolders
- adds a using-helm folder (6 docs)
- adds a architecture folder (1 doc)
- adds a developing-charts folder (8 docs)
- adds a glossary folder (1 doc)
- adds a history folder (1 doc)
- adds a related folder (1 doc)
- renames the helm folder to helm-commands

docs/chart-best-practices/index.md

@@ -17,4 +17,3 @@ may find that their internal interests override our suggestions here.
 - Kubernetes Resources:
 	- [Pods and Pod Specs](pods.md): See the best practices for working with pod specifications.
 	- [Third Party Resources](third_party_resources.md): Third Party Resources (TPRs) have their own associated best practices.
-

docs/chart-best-practices/labels.md

@@ -47,8 +47,3 @@ release | REC | This should be the `{{ .Release.Name }}`.
 chart | REC | This should be the chart name and version: `{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}`.
 app | OPT | This should be the app name, reflecting the entire app. Often the chart's `{{ .Chart.Name }}` is used for this. This is used by many Kubernetes manifests, and is not Helm-specific.
 component | OPT | This is a common label for marking the different roles that pieces may play in an application. For example, `component: frontend`
-
-
-
-
-

docs/chart-best-practices/pods.md

@@ -73,5 +73,3 @@ the pod.
 But this is even more important for sets like Deployment.
 Without this, the _entire_ set of labels is used to select matching pods, and
 this will break if you use labels that change, like version or release date.
-
-

docs/chart-template-guide/accessing_files.md

@@ -222,4 +222,3 @@ data:
 Currently, there is no way to pass files external to the chart during `helm install`. So if you are asking users to supply data, it must be loaded using `helm install -f` or `helm install --set`.
 
 This discussion wraps up our dive into the tools and techniques for writing Helm templates. In the next section we will see how you can use one special file, `templates/NOTES.txt`, to send post-installation instructions to the users of your chart.
-

docs/chart-template-guide/builtin_objects.md

@@ -49,4 +49,3 @@ In the previous section, we use `{{.Release.Name}}` to insert the name of a rele
 The values are available to any top-level template. As we will see later, this does not necessarily mean that they will be available _everywhere_.
 
 The built-in values always begin with a capital letter. This is in keeping with Go's naming convention. When you create your own names, you are free to use a convention that suits your team. Some teams, like the [Kubernetes Charts](https://github.com/kubernetes/charts) team, choose to use only initial lower case letters in order to distinguish local names from those built-in. In this guide, we follow that convention.
-

docs/developing-charts/charts_hooks.md

@@ -188,4 +188,3 @@ deterministic executing order. Weights are defined using the following annotatio
 Hook weights can be positive or negative numbers but must be represented as
 strings. When Tiller starts the execution cycle of hooks of a particular Kind it
 will sort those hooks in ascending order.
-

docs/glossary/glossary.md

@@ -179,5 +179,3 @@ These exposed variables are called _values_ in Helm parlance.
 Values can be set during `helm install` and `helm upgrade` operations,
 either by passing them in directly, or by uploading a `values.yaml`
 file.
-
-

docs/index.md

@@ -1,35 +0,0 @@
-# Helm Documentation
-
-- [Quick Start](quickstart.md) - Read me first!
-- [Installing Helm](install.md) - Install Helm and Tiller
-  - [Kubernetes Distribution Notes](kubernetes_distros.md)
-  - [Frequently Asked Questions](install_faq.md)
-- [Using Helm](using_helm.md) - Learn the Helm tools
-  - [Plugins](plugins.md)
-- [Developing Charts](charts.md) - An introduction to chart development
-	- [Chart Lifecycle Hooks](charts_hooks.md)
-	- [Chart Tips and Tricks](charts_tips_and_tricks.md)
-	- [Chart Repository Guide](chart_repository.md)
-	- [Syncing your Chart Repository](chart_repository_sync_example.md)
-	- [Signing Charts](provenance.md)
-	- [Writing Tests for Charts](chart_tests.md)
-- [Chart Template Developer's Guide](chart_template_guide/index.md) - Master Helm templates
-  - [Getting Started with Templates](chart_template_guide/getting_started.md)
-  - [Built-in Objects](chart_template_guide/builtin_objects.md)
-  - [Values Files](chart_template_guide/values_files.md)
-  - [Functions and Pipelines](chart_template_guide/functions_and_pipelines.md)
-  - [Flow Control (if/else, with, range, whitespace management)](chart_template_guide/control_structures.md)
-  - [Variables](chart_template_guide/variables.md)
-  - [Named Templates (Partials)](chart_template_guide/named_templates.md)
-  - [Accessing Files Inside Templates](chart_template_guide/accessing_files.md)
-  - [Creating a NOTES.txt File](chart_template_guide/notes_files.md)
-  - [Subcharts and Global Values](chart_template_guide/subcharts_and_globals.md)
-  - [Debugging Templates](chart_template_guide/debugging.md)
-  - [Wrapping Up](chart_template_guide/wrapping_up.md)
-  - [Appendix A: YAML Techniques](chart_template_guide/yaml_techniques.md)
-  - [Appendix B: Go Data Types](chart_template_guide/data_types.md)
-- [Related Projects](related.md) - More Helm tools, articles, and plugins
-- [Architecture](architecture.md) - Overview of the Helm/Tiller design
-- [Developers](developers.md) - About the developers
-- [History](history.md) - A brief history of the project
-- [Glossary](glossary.md) - Decode the Helm vocabulary